Search Notion the way your team does.
Notion's own MCP server, passed through per business unit. Your agent works with the permissions of the person who signs in and gets what the API doesn't have.
- Vendor MCP · passed through as is
- Coverage: complete
- 18 tools (per vendor) · 9 of them make changes
Read and change.
Your agent works with exactly the permissions of the connected account. Read tools are quick to enable. Tools that change data stay off until you explicitly turn them on.
What your agent can read
- Search, with Notion AI also across connected sources such as Slack, Google Drive or Jira.
- Pages and databases as Markdown, queries and, with Notion AI, SQL across several databases.
- A page's backlinks and version history.
- Comments, people, teamspaces, calendar and meeting notes.
What your agent can change
- Create, update, move and duplicate pages and databases.
- Suggest edits for a person to accept instead of changing directly.
- Write comments and create calendar events.
Only once you enable it, per agent and per tool. If you want, a person also approves each action before it runs.
How teams use Notion MCP.
Marketing, sales and RevOps run these as recurring routines or on request.
- 01
Who decided what?
A question about an account comes up- Search Notion and connected sources
- Read the hits
- Sum up the answer with sources
ResultAn answer from Notion, Slack and Drive, with links to where it came from.
- 02
Suggest instead of overwrite
A playbook is out of date- Read the page and its version history
- Draft new sections
- Submit them as suggested edits
ResultThe team accepts or rejects the changes in Notion.
Built-in safeguards
- Your agent can't start or steer Notion AI agents through the hub. They would run outside its rules and spend Notion AI credits.
- Notion itself marks deleting as destructive, and the hub asks for approval.
- If you want, changes only run after a person approves them, for example the team lead: in the Data Hub, in Slack or via a link. On top of that, each agent has daily and hourly limits.
- Guardrails for every agent: deletes and changes to more than 10 records need approval by default, an emergency brake kicks in on a run of deletes, and you can set your own rules per tool.
- Each connection has an access level: Read, Write or Admin. Where the vendor allows it, the Data Hub only requests the permissions for that level.
- Credentials are stored encrypted in the Data Hub, and the agent never sees them. Every call is logged.
What it can't do
- Beta. Search across connected sources, SQL and suggested edits need Business or Enterprise and Notion AI.
- After 30 days without use you have to reconnect.
Notion decides which tools exist through its own MCP server. The hub passes on everything that server offers and refreshes the list every 24 hours.
Connect Notion MCP to your agents.
In 30 minutes, we'll show you the Data Hub with your own tools.