Notion MCP connector
Notion brings AI tools to Elaichi for pages, databases, comments and users. Connect the workspace once, then Claude, ChatGPT, Cursor, Microsoft Copilot or any MCP client reaches only the pages each person is already allowed to open.
- OAuth or API key
- Free 14-day trial
- No credit card
Summarize comments added to the product spec page this week.
Working in Notion with Elaichi
-
List all Notion users
-
Get single Notion user by ID
-
List all Notion databases
How to connect Notion to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Notion MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Notion MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Notion MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Notion MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Notion MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Notion to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with Notion through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Notion is logged.
-
Engineering
Answer wiki questions without opening Notion
Ask which specs changed this week, or what a design doc concluded, and the answer comes back with the page it came from. Reading is all this needs, so the agent doing it cannot change a thing.
-
Product
Find the gaps in a roadmap
Ask which roadmap entries have no owner, or which shipped last month with nothing written up. The Monday morning scan somebody used to do by hand, answered in a sentence.
-
Marketing
Draft into the right place, every time
Ask for a meeting note or a campaign brief and it lands in the team's own database. You can fix the destination in advance, so nothing arrives in the wrong corner of the workspace.
-
Support
Catch up on a thread before a review
Comments are where decisions actually get made and where nobody reads back. Ask for the argument so far in a paragraph, without granting anything that can write.
-
People Ops
Give each team its own corner
One Notion connection, a different set of tools per team. Engineering reaches the engineering wiki, People Ops the handbook, and nobody browses into a corner that was never theirs.
-
Legal
Keep legal holds in Legal's hands
Notion's legal hold controls sit in the same list as the content calendar and look like ordinary admin. Keep them available to Legal and unavailable to everybody else.
Try asking
- “Summarize comments added to the product spec page this week.”
- “List Notion pages in the roadmap database missing an owner.”
- “Create a meeting notes page in the team database.”
What connecting Notion gets you
6 screens from Elaichi, each doing one job for your Notion account.
Ask Elaichi to work across your apps.
Summarize comments added to the product spec page this week.
List Notion pages in the roadmap database missing an owner.
Create a meeting notes page in the team database.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask in plain language, read live Notion pages.
Three starter prompts pull answers straight from Notion pages, databases and comments.
Copy the endpoint
AI apps
One Notion endpoint, governed for the whole org.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, no SDK and no shared key.
Tool catalog
122 Notion tools land ready to call.
Pages, databases, comments and users are covered without writing custom code.
Toolboxes
Each team gets its own Notion toolbox.
Curate one toolbox per team so people see only relevant Notion tools.
Shared connections
Teammates use Notion without seeing a token.
See who connected each Notion account and which teams and members share it.
Audit log
Answer who changed which Notion page.
Every call records time, person, action, type and the Notion resource touched.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Notion digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch pages
Notion
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Notion
Queued
Automations
A schedule drafts your Notion digest nightly.
Six steps fetch pages, group them, draft a digest, await approval, post to Notion.
Notion health
Refreshed 4 minutes ago · every 15 minutes · from the pages collection
Pages
1,284 ↓ 12%
Databases
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Pages created
Last 14 days
By team
Share of activity
Engineering wiki 34%
Product roadmap 27%
Marketing content 21%
People handbook 18%
Collections and dashboards
Notion page activity counted, not summarized.
Four metrics, 14 days of pages created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Notion
All three can connect Notion to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Notion tools | Allow or restrict single Notion tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Notion call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
Notion tools for your AI agents
122 tools are ready to call through Elaichi's MCP endpoint the moment you connect Notion, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Notion to Claude?
Two steps. In Elaichi, add Notion and sign in to your Notion workspace, choosing which pages and databases to share on Notion's own consent screen. Then in Claude open Customize, then Connectors, press Add, and paste https://api.elaichi.ai/mcp as the MCP server URL. There is no client ID or secret to generate, and you only do the Claude half once, however many apps you add later.
Does Notion work with ChatGPT and Cursor as well as Claude?
Yes. The same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Notion once in Elaichi and it shows up in whichever client each person prefers, so nobody re-does the setup per tool.
What can an AI agent actually do with my Notion?
Find and read pages, draft new ones, update page properties, work through database rows, and read or write comments. In practice people ask it to write up a meeting, keep a project database current, or pull together what a handful of scattered pages say. It works on the pages you share, using your own Notion access.
Does connecting Notion give the AI my whole workspace?
No. Notion's own consent screen decides this: you pick the pages and databases the connection can see, and everything you do not pick stays invisible. Inside Elaichi you can narrow it further, down to specific people or specific actions, and anything you restrict still appears in Elaichi's tool search, flagged as restricted, but the AI cannot run it, whatever the prompt says.
Can I let people read Notion without letting the AI change anything?
Yes. Restrictions work per action, so you can allow the Notion read tools and restrict create, update and delete for a person or a role. A restricted tool still appears in Elaichi's tool search, flagged as restricted, but Claude or ChatGPT cannot run it, whatever the prompt says.
What happens to a Notion connection when someone leaves?
Offboard them in Elaichi and their access stops immediately, including anything they had connected through a client. A shared Notion connection keeps working for everyone else. To remove Notion entirely, disconnect it once in Elaichi; nobody has to go tidy their own Claude or ChatGPT settings.
Does the Notion MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Notion is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Notion?
Yes. Both let Claude, ChatGPT or Cursor use Notion. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Notion call.
How is Elaichi different from Composio for Notion?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Notion: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Notion in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot