Secure Notion access for AI agents

Search, read, and edit pages, databases, comments, and meeting notes via Notion's official MCP server.

Connect Notion to the gateway to give agents governed access to your Notion workspace: pages, databases, views, comments, teamspaces, and meeting notes — every call runs through your policies and is logged for audit.

Server URL: https://mcp.notion.com/mcp

Setup

Notion's MCP server supports Dynamic Client Registration, so there is no app to create on Notion's side; the gateway registers an OAuth client automatically per org. See Dynamic client registration.

Dynamic client registration

  1. Navigate to Resources, click Add Resource, and select Notion from the catalog.
  2. Pick the Per-org dynamic registration card. The gateway self-registers an OAuth client with Notion — no client ID/secret needed — and installs the resource right away.
  3. Each user authorizes their own Notion account and selects which workspace (and pages) the connection can access.

Access is scoped by what the user grants during the Notion OAuth flow: the connection can only reach content shared with it in the selected workspace. Manage linked accounts in Connections.

Available tools

ToolAccessDescription
notion-searchreadSearch the workspace and connected sources, or find people by name or email
notion-fetchreadRetrieve a page, database, or data source by URL or ID
notion-get-commentsreadGet comments and discussions from a page
notion-get-teamsreadList teams (teamspaces) in the workspace
notion-get-usersreadList workspace users, or look up a specific user
notion-get-async-taskreadGet the status and result of an async task started by another tool
notion-query-data-sourcesreadQuery databases with SQL, or run a database view's filters and sorts
notion-query-database-viewreadQuery a database view using its configured filters, sorts, and columns
notion-query-meeting-notesreadQuery the current user's meeting notes by title, attendees, or date range
notion-create-pageswriteCreate one or more pages with properties and Notion-flavored Markdown content
notion-update-pagewriteUpdate a page's properties or content
notion-move-pageswriteMove pages or databases to a new parent
notion-duplicate-pagewriteDuplicate a page within the workspace (completes asynchronously)
notion-create-databasewriteCreate a new database from a SQL DDL schema
notion-update-data-sourcewriteUpdate a data source's schema, title, or attributes via SQL DDL
notion-create-commentwriteAdd a comment to a page or content, or reply to a discussion thread
notion-create-viewwriteCreate a new view on a database (table, board, calendar, timeline, and more)
notion-update-viewwriteUpdate a view's name, filters, sorts, or display configuration

Required scopes

Notion does not use granular OAuth scopes for its MCP server. The connection's reach is set during the OAuth flow, where the user picks the workspace and the pages shared with the connection.

Policy examples

Every org is created with a seeded Allow all rule at the bottom of the list, so any call your own rules don't match stays allowed. Express restrictions as deny rules above it — new rules are added at the top, so a fresh deny outranks it automatically. See Rule order.

  • Read-only access: deny notion-create-*, notion-update-*, notion-move-pages, and notion-duplicate-page. Those patterns cover every write in the table above, leaving the notion-search, notion-fetch, notion-get-*, and notion-query-* reads.
  • Comment-only collaboration: on top of the read-only rule, add an Allow for notion-create-comment so agents can leave feedback without editing content. Create it after the deny — new rules land at the top, which is where the allow has to sit to win.
  • No schema changes: deny notion-create-database, notion-update-data-source, notion-create-view, and notion-update-view while leaving page tools allowed.

Next steps

  • Create a policy — start from the read-only pattern in Policy examples above.
  • Credential modes — see how DCR compares to the other modes catalog resources use.

On this page