Notion

Catalog name notion. A remote MCP server for Notion pages and databases.

What it’s for

If your specs, decisions and open questions live in Notion, the agent building against them normally gets a paraphrase of a page, filtered through whatever you remembered to copy. This connector lets it search for the page itself and read what is actually written there, including the part that contradicts the summary.

It writes as well as reads, with the rights of the account you sign in with.

Add it

At init, or to an existing workbench:

monoceros init acme --with-mcp-servers=notion

monoceros add-mcp-server acme notion

Note

acme is just a sample workbench name - it’s whatever you passed to monoceros init. Substitute your own throughout.

Then apply:

monoceros apply acme

Signing in

There is no key to fill. Notion’s hosted server authenticates interactively, so the yml entry is one line and you sign in once from inside the container:

mcpServers:
  - name: notion

The per-agent step is in Servers that sign in.

The older token route needs page-by-page access

Notion also publishes a server you run yourself, authenticated with an internal integration token. That token starts with access to nothing: until you connect pages to the integration in Notion’s own Access tab, the server connects, reports its tools, and finds no content. The hosted server this connector uses has no such step.

Where it runs

Remote (http), at https://mcp.notion.com/mcp. The request leaves the container.

Verify it

monoceros check acme

MCP servers
  notion → Claude Code
      signs in interactively; authenticate once inside the container

That line means the server is registered with every agent and waiting for a sign-in. Once you have signed in, ask the agent to find a page you know the title of.

Remove it

monoceros remove-mcp-server acme notion

See also

• MCP servers overview - the model behind this, and the per-agent sign-in.
• Atlassian Rovo and Linear - the same role for the other two places requirements tend to live.