Remote MCP

Connect AI agents to Colma workspaces and SEO workflows

Colma MCP gives Claude, Codex, and other MCP clients a secure, organization-scoped way to inspect client sites, read and update strategy files, launch billable SEO investigations, and retrieve job results.

MCP endpoint Admin setup page

Colma MCP

Streamable HTTP server with OAuth 2.0 and PKCE

Endpoint: https://app.colma.ai/mcp
Transport: streamable-http
Auth: oauth2

Ask questions about a site

Pick a workspace, read prior research, search strategy files, inspect domains, and pull recent job context before answering.

Launch SEO investigations

Validate dependencies, estimate credit impact, launch approved workflows, check job status, and read completed results.

Save strategy as you go

Append durable strategy notes and update workspace documents so important decisions do not disappear into chat history.

Install

Connect from Claude and MCP clients

The Colma server is hosted at app.colma.ai. Users authenticate with their existing Colma account, then the client receives an OAuth access token scoped to that organization.

Claude Desktop does not accept remote HTTP MCP entries directly in claude_desktop_config.json. Add Colma through Settings > Connectors. Use the bridge config only when you specifically need a local Desktop config entry.

Claude Desktop

Open Claude Desktop, go to Settings > Connectors, add a custom connector, and enter this URL:

https://app.colma.ai/mcp

Claude Desktop local bridge

{
  "mcpServers": {
    "colma": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://app.colma.ai/mcp"]
    }
  }
}

Claude Code

claude mcp add colma --transport http https://app.colma.ai/mcp

Auth

OAuth for logged-in Colma users

Start in your MCP client

The client discovers Colma's OAuth metadata and opens the Colma authorization flow when a token is needed.

Authorize with your Colma session

Logged-in users can authorize without setting up a separate API key. New users sign in through Colma first.

Pick a workspace

Agents should call list_workspaces first, then pass the selected workspaceId to file, context, strategy, and workflow tools.

Discovery endpoints

MCP clients and directories can use these public endpoints to understand Colma's transport, auth requirements, logo, server card, and available tools.

MCP discovery Server card OAuth metadata Protected resource

Discovery JSON preview

{
  "mcp_version": "2025-11-25",
  "name": "Colma MCP",
  "endpoint": "https://app.colma.ai/mcp",
  "transport": "streamable-http",
  "logo": "https://app.colma.ai/colma-dot-cluster-512.png",
  "homepage": "https://www.colma.ai/mcp"
}