Connecting an agent

Connect Claude Code, Claude Desktop, Cursor or any MCP client to Glowo.

There are two transports. Use the hosted one unless you have a specific reason not to.

Hosted

The MCP endpoint is:

https://api.glowo.dev/mcp

Nothing to install. Your client registers itself, sends you to Glowo to approve scopes, and receives a token.

Every client below connects to that one URL — only the file it goes in changes.

Claude Code

claude mcp add --scope user --transport http glowo https://api.glowo.dev/mcp

Or check it into the repository so everyone on the team gets it:

{
  "mcpServers": {
    "glowo": {
      "type": "http",
      "url": "https://api.glowo.dev/mcp"
    }
  }
}

The first time the server is used, your browser opens the Glowo consent screen. Approve the scopes and you are connected.

Codex CLI

codex mcp add glowo --url https://api.glowo.dev/mcp

codex mcp add detects that the endpoint speaks OAuth and starts the browser flow straight away. If you skip or interrupt it, run the login step on its own — it is safe to repeat:

codex mcp login glowo

The equivalent config, if you would rather write the file yourself:

[mcp_servers.glowo]
url = "https://api.glowo.dev/mcp"

codex mcp list shows the server with an Auth column — it reads Not logged in until the browser flow completes.

Cursor

{
  "mcpServers": {
    "glowo": {
      "url": "https://api.glowo.dev/mcp"
    }
  }
}

Use ~/.cursor/mcp.json instead to make it available in every project rather than just this one.

VS Code

VS Code uses servers, not mcpServers — the rest is the same shape.

{
  "servers": {
    "glowo": {
      "type": "http",
      "url": "https://api.glowo.dev/mcp"
    }
  }
}

Any other MCP client

A client that speaks remote MCP over HTTP and supports dynamic client registration connects with nothing but the URL — no client ID to create, no secret to paste. Glowo implements RFC 7591 registration and publishes standard discovery metadata (RFC 8414 authorization-server metadata and RFC 9728 protected-resource metadata), so such a client can find and enrol itself.

Registration is the part to check. A client can support OAuth perfectly well and still expect you to paste a client ID it cannot obtain here — Glowo issues client IDs only through dynamic registration, so there is nothing to hand it.

If your client asks for the discovery documents explicitly:

Managing the connection

Connected clients appear in the dashboard under Settings → MCP → Connections, where you can revoke any of them immediately.

Local

The stdio server runs on your machine and authenticates with a Glowo API key instead of OAuth. Use it when you are running Glowo yourself, or when you want the client to talk to a local API.

git clone https://github.com/iiAku/glowo.git
cd glowo
bun install
bun run --cwd packages/mcp-server build

claude mcp add --scope user \
  --env GLOWO_API_TOKEN=gl_... \
  glowo -- node /path/to/glowo/packages/mcp-server/dist/main.js

Configuration

Point GLOWO_API_URL at your own instance if you self-host.

The package is MIT licensed and lives at packages/mcp-server in the Glowo repository.

Which to choose

Use hosted if you are on glowo.dev. It needs no build step, grants scopes through an explicit consent screen, and is revocable per connection.

Use local if you self-host Glowo, need the agent to reach an API that is not publicly routable, or want the client talking to a server you built yourself.

Checking it works

Ask the agent something read-only first:

Which of my monitors are currently down?

If it answers, the connection and its scopes are good. If it reports a permission error, widen the scopes — or, on the local transport, the permissions on the API key.