Connecting a Client
The EdgeComet MCP server lives at:
https://cloud.edgecomet.com/mcpIt speaks the standard MCP HTTP transport with OAuth. Any client that supports remote MCP servers with OAuth can connect; no API keys or tokens are pasted anywhere - authentication is a browser sign-in to your EdgeComet account.
claude.ai and Claude Desktop
Add a custom connector and give it the server URL above. On first use, the connector opens a browser window where you sign in to EdgeComet and approve the connection. After that, EdgeComet's tools are available in your conversations.
Claude Code
claude mcp add --transport http edgecomet https://cloud.edgecomet.com/mcpThe first request triggers the same browser sign-in flow.
Other MCP clients
Configure a remote MCP server with the URL above. The server implements OAuth discovery, so a compliant client walks the authorization flow on its own and asks you to complete the sign-in in the browser.
Access and revocation
The connection acts as you: it sees exactly the websites your EdgeComet account can access, and nothing else. Requests are rate-limited per user.
To revoke a client's access, disconnect it on the client side, or revoke the authorization in your EdgeComet account settings. Reconnecting simply repeats the sign-in flow.
First steps after connecting
Ask the assistant to call list_websites first - most tools require a websiteId. Before writing queries, have it call get_schema: the response carries the complete query grammar plus your site's exact field names, custom extraction fields, and saved segments. See the query guide.