Connecting clients

The command is the same everywhere: run @cloudgrid-io/mcp over stdio for the local edition, or point a remote-capable client at a hosted URL for the web edition.

Hosted connect URLs (web edition)

Endpoint	Auth	Use case
https://mcp.cloudgrid.io/mcp	Anonymous-first	Publish without an account. Auth honored if presented.
https://mcp-connected.cloudgrid.io/mcp	Required (OAuth)	Full access with your identity — publishes into your grid.

The connected endpoint triggers an OAuth flow when authentication is needed. Both are inline-only (single-file pages); a multi-file app needs the local edition.

Claude Desktop

The easiest path is the one-click Desktop Extension. Download the .mcpb bundle from the MCP releases and open it (Settings, Extensions, Install from file). It carries the full local toolset. Sign in from chat with the grid_login tool on first use.

To configure it manually instead, add a stdio server:

{
  "mcpServers": {
    "cloudgrid": {
      "command": "npx",
      "args": ["-y", "@cloudgrid-io/mcp"]
    }
  }
}

Claude Code

Add the local server:

claude mcp add cloudgrid -- npx -y @cloudgrid-io/mcp

Cursor

Edit ~/.cursor/mcp.json:

{ "mcpServers": { "cloudgrid": { "command": "npx", "args": ["-y", "@cloudgrid-io/mcp"] } } }

Remote variant (nothing installed):

{ "mcpServers": { "cloudgrid": { "url": "https://mcp.cloudgrid.io/mcp" } } }

Codex

Add to ~/.codex/config.toml:

[mcp_servers.cloudgrid]
command = "npx"
args = ["-y", "@cloudgrid-io/mcp"]

# or remote, nothing installed:
# [mcp_servers.cloudgrid]
# url = "https://mcp.cloudgrid.io/mcp"

Gemini CLI

gemini mcp add cloudgrid npx -y @cloudgrid-io/mcp

Or edit ~/.gemini/settings.json:

{ "mcpServers": { "cloudgrid": { "command": "npx", "args": ["-y", "@cloudgrid-io/mcp"] } } }

claude.ai (web)

Add the hosted MCP server URL in your claude.ai connector settings:

• Anonymous publishing: https://mcp.cloudgrid.io/mcp
• Authenticated (full access): https://mcp-connected.cloudgrid.io/mcp

Signing in on the web

A hosted server cannot read a local credentials file, so each session signs in through the server:

1. grid_login returns a sign-in URL to open.
2. Complete Google sign-in in the browser.
3. grid_login_status polls and holds the token in the session.

Anonymous publishing needs no sign-in and works immediately.