Skip to content

Connect an AI client to the EdgeComet MCP server ​

You connect an AI client to EdgeComet by adding https://cloud.edgecomet.com/mcp as a remote MCP server and signing in through your browser. There is no API key: the client registers itself, and you approve it on an EdgeComet sign-in screen. Also called adding the EdgeComet connector.

After you approve, the client reads your EdgeComet data and drafts Edge SEO changes as you. It sees only the websites your account can open.

The EdgeComet sign-in screen for an AI client, titled Authorize Codex. It reads This application is requesting access to your EdgeComet data, shows Signed in as max@edgecomet.com, and lists This will let it: see your websites and their configuration; read your bot traffic, rendering, and cache analytics; read your Google Search Console metrics and alerts; draft Edge SEO changes, titles, canonicals, and structured data, for your review. The footer reads It works within your account's access and can prepare drafts, but cannot publish changes live, with Cancel and Authorize buttons

Before you start ​

  • An EdgeComet account. A new account sees the demo website. Add your own website in the dashboard, or from the chat with add_website.
  • An AI client that supports remote MCP servers over Streamable HTTP with OAuth sign-in.
  • On company plans, some clients need an admin to allow custom MCP servers first. Each client page says where.

Server details ​

SettingValue
Server URLhttps://cloud.edgecomet.com/mcp
TransportStreamable HTTP
AuthenticationOAuth with PKCE. The client registers itself, with no client ID or secret to enter
Suggested server nameedgecomet

The dashboard shows the same URL on the MCP Connection page: the account menu in the left strip, then MCP.

Pick your client ​

ClientHow you add the serverGuide
claude.ai and Claude DesktopCustomize > Connectors > Add custom connectorClaude
Claude Codeclaude mcp add --transport http edgecomet https://cloud.edgecomet.com/mcpClaude Code
ChatGPTPlugins > Add custom MCP serverChatGPT
Codex CLI, IDE extension and ChatGPT desktop appcodex mcp add edgecomet --url https://cloud.edgecomet.com/mcpCodex
GitHub Copilot in VS Code, JetBrains, Visual Studio and Copilot CLIMCP: Add Server, or copilot mcp addGitHub Copilot
Microsoft Copilot Studio and Microsoft 365 CopilotTools > Add a tool > New tool > Model Context ProtocolMicrosoft Copilot
Cursor~/.cursor/mcp.jsonCursor

For a client not listed here, see Other MCP clients.

How sign-in works ​

  1. You add the server URL to the client. The client finds EdgeComet's OAuth server and registers itself, with no setup on the EdgeComet side.
  2. The client opens your browser on EdgeComet. Sign in to the dashboard if you are not signed in yet.
  3. The screen Authorize {client name} shows the account under Signed in as and what the client can do.
  4. Press Authorize. The browser returns you to the client, and the EdgeComet tools become available. Cancel refuses the connection.

The client renews its access on its own while you keep using it. You sign in again after you revoke it, remove it from the client, or leave it unused for a long time.

What a connection can do ​

A connection acts as the EdgeComet user who approved it:

  • Websites: the websites your account can open: your own, and those of the teams you belong to.
  • Reads: your websites and their configuration, bot traffic, rendering and cache data, Search Console metrics, the crawl, alerts and Edge SEO rules, as the sign-in screen lists them.
  • Drafts: Edge SEO changes, which stay drafts until a person deploys them in the dashboard. No tool publishes.
  • Live data: page reads and keyword research. Keyword research and reads of other domains draw on a daily per-site budget.

See the tool reference for every tool.

Manage and revoke connections ​

The Connected applications table on the MCP Connection page lists each client that holds access:

  • Application: the name the client registered, such as Claude, Codex or Claude Code (edgecomet).
  • Connected: when the client last renewed its access.
  • Expires: when the client's current access runs out. The client renews it while you use it.

With no clients, the table reads "No applications are connected yet."

To revoke a client:

  1. Open the account menu in the left strip, then MCP.
  2. Under Connected applications, press Revoke on the client's row.
  3. In Revoke connection, press Revoke. The dialog reads: "It will lose access until you reconnect and authorize it again."

The Revoke connection dialog on the MCP Connection page. It asks Are you sure you want to revoke Codex? It will lose access until you reconnect and authorize it again, with Cancel and Revoke buttons

Also remove the server in the client, which deletes the access the client stored. Each client page has a Remove section. To connect again, add the server and sign in again.

Other MCP clients ​

Other clients connect the same way when they support remote MCP servers with OAuth and sign in through a browser on the same computer. For Gemini CLI, add the server to ~/.gemini/settings.json:

json
{
  "mcpServers": {
    "edgecomet": {
      "httpUrl": "https://cloud.edgecomet.com/mcp"
    }
  }
}

Then run /mcp auth edgecomet in a Gemini CLI session to sign in.

First steps after connecting ​

  1. Ask the client to list your EdgeComet websites. It calls list_websites and shows each website's ID and domains.
  2. Ask for an overview of one site, such as "Give me an overview of example.com in EdgeComet". The agent reads the dashboard's own numbers with get_report.
  3. Ask a question that combines sources. See Example prompts for the EdgeComet MCP server.

If it does not work ​

The browser does not open ​

Some clients also print the sign-in link. Codex prints "Authorize edgecomet by opening this URL in your browser:" with the link. Open it in a browser on the same computer, where you can sign in to EdgeComet.

The wrong EdgeComet account signed in ​

The sign-in screen names the account under Signed in as. Press Cancel, sign out of the dashboard, sign in with the right account and start the connection again.

The client lists only the demo website ​

Your EdgeComet account has no website of its own yet. Add one in the dashboard, or ask the client to add it with add_website. For a website someone else owns, ask the owner to add you to their team in Team Access, then ask the client again. See Invite your team.

Tools stop working after a while ​

Sign in again from the client: /mcp in Claude Code, codex mcp login edgecomet in Codex, or the client's reconnect button.

Next ​