MCP Server

EdgeComet exposes your data to AI assistants through an MCP (Model Context Protocol) server. Connect it to Claude - or any MCP client - and the assistant can work with your actual site data in conversation: query bot traffic and Search Console performance, read pages live, research keywords, and stage Edge SEO changes as drafts.

Endpoint: https://cloud.edgecomet.com/mcp

Authentication is OAuth: connecting sends you through a browser sign-in to your EdgeComet account, and the client only sees the websites your account can access. See Connecting a client.

What the server exposes

• Your data, queryable. The query tool reads five data grains - per-URL on-page SEO, the raw bot request log, and Search Console per page, per query, and per-URL trend - with filters, aggregation, and joins between them. export renders the same query shape to a downloadable CSV when the result is too large for a conversation.
• Drills and alerts. URL-hierarchy orientation, keyword-cannibalization detail, and your alert rules with their fired alerts.
• Live page reads. Fetch any page's current content as markdown or HTML - for your own pages, down to specific CSS selectors.
• Keyword research. SERP checks, ranked keywords, keyword expansion and metrics, competitor gap analysis, and backlink summaries. These buy live third-party data on a daily per-site budget.
• Edge SEO authoring. Draft on-page changes (titles, meta tags, content edits) as rules, preview them against the live ruleset, and save them as drafts. Deployment stays in the dashboard: there is deliberately no publish tool on this surface.

The full tool list with inputs and usage notes is in the tool reference.

A typical session

"Which of our category pages lost Google clicks this month, and do they still render a price?" - the assistant queries the Search Console trend grain, joins against your extracted page fields, reads one of the affected pages live, and proposes a fix as an Edge SEO draft you review in the dashboard.