Using Ayzeo

Connect AI Clients to Ayzeo (MCP Server)

Connect ChatGPT, claude.ai, Claude Desktop, or Claude Code to Ayzeo via the Model Context Protocol (MCP): add one URL, sign in with your Ayzeo account, and work across all your projects — no tokens to copy.

Ayzeo Team July 13, 2026 8 min read

Key Takeaways

  • Ayzeo exposes a remote MCP server at https://ayzeo.com/mcp/v2 — add that one URL to your AI client and you're connected
  • No tokens, no copy-paste. You sign in with your Ayzeo account in the browser (OAuth) and approve access once — the connection takes care of itself from then on
  • One connection covers all your projects. Your assistant starts by listing the Ayzeo projects you can access, then works on the one you name
  • Works today in ChatGPT (developer mode), claude.ai, Claude Desktop, and Claude Code — store listings and more clients are on the way

What is the Ayzeo MCP Server?

The Model Context Protocol (MCP) is the open standard that Anthropic, OpenAI, and Google are converging on for letting AI assistants call external tools and data sources. Ayzeo's MCP server puts your full GEO data layer directly inside any MCP-capable AI client — so instead of switching to the Ayzeo dashboard to check opportunities, you ask your assistant in natural language and it fetches the answer.

Ask "based on our ACOS, what's the next best content page to create for acme.com?" and your assistant will query the top-scoring GSC opportunities, cross-reference GA4 to see which landing pages already convert from AI referrals, check whether a dedicated content page already exists, and recommend one with the 9-dimension score breakdown as justification. If you agree, it can call Ayzeo's content generator directly — all without leaving the chat.

Connecting works the way you already know from other AI integrations: you add the server, a browser window opens, you sign in with your Ayzeo account, and you approve access. One connection gives your assistant access to every Ayzeo project you're a member of — no per-project setup.

Prerequisites

  • An Ayzeo account. Anyone can connect — the projects your assistant can work on are those whose owner has an active Pro or Enterprise plan (trials count). If you're a team member on a paying organisation's project, you're covered by the owner's plan.
  • A supported AI client (see supported clients).
  • Optional but recommended: connect Google Search Console and Google Analytics for full tool coverage. Tools that need these return a clear setup URL if they're missing, so nothing breaks if you skip this step.

Two Ways to Connect

Add manually (available now)

Add https://ayzeo.com/mcp/v2 as a remote MCP server in your client's connector settings, sign in, done. The step-by-step guide below covers each client.

Install from the store (coming soon)

Ayzeo listings for the ChatGPT app directory and Claude's connector directory are in preparation. Once live, connecting will be a single click from inside your AI client — no URL needed.

Setting It Up

1

Add the Ayzeo server to your AI client

In your client's connector or MCP settings, add a new remote server with the URL https://ayzeo.com/mcp/v2. That's the only thing you need to enter — there is no token or secret to copy. Exact click paths per client are in the supported clients section below.

2

Sign in and approve access

Your browser opens an Ayzeo page. Sign in with your normal Ayzeo account (if you aren't already), review what the AI client is asking for, and click Approve. You only do this once per client — afterwards the connection renews itself automatically in the background.

3

Ask your first question: list your projects

Start every new session the same way: "List my Ayzeo projects." The assistant calls list_projects and returns every project you can access, with your role and a dashboard link. From there, name the project you want to work on — "For acme.com, …" — and the assistant scopes all further tool calls to it.

Working across several Ayzeo projects? That's the default now. One connection covers your whole portfolio — agencies included. There's nothing extra to configure per project; just tell the assistant which project a question is about.

Supported AI Clients

The connection uses OAuth over Streamable HTTP — the standard for remote MCP servers. These clients are supported today:

claude.ai & Claude Desktop Easiest

Open Settings → Connectors → Add custom connector, name it Ayzeo, and paste the URL:

https://ayzeo.com/mcp/v2

If the advanced settings ask for an OAuth client ID, enter claude-web and leave the secret empty. Click Connect — the Ayzeo sign-in page opens, you approve, and the connector shows as connected. Connectors sync between claude.ai and Claude Desktop, so you set this up once for both.

Claude Code CLI

One command adds the server. Use --scope user to persist it across projects, or leave it off for project-local.

claude mcp add --transport http --scope user ayzeo https://ayzeo.com/mcp/v2

On the first request Claude Code detects that the server requires sign-in and opens your browser for the OAuth flow (you can also trigger it with /mcp inside a session). Verify with claude mcp list; remove with claude mcp remove ayzeo.

ChatGPT (developer mode)

Until the Ayzeo listing in the ChatGPT app directory is live, custom MCP connectors require developer mode, available on Plus, Pro, Business, Enterprise, and Edu plans on the web:

  • • Enable it under Settings → Apps → Advanced settings → Developer mode
  • • Click Create app, name it Ayzeo, and set the MCP server URL to https://ayzeo.com/mcp/v2
  • • Choose OAuth as the authentication method; if asked for a client ID, enter chatgpt (no secret)
  • • Complete the sign-in when ChatGPT opens the Ayzeo authorization page

Once the store listing ships, this whole section collapses to a single click on the Ayzeo entry.

Cursor, Windsurf, and Gemini CLI handle OAuth MCP servers via automatic client registration, which Ayzeo doesn't offer yet — support for these clients is on the roadmap. gemini.google.com has no public MCP client yet.

The Tools

Your assistant discovers the available tools automatically via MCP's tools/list handshake — no manual wiring needed. Every project-scoped tool takes a projectId, which the assistant picks up from the project list (list_projects and the global get_geo_recommendations take none). Reading data works for every member role; triggering analyses, prompt runs, and content generation requires the editor role or above on the project.

Projects

  • list_projects — every Ayzeo project you can access, with your role (owner/admin/editor/viewer) and dashboard link — the entry point for every session

Project & Analysis

  • get_project_info — name, domain, plan tier, dashboard URL
  • get_analysis_results — latest advanced website analysis (SEO health, schema, AI readiness)
  • run_website_analysis — trigger a fresh site audit
  • get_project_stats — aggregated citation and mention counts by model

GEO Playbook

  • get_geo_recommendations — Ayzeo's curated, versioned list of GEO tactics, each tagged with the prompt intents, AI engines, and confidence it applies to (global — not project-specific)

AI Visibility

  • list_prompts — saved prompts with latest runs per model (answer, sentiment, mentioned brands, cited URL)
  • run_prompt — re-run a saved prompt (enables before/after comparison)
  • run_ai_visibility_check — ad-hoc AI search for any query
  • get_citation_history — recent per-model citation results
  • get_brand_mentions — aggregated brand mentions with sentiment

GSC & GA Data

  • get_gsc_opportunities — top-N high-ACOS queries with full 9-dimension breakdown (headline tool)
  • get_gsc_queries — paginated raw GSC data for custom filtering
  • get_ga_ai_traffic — GA4 traffic by AI referrer source with top landing pages

Content

  • get_content_pages — list already-generated pages with edit URLs
  • create_content_page_from_query — generate a new AI-optimised page for a query (counts against 5/day quota)

Example Prompts to Try

Because one connection spans all your projects, the pattern is always: discover first, then drill down. Start a session with the project list, or name the project directly in your question.

"List my Ayzeo projects and tell me which one had the most recent citation activity."

"For acme.com, show me my top 10 ACOS opportunities and explain why the number-one query scored so high."

"Which of acme.com's prompts have zero brand mentions in ChatGPT? What do competitors rank for those prompts?"

"Cross-reference acme.com's top ACOS opportunities with its GA AI-referrer traffic. Pick the single best page to create and generate it."

"Compare AI visibility across all my projects: which project has the weakest ChatGPT presence, and what would you fix first?"

Troubleshooting

The project list comes back empty

list_projects returns a message explaining which of three cases applies: you aren't a member of any project yet (create one in the dashboard or ask a teammate to invite you), you own projects but none of them are on a plan that includes MCP access (upgrade from the pricing page — a Pro trial is enough), or you're a member of other people's projects and none of those owners have an active Pro or Enterprise plan (ask the project owner to upgrade).

The sign-in window loops or the client says "authorization failed"

Finish the flow in the same browser where you're signed in to Ayzeo. If the consent page sat open for more than a few minutes before you clicked Approve, the request expires — remove the connector from the client and add it again. Also verify the URL is exactly https://ayzeo.com/mcp/v2 (no trailing slash).

The connection worked, then stopped

Connections refresh themselves automatically, but they end when access is revoked — for example after disconnecting the connector, or when Ayzeo's security checks detect the connection's credentials being replayed from somewhere else and shut the whole connection down as a precaution. Reconnecting is the fix: remove and re-add the connector, sign in, approve.

gsc_not_connected / ga_not_connected / *_sync_pending

The tool you invoked requires a connected integration on that project. The error payload includes a setupUrl — open it to finish the setup, then retry. After connecting, allow a few minutes for the first sync to populate data (GSC imports up to 90 days on first sync).

"Rate limit exceeded"

The limit is 100 requests per 5 minutes per connection. An aggressive agent loop can burn through this. Wait 5 minutes for the window to reset, or rein in the loop — asking the assistant to batch its analysis instead of calling tools one query at a time goes a long way.

Assistant can't see the tools

Verify the endpoint URL is exactly https://ayzeo.com/mcp/v2, then disconnect and reconnect the connector so the client redoes the handshake. In ChatGPT, confirm developer mode is still enabled and the app's tools were scanned. In Claude clients, check the connector shows as "Connected" in Settings → Connectors.

Security & Limits

  • The connection uses OAuth 2.1 with PKCE — the current industry standard. Your Ayzeo password never touches the AI client; the client only ever holds short-lived, automatically rotating credentials.
  • Credentials are stored only as cryptographic hashes on Ayzeo's side and are bound to the Ayzeo MCP server — they can't be replayed against any other service.
  • Access follows your project membership and role. The assistant sees exactly the projects you see, nothing more — and only while the owning organisation has an active plan.
  • Revoke anytime: disconnect the connector in your AI client and its stored credentials are revoked against Ayzeo's standard OAuth revocation endpoint. Access credentials also expire on their own within an hour.
  • Rate limit: 100 requests per 5 minutes per connection. All traffic runs over HTTPS; the server is stateless between requests.
  • create_content_page_from_query counts against the 5-per-day content-page quota per project.

Frequently Asked Questions

Q: Does the MCP server work across multiple Ayzeo projects at once?

A: Yes — natively. One connection covers every project you're a member of. Ask for the project list, then name the project each question is about. You can even ask cross-project questions ("which of my projects has the weakest ChatGPT presence?") in a single conversation.

Q: Can I connect more than one AI client?

A: Yes. Each client (ChatGPT, claude.ai, Claude Code, …) goes through its own sign-in and gets its own grant. Disconnecting one client never affects the others.

Q: I'm a team member without my own paid plan — can I use this?

A: Yes. Connecting is open to every Ayzeo account. What you can access follows the projects: if the organisation that owns a project has an active Pro or Enterprise plan (trials count), every member of that project can work on it over MCP — the owner's plan covers the team.

Q: I set up an MCP connection with an API token earlier — does it still work?

A: Existing token-based connections keep working — nothing breaks. New connections use the sign-in flow described here, and we recommend switching when convenient: it's less setup, covers all your projects at once, and no secret ever sits in a config file. Project API tokens themselves remain in place for the WordPress plugin.

Q: Can I see which MCP tools the assistant called?

A: Most AI clients (ChatGPT, claude.ai, Claude Code) surface tool calls inline in the conversation. You can inspect each call, its arguments, and the returned payload.

Q: Will the assistant hallucinate data?

A: All tools return real Ayzeo data — the MCP server never generates numbers. The assistant's narration ("this query scored 87 because...") is derived from the actual dimension scores returned by get_gsc_opportunities. If the assistant ever cites a number you can't find in the data, ask it to re-run the tool call with the filter you care about.

Q: Is there usage metering?

A: MCP calls are limited to 100 requests per 5 minutes per connection. Content-page generation counts against the project's 5-per-day content quota. AI-visibility runs (run_ai_visibility_check, run_prompt) count against the project's daily AI-visibility-check quota, which depends on the owner's plan.