Skip to main content
Back to the Notion MCP server

MCP Gateway · Claude Cowork

Notion icon

Connect Notion to Claude Cowork

Some Notion jobs take many steps: building a new team database with its views and first entries, reorganizing a teamspace, or working through every open comment on a set of pages. Cowork handles them as one longer task. Notion reaches Cowork through the synced plugin marketplace, and Speakeasy's agent hooks check each prompt before a step runs.

Category
Productivity
Tools
14
Authentication
OAuth
Claude Cowork
Cowork tab in Claude Desktop

Behind the MCP Gateway

Run Notion MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Notion call inspected and logged.

Deploy on MCP Gateway

Set up

Add Notion to Claude Cowork in 4 steps

  1. 01

    Add Notion from the catalog

    An admin finds Notion in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    Notion uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use Notion

    Give teams the mcp:connect scope on the Notion server through team access or a role. Claude Cowork connects to the Notion server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect Claude Cowork

    Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.

    New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.

    Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.

    In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.

    Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.

    In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.

  4. 04

    Sign in and use Notion from Claude Cowork

    The first time Claude Cowork connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    Notion needs its own OAuth grant, so each person connects it once. Until they do, Notion calls fail while the rest of the gateway keeps working.

    From then on, Notion's tools appear in Claude Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.

Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.

Use cases

What Claude Cowork users do with Notion

Build a content calendar

Cowork creates a content calendar database, adds a calendar view by publish date, and fills in a page for each piece already planned.

notion-create-databasenotion-create-viewnotion-create-pages

Reorganize a teamspace

Cowork lists the teamspaces, works out where each stray page belongs, and moves pages and databases under the right parents.

notion-get-teamsnotion-move-pages

Clear open comments on a document set

Give Cowork a list of policy pages. It reads every open discussion, makes the agreed edits, and replies to each comment to say what changed.

notion-get-commentsnotion-update-pagenotion-create-comment

Tools

14 tools

Each Notion tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork sees it.

notion-fetch

Retrieves details about a Notion entity (page, database, or data source) by URL or ID. Provide URL or ID in id parameter. Make multiple calls to fetch multiple entities. Pages use enhanced Markdown format.

notion-create-pages

Overview Creates one or more Notion pages, with the specified properties and content. Parent All pages created with a single call to this tool will have the same parent. The parent can be a Notion page ("page_id") or data source ("data_source_id").

notion-update-page

Overview Update a Notion page's properties or content. Properties Notion page properties are a JSON map of property names to SQLite values. For pages in a database: - ALWAYS use the "fetch" tool first to get the data source schema and the exact property names.

notion-move-pages

Move one or more Notion pages or databases to a new parent.

notion-duplicate-page

Duplicate a Notion page. The page must be within the current workspace, and you must have permission to access it. The duplication completes asynchronously, so do not rely on the new page identified by the returned ID or URL to be populated immediately.

See all 14 tools

Control

What Speakeasy can see and stop in Claude Cowork

The gateway covers every client the same way. The rest depends on what Claude Cowork exposes to Speakeasy.

Tool logs

Gateway

Every Notion call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Notion tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Notion can reject a tool request before it reaches the server, or withhold a result from Claude Cowork. MCP-scoped policies are enabled per organization.

Prompt blocking

Claude Cowork

Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.

Session telemetry

Claude Cowork

Cowork's OTLP export ties sessions to people and feeds observability.

Anthropic inference hooks

Claude Cowork

On Claude Enterprise, prompts can be checked before inference (beta).

  • Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
  • Personal Claude accounts can't be governed in Cowork.

Questions

Frequently asked questions

What does an admin set up for Notion in Cowork?
In Claude's Organization settings > Plugins & skills, the admin syncs the plugin repository from GitHub, marks the observability plugin Required and sets the plugin carrying Notion to Available to install or Installed by default.
Can personal Claude accounts use governed Notion in Cowork?
No. Personal Claude accounts can't be governed in Cowork, and neither the device agent nor MDM reaches it, so the Claude-side setup always applies.
How do Claude Cowork users get Notion?
An admin adds Notion from the Speakeasy MCP Catalog and grants access by team or role. Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork. Each person then sees only the Notion tools their access allows.
Are Notion calls from Claude Cowork logged?
Yes. Notion calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Notion in other clients

AI everywhere.

Control here.