Answer
Notion MCP doesn't work for guests — here's why and what to do
Notion's MCP server blocks guest users, so clients and contractors on guest seats can't query your workspace through their AI agent. Here's the cause, the open issue, and the workarounds.
The short answer
Notion's MCP server does not work for guest users — guests get blocked from connecting, so a client or contractor on a guest seat can't query your Notion content through Claude, ChatGPT, or any MCP client. This is a known, long-open limitation (tracked in the makenotion/notion-mcp-server repo). The workarounds are: upgrade the person to a full member (costs a seat and over-grants access), build a custom proxy, or use a tool whose MCP is designed for external collaborators — a role-aware MCP over private docs that works for guests within their permissions.
If you've tried to let a client or contractor query your Notion workspace through an AI agent and hit a wall, you're not doing it wrong — Notion's MCP server blocks guest users. This is one of the most common surprises teams hit when they try to extend docs-as-AI access to the people outside their company. Here's exactly what's happening and what your options are.
The problem
Notion's MCP server authenticates and authorizes full members fine. Guest accounts — the seats agencies use for clients, freelancers, and contractors — are effectively locked out of the MCP connection flow. So the workflow you wanted ("my client asks their Claude a question and it answers from the shared docs") doesn't work for the very people it was meant for.
This isn't a fringe edge case. It's tracked in a long-standing open issue on Notion's MCP server repo (#227), and it's sat there long enough to be treated as a structural limitation, not an imminent fix.
Why it matters for agencies and teams
The entire point of giving a client AI access to docs is that the client is external. They're guests by definition. If guests can't use the MCP, the feature only works for your own employees — who already have access to everything anyway. The interesting, modern use case is exactly the one Notion's MCP doesn't support.
Your options today
1. Upgrade the guest to a full member
It works, but it's the wrong trade: you pay for another member seat, and a full member usually has far more visibility than a client should. You've solved MCP access by over-granting access. Not great for a client relationship.
2. Build a custom proxy
You can stand up your own service that authenticates the client and proxies queries into Notion's API with scoping you control. This is real engineering work to build and maintain, and you're reimplementing access control Notion didn't give you.
3. Use a tool with guest-capable, role-aware MCP
The clean fix is a documentation tool whose MCP is designed for external collaborators. Miradorly's MCP works for invited guests, scoped to their role (viewer / commenter) and project, secured with OAuth 2.1 + PKCE, and read-only by design. Files matched by .docignore are never indexed, so a guest's agent can never surface internal content.
# A client connects their agent; results are scoped to their account
claude mcp add miradorly https://mcp.miradorly.com/<workspace>Comparison
| Notion MCP | Miradorly MCP | |
|---|---|---|
| Works for guest users | ❌ | ✅ |
| Per-user role-aware scoping | ❌ | ✅ |
| Private docs | ⚠️ member-only | ✅ |
| Respects an ignore file | — | ✅ .docignore |
| Read-only by design | — | ✅ |
If you're committed to Notion
If Notion is your source of truth and you can't move, the only reliable path today is upgrading the person to a member and tightening their page-level permissions manually — accepting the seat cost and the access trade-off. There's no supported guest-scoped MCP.
If your docs are (or could be) in git
If the documentation you want to share already lives — or could live — as markdown in a repo, a role-aware MCP over that repo sidesteps the whole problem. The guest connects, the agent answers from the docs they're allowed to see, and nothing internal leaks. That's the model Miradorly is built around, and it's the difference between "AI access for employees only" and "AI access for the clients who actually needed it."
Frequently asked questions
Why doesn't Notion's MCP work for guests?
Notion's MCP authorization flow doesn't support guest-level accounts the way it supports full members, so guest users are effectively blocked from connecting. It's a documented limitation with an open issue in Notion's MCP server repository (#227).
Can I make Notion MCP work for a client?
Only by upgrading them to a full member seat, which costs money per user and usually grants more access than a client should have. There's no clean guest-scoped MCP path in Notion today.
What's the alternative for client AI access to docs?
A role-aware MCP server that's built for external collaborators. Miradorly's MCP works for invited guests, scoped to their role and project, secured with OAuth 2.1 + PKCE, and respects .docignore so internal files are never returned.
Is this a temporary Notion bug or a design limitation?
It's been open long enough to be treated as a structural limitation rather than a quick bug fix. If guest MCP access is essential to your workflow now, relying on Notion to fix it is risky.