Activation required. AI access management must be enabled for your tenant before you can use it. To get started, contact the C1 support team for a walkthrough.
- Notion MCP — listed as plain Notion in your catalog. C1 registers Notion’s own hosted MCP server (
mcp.notion.com) as a downstream server C1 governs. Authentication is always per-user OAuth using dynamic client registration (DCR) — Notion’s hosted MCP server doesn’t support a bearer token or API key, so there’s no integration to create in Notion first. Tool calls run with the connected user’s full Notion permissions, plus whatever connected sources (Slack, Google Drive, GitHub, Jira, Microsoft Teams, SharePoint, OneDrive, Linear) their Notion AI connectors expose. - Notion API — C1 hosts its own MCP server that translates Notion’s REST API into tools. You choose between per-user OAuth or a shared internal integration secret (a bearer token), and you scope access with the capabilities you grant the Notion integration (read/update/insert content, comments, user information).
Use the native Notion MCP option (listed as plain Notion in your catalog) if you want Notion’s own broader, agentic tool set — including cross-source search — and per-user OAuth is acceptable for your tenant. Use Notion API if you need a shared service-account credential (bearer token), or you want to scope access with Notion’s capability toggles.
- Notion MCP
- Notion API
C1 registers as a client of Notion’s own hosted MCP server (Notion MCP) rather than translating Notion’s REST API itself. Your users’ AI clients still only ever see C1-governed MCP tools, but C1 proxies each tool call straight through to
mcp.notion.com under the connected user’s authorized session, then returns the result. The tools available are exactly the ones Notion’s own MCP server exposes — C1 doesn’t reshape or add to them.Before you begin
- AI access management must be enabled for your tenant. See Enable AI access management.
- Nothing to create in Notion ahead of time. This option only supports per-user OAuth with dynamic client registration — Notion’s hosted MCP server doesn’t offer a bearer token or API key mode, so there’s no client ID, secret, or integration to register. Each user just needs a Notion account with access to the workspace.
- To search and read from connected sources (Slack, Google Drive, GitHub, Jira, Microsoft Teams, SharePoint, OneDrive, Linear) through Notion MCP, users need those connectors set up on the Notion side. See Notion’s Notion MCP documentation.
In your MCP server catalog, this option is listed as Notion — distinct from the Notion API entry, which connects through C1’s own MCP server. If you don’t see either, contact the C1 support team to enable it for your tenant.
Set up per-user OAuth
Per-user OAuth with dynamic client registration (DCR) is the only authentication method this option supports — there’s no bearer token or API key fallback. Each user authorizes individually, and C1 registers itself with Notion’s authorization server automatically, so there’s no app to create in Notion first (see Notion’s Connecting to Notion MCP documentation).1
Follow Register an MCP server and select Notion from the catalog.
2
When you configure authentication, choose OAuth2 — per-user passthrough and enable Use dynamic client registration. There’s no client ID or secret to enter.
3
Save your changes. The first time a user calls a Notion tool from their AI client, they’re redirected to Notion to sign in (if they aren’t already) and approve the connection, then returned to C1.
What access is granted
Unlike the Notion API option, there are no separate capability toggles to configure. Once a user authorizes, tool calls run with that user’s full Notion permissions — they can access everything the user can already access in Notion, including pages, databases, and comments, plus any connected sources their Notion AI connectors expose (Notion MCP).How Notion MCP credentials are shared
This option only supports per-user OAuth — there’s no shared, service-account, or bearer-token mode. Every tool call runs under the calling user’s own Notion identity, and Notion attributes each action to that individual. C1 still attributes each call to the individual user in the AI tool usage audit log.Discover and govern tools
After you register the server, C1 runs tool discovery against Notion’s MCP server. Discovered tools appear on the server’s Tools tab and include Notion’s own search and fetch tools, page and database creation and editing, page duplication, comments, teamspaces, users, and database views.Each tool starts as either Pending review or automatically Approved, depending on the option chosen when the server was set up or your tenant’s default tool settings in AI > MCP > Settings. See Require tool approval and Default tool classification.Before anyone can call a Notion tool, it must be approved, added to a toolset, and bound to an access profile. Continue to Govern tools and toolsets to set this up.Tool discovery runs even if authentication isn’t complete yet, so seeing discovered tools doesn’t confirm a user has authorized. You confirm access when an approved user successfully calls a Notion tool from their AI client.
Manage access to Notion MCP
Because this option uses per-user OAuth, there’s no shared secret in C1 to rotate. Users and admins manage access from Notion itself:- An individual user can disconnect at any time. In Notion, go to Settings > Connections, select the connection, open the ••• menu, and choose Disconnect the connection (Add and manage connections).
- An Enterprise workspace owner can revoke access for one user or everyone. In Notion, go to Settings > Connections > Manage, open the ••• menu next to the connection, then choose Revoke specific users’ access to a connection or Disconnect all users (Enterprise connection settings). Disconnecting all users revokes every external AI tool and MCP client connected through Notion MCP at once; affected users must re-authenticate to reconnect.