Ayzeo MCP 2.0: Sign In, Connect, Done — No More Tokens

Book a Demo

Walk through the platform with Aykut, our founder.

Add one URL, sign in with your Ayzeo account, and your AI assistant can work across your whole project portfolio.

1. What's New

When we launched the Ayzeo MCP server earlier this year, the setup looked like every early MCP integration did: create an API token in your project settings, copy it before it disappears, paste it into a JSON config file, restart your client, repeat per project. It worked — but it was developer-grade plumbing for what should be a consumer-grade moment.

Today that plumbing is gone. The Ayzeo MCP server now runs on OAuth 2.1, the same authorization standard behind “Sign in with Google”. The new endpoint is:

https://ayzeo.com/mcp/v2

Add that URL as a connector in ChatGPT, claude.ai, Claude Desktop, or Claude Code. Your browser opens, you sign in with your normal Ayzeo account, you approve access once — and you're connected. No token, no config-file surgery, no secrets sitting in plaintext on your laptop.

"The best integration setup is the one you don't have to explain. Add a URL, sign in, done."

2. No More Token Copy-Paste

The token flow had three problems we wanted gone:

The OAuth connection solves all three at once. Sign-in happens in the browser against Ayzeo directly (your password never touches the AI client), the credentials the client ends up holding are short-lived and rotate automatically in the background, and a single approval covers your whole project portfolio.

3. Connecting in Under a Minute

The flow is the same everywhere: add the URL, sign in, approve.

Exact click paths, client-ID hints, and troubleshooting live in the setup guide.

Then ask your first question: "List my Ayzeo projects." The assistant returns every project you can access, with your role and a dashboard link — and from there you name the project you want to dig into.

4. One Connection, Your Whole Portfolio

This is the change agencies asked for most. The connection is bound to you, not to a project. Whatever projects you're a member of — your own, your organisation's, your clients' — are reachable through the same connection, governed by the same roles you have in the dashboard.

Plan handling follows a simple principle: the owner pays, the team works. A project is available over MCP when the organisation that owns it has an active Pro or Enterprise plan (trials count). Team members don't need their own paid plan — if you're on a paying organisation's project, you're covered. Your assistant sees exactly what you see, nothing more.

That unlocks genuinely new workflows: “ Which of my projects has the weakest ChatGPT presence?” is now one question in one conversation — not a tab-switching exercise across ten configured servers.

5. Security Under the Hood

For the security-minded (and the security teams doing vendor review), the new connection is a straight upgrade:

6. Rollout & What's Next

Here's what's live and what's next:

Existing token-based connections keep working — nothing breaks today. But new connections use the sign-in flow, and we recommend switching when convenient.

7. Frequently Asked Questions

Q: What changed with MCP 2.0?
A: Authentication and scope. Connecting now uses OAuth 2.1 — you add https://ayzeo.com/mcp/v2 to your AI client, sign in with your Ayzeo account in the browser, and approve access once. No more API tokens to create and paste. And one connection covers every Ayzeo project you're a member of, instead of one token per project.
Q: Which AI clients are supported?
A: ChatGPT (via Developer mode until the app-directory listing is live), claude.ai and Claude Desktop (native custom connectors — no bridge needed anymore), and Claude Code. Cursor, Windsurf, and Gemini CLI are on the roadmap; they require automatic client registration, which Ayzeo doesn't offer yet.
Q: Do my existing token-based MCP connections still work?
A: Yes. Nothing breaks — existing connections keep authenticating exactly as before, and project API tokens continue to power the WordPress plugin. New MCP connections use the OAuth flow, and we recommend switching when convenient: less setup, all projects at once, and no secret in a config file.
Q: Who can connect, plan-wise?
A: 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.
Q: How do I revoke access?
A: Disconnect the connector in your AI client — its stored credentials are revoked against Ayzeo's standard OAuth revocation endpoint, and access credentials expire on their own within an hour regardless. Each client you connect holds its own credentials, so disconnecting one never affects the others.
Q: Is this more secure than the token setup?
A: Yes, on every axis. Your password never touches the AI client, the client holds only short-lived credentials that rotate automatically, Ayzeo stores credentials only as cryptographic hashes, and replayed credentials trigger an automatic revocation of the whole connection. Long-lived plaintext secrets in config files are gone.
Q: Can my whole team use it, and what can each member do?
A: Yes — every member connects with their own account, and tool access follows dashboard roles: viewers read data, while triggering analyses, prompt runs, and content generation requires the editor role or above on the project. Access checks run per call, so role changes take effect immediately.

Key Takeaways

If you have an Ayzeo account, you're sixty seconds from a connected assistant: open your AI client, add https://ayzeo.com/mcp/v2 as a connector, sign in, and ask it to list your projects. If you're new to Ayzeo, the Pro trial covers everything you need to try it — including MCP access for your whole team.