Give every agent a safer way into Notion
Your workspace mixes durable knowledge with plans that are still moving. Route Notion through AIP and each agent gets only the search, page, database, or comment tools its job requires — while every client keeps using the same managed connection.
What your agent can do
Notion publishes purpose-built tools instead of exposing raw REST endpoints. The read highlights below cover discovery and structured queries; the write highlights cover the page, database, view, and discussion changes most teams delegate to agents. AIP applies Allow, Confirm, or Hide after discovery.
| Tool | What it does | Access |
|---|---|---|
| notion-search | Search accessible Notion content and, when the workspace permits it, connected sources. | read |
| notion-fetch | Fetch a page, database, data source, saved view, or the connected workspace identity. | read |
| notion-query-data-sources | Run a saved view or structured query across one or more Notion data sources. | read |
| notion-query-meeting-notes | Find meeting notes available to the signed-in user when the workspace plan supports it. | read |
| notion-get-comments | Read page-level, block-level, inline, resolved, and unresolved discussions. | read |
| notion-get-users | Resolve workspace members and guests to the IDs used in people properties and filters. | read |
| notion-create-pages | Create one or more pages, optionally using database templates, icons, covers, or draft mode. | write |
| notion-update-page | Change page properties or content, apply a template, and manage its icon or cover. | write |
| notion-create-comment | Add a page comment, comment on selected content, or reply to a discussion. | write |
| notion-move-pages | Move pages or databases under a different parent in the connected workspace. | write |
| notion-create-database | Create a database with its first data source, properties, and initial view. | write |
| notion-create-view | Add a table, board, calendar, timeline, gallery, form, chart, map, or dashboard view. | write |
Notion's hosted MCP inventory changes with workspace plan and enabled products. This table highlights stable, documented tools rather than presenting a plan-dependent list as complete.
Capability snapshot: 1 September 2026 · provider source
Search first, then decide whether to write
Notion work often begins with an ambiguous title: “the launch plan,” “last week’s research,” or “the customer tracker.” A useful agent searches, fetches the strongest matches, checks their paths and last-edited timestamps, and only then creates or updates anything. Splitting those steps into visible tools lets you keep a research agent on read operations while a documentation agent can propose a page change behind confirmation.
This boundary matters more than a single OAuth toggle. In the
AIP control room, notion-search can be allowed for one agent,
notion-update-page set to Confirm for another, and database creation hidden
everywhere else. Browse the integration hub to combine Notion
with the systems that supply the source material.
Connect the hosted Notion MCP through AIP
- Open the AIP dashboard, choose Notion, and finish Notion’s OAuth consent flow for the workspace you intend to expose.
- Add the connected account to an agent. Review the discovered tools and set each one to Allow, Confirm, or Hide instead of accepting one blanket mode.
- Give Claude, Codex, Cursor, or another client the agent URL generated by AIP. The client speaks MCP to AIP; AIP keeps the Notion credential and enforces the account and tool policy.
Notion’s server remains the source of tool behavior and workspace access. AIP is the reusable gateway in front of it, as described in the MCP and OpenAPI overview.
Design an agent around a Notion role
A project researcher usually needs search, fetch, comments, and structured queries. A release-note writer may also need page creation but not database or view administration. A workspace curator is the rare role that benefits from move, database, and view tools. Start with the smallest of those shapes and add write access only after the repeated workflow is clear.
If several people or automations need different boundaries, compare the available plans before collapsing them into one overpowered agent. The goal is not to make all of Notion available everywhere; it is to make the right slice reliably available wherever that agent runs.
What to ask your agent
Useful Notion prompts name both the source of truth and the artifact the agent should leave behind. Start with one of these, then narrow the agent's visible tools as the workflow settles: