Ezeo connector

Anyone with an Ezeo login can add Ezeo to an AI assistant from that assistant's settings, sign in once, and then ask things like "how did EquipMaxx do in Search Console this month?". It is a remote MCP server; there is nothing to install.

Every tool runs as the signed-in user, so you see exactly the projects you see in the Ezeo dashboard. Unmeasured figures come back as null with a note, never as 0. The read tools call no paid API, so a question costs Ezeo nothing: your own assistant plan pays for the model.

Use this URL in every assistant:

Skip the manual steps: the connect guide has one-click setup for Claude, ChatGPT, Cursor, VS Code and terminal agents.

Every assistant uses the same server URL. Find yours below; the steps are the ones the connect guide shows.

Verified means we signed in and got answers end to end: Claude, Claude Code, ChatGPT, OpenAI Codex and Cursor, as of 2026-10-15. The others are set up from each assistant's own documentation and have not been tested yet, so a step may differ. Gemini CLI is not verified: Google no longer lets personal accounts sign in to it, so it needs a Gemini API key or Vertex AI.

https://ezeo.ai/mcp

https://ezeo.ai/mcp

https://ezeo.ai/mcp

https://ezeo.ai/mcp/openapi.json

{
  "mcpServers": {
    "ezeo": {
      "url": "https://ezeo.ai/mcp"
    }
  }
}

{
  "servers": {
    "ezeo": {
      "type": "http",
      "url": "https://ezeo.ai/mcp"
    }
  }
}

{
  "mcpServers": {
    "ezeo": {
      "serverUrl": "https://ezeo.ai/mcp"
    }
  }
}

claude mcp add --transport http ezeo https://ezeo.ai/mcp

[mcp_servers.ezeo]
url = "https://ezeo.ai/mcp"

gemini mcp add --transport http ezeo https://ezeo.ai/mcp

When the assistant asks you to sign in, use your Ezeo login. You land on an Ezeo page that shows the account you are signed in as and the permissions requested. Choose Allow to approve, or Deny.

The assistant then works as you. Sign-in runs on Ezeo's own sign-in service, so an assistant may briefly show a different address than the URL you pasted.

Once connected, ask in plain language. For example:

The connector offers 16 tools. All are read-only except request_articles, which spends content allowance and always asks first.

list_projectsadd_siteget_setup_statusget_connection_stepsget_project_overviewget_keyword_rankingsget_quick_winsget_weekly_readoutlist_articlesget_content_ideasget_sync_statuslist_waiting_runslist_cro_hypothesesget_cro_auditget_variant_briefrequest_articles

Each article uses one unit of the project's content allowance, the same as the dashboard button and "ezeo articles request". The tool always takes two calls.

1. 01
   Without a confirmation code it spends nothing. It returns a preview, the allowance left and an 8-character code, or refuses when automation is off or you cannot see the project configuration.
2. 02
   With the code it starts the runs and reports what started, what was already running this week and what was skipped.

The code stops an assistant from spending in a single step, from using a preview older than about 20 minutes, or from changing the count after you agreed. The assistant is told to show you the preview and wait for an explicit yes. Who may spend and whether allowance remains are decided by the database, not by the code.

• You only see projects your Ezeo account can already see. Client accounts see a project once it has been granted to them.
• Starting a site or CRO audit is not exposed. You can read the latest CRO audit, but not run a new one.
• request_articles is the only tool that writes. There are no other write tools.
• There are no personal API keys. An agent that cannot open a browser to sign in cannot connect.
• Ezeo is not listed in the Claude or ChatGPT public directories; you add it as a custom connector.