Notion MCP server, with a policy gate.
Connect Notion to Claude, Cursor, and any MCP client through one URL. Gentkey proxies the official Notion MCP server, keeps your OAuth token encrypted server-side, and gates writes behind a grant you control.
https://app.gentkey.com/mcpclaude.ai (web & mobile) · Claude Code · Cursor · any MCP clientWhat’s free, what needs a grant.
Reads: Notion's tools aren't curated into a free-read set yet — every tool, search included, sits behind the grant.
Writes: Grant mcp-notion.write and the connector opens; revoke it any time and the next call is denied.
Gentkey proxies the official Notion MCP server (https://mcp.notion.com/mcp) — you get the vendor’s own tools, with custody, gating, and audit added in front.
| Grant | What it governs |
|---|---|
mcp-notion.write | Every tool the official Notion server exposes — page and database edits, comments, and reads too, until a curated read set lands |
Connect once, use everywhere.
Sign in at gentkey.com, add Notion (oauth), then point each client at your endpoint. Every client completes a standard OAuth flow and lands in your Gentkey — your connections, nobody else’s.
claude.ai (web & mobile)
- Settings → Connectors
- Add custom connector
- Paste
https://app.gentkey.com/mcpand finish the OAuth prompt
Claude Code
claude mcp add --transport http \
gentkey https://app.gentkey.com/mcpCursor
// .cursor/mcp.json
{
"mcpServers": {
"gentkey": { "url": "https://app.gentkey.com/mcp" }
}
}Things agents do with Notion here.
- Find the meeting notes from last Tuesday's product sync.
- Add a row to the Content Calendar database for next Friday.
- Summarize everything in the Q3 Planning page.
- Create a page under Projects titled 'Onboarding revamp' with a task checklist.
Custody, gating, and audit — built in.
The model never sees a credential
Your Notion token is encrypted at rest and injected server-side at call time. Your stored credential never enters a context window.
Writes need a grant
Anything that changes state needs a capability you granted explicitly — revoke it and the next call is denied.
A trail you can act on
Every decision is attributed to the agent that made it — allowed, denied, or denied by constraint.
Fair questions.
Does connecting Notion expose my whole workspace to every agent?
Until you grant mcp-notion.write, agents can't touch Notion at all — the connector's tools aren't curated into a free-read set yet, so the grant is the single switch for the whole connector, and the OAuth token itself never leaves Gentkey's server.
What happens when an agent calls a Notion write tool it hasn't been granted?
The call is denied at the gateway — nothing reaches Notion — and the denial is recorded in the audit log along with the grant that would have authorized it, so you can decide deliberately instead of finding out later.
Where are my credentials stored?
Encrypted at rest (AES-256-GCM) on Gentkey's server and injected server-side at call time. No credential you store with Gentkey ever enters a model's context window or an agent's config file.
Can I use this from claude.ai's free plan?
Yes — and it's the strongest case for a gateway: free claude.ai accounts currently get a single custom connector, so pointing that one slot at Gentkey puts every connector you've linked behind it.
How do I revoke an agent's access?
Revoke the grant (the next write is denied) or revoke the agent's tokens entirely in one click. Other agents and their grants are untouched — no shared key to rotate.
Is Gentkey affiliated with Notion?
No. Gentkey is an independent MCP gateway. Trademarks belong to their owners; where an official Notion MCP server exists, Gentkey proxies it and adds custody, gating, and audit on top.
Often connected together.
Cut Notion a smaller key.
Sign in, connect Notion, and grant your first scoped capability in under a minute.