Bring Ayzeo Into Your AI Assistant

MCP (Model Context Protocol) is the open standard for connecting AI assistants to external tools and data. Instead of an AI assistant being a sealed conversation, MCP lets it call real tools -- like querying your GSC data or generating a content page. Ayzeo's MCP server exposes your GEO data layer to MCP-capable AI clients so you can use Ayzeo from inside ChatGPT, claude.ai, Claude Desktop, or Claude Code instead of context-switching to the dashboard.

Supported today: ChatGPT (via developer mode until the Ayzeo app-directory listing is live), claude.ai and Claude Desktop (native custom connectors -- Settings, Connectors, add https://ayzeo.com/mcp/v2), and Claude Code (claude mcp add --transport http). Cursor, Windsurf, and Gemini CLI expect automatic client registration for OAuth servers, which Ayzeo does not offer yet -- support for those clients is on the roadmap.

list_projects is the entry point -- it returns every project you can access. The project toolset covers get_project_info, get_analysis_results, run_website_analysis, get_citation_history, run_ai_visibility_check, get_project_stats, list_prompts, run_prompt, get_content_pages, get_brand_mentions, get_geo_recommendations, get_gsc_opportunities, get_gsc_queries, get_ga_ai_traffic, and create_content_page_from_query, each taking the projectId your assistant picks up from the project list (get_geo_recommendations is global and takes none). The AI assistant discovers the available tools automatically via the standard MCP tools/list handshake.

Anyone with an Ayzeo account can connect. The projects available to your assistant are those whose owning organisation has an active Pro or Enterprise plan -- trials count. Team members are covered by the owner's plan: the owner pays, the team works. Free and Starter project owners need to upgrade for their projects to be reachable over MCP.

Yes -- natively. One connection covers every project you are a member of. Start a session by asking for your project list, then name the project each question is about; the assistant passes the right projectId to every tool call. You can even ask cross-project questions like "which of my projects has the weakest ChatGPT presence?" in a single conversation.

Via OAuth 2.1 with PKCE -- the same standard behind "Sign in with Google". You add https://ayzeo.com/mcp/v2 in your AI client, a browser window opens, you sign in with your Ayzeo account and approve access once. The client then holds only short-lived credentials that rotate automatically; your password never touches it. Rate limit: 100 requests per 5 minutes per connection. Disconnecting the connector in the AI client revokes its stored credentials; access credentials also expire on their own within an hour.

ACOS (Ayzeo Content Opportunity Score) is a 0-100 composite score combining 9 weighted dimensions -- striking distance, CTR gap, impression volume, 30-day momentum, position trend, content gap, brand filter, long-tail classification, and traffic uplift -- to rank which GSC queries deserve a new content page. The get_gsc_opportunities MCP tool returns top-scoring queries with the full dimension breakdown plus weights, so the AI assistant can articulate exactly why a query is a good opportunity rather than just handing back a number.

Yes. The create_content_page_from_query tool triggers Ayzeo's content generation pipeline for a given query and returns the new page id plus generated SEO elements and edit URL. It counts against the standard 5-per-day content-page quota per project and requires an active paid subscription. In practice, an AI assistant will typically chain get_gsc_opportunities -> get_ga_ai_traffic -> create_content_page_from_query to close the full gap-to-draft loop. Triggering content generation requires the editor role or above on the project.

Tools that depend on those integrations return a structured error with codes like gsc_not_connected, gsc_sync_pending, ga_not_connected, or ga_sync_pending -- along with a setupUrl pointing at the relevant Ayzeo settings page. Your AI assistant can read this and tell you exactly how to connect the missing integration, rather than failing silently.

Yes. The connection uses OAuth 2.1 with PKCE; credentials are short-lived, rotate automatically, are bound to the Ayzeo MCP server (useless anywhere else), and are stored only as cryptographic hashes on Ayzeo's side. Access follows your project membership and roles, plan gating is enforced per request, all traffic runs over HTTPS, and rate limiting prevents runaway usage. Disconnecting the connector revokes that client's credentials, and access credentials expire on their own within an hour.