Notion (local)
BetaNotion's own MCP server reads and writes pages and databases with an integration token.
- Productivity
- Local
- Runs
- On the developer's Mac
- Launched with
- npx, Docker
- Platform
- macOS
- Publisher
- Notion Labs
How it works
Every agent request passes through Ferentin policy before it reaches Notion (local).
It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with npx -y @notionhq/notion-mcp-server or docker run -i --rm mcp/notion.
Ferentin's endpoint agent finds Notion (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.
- AI agentAsks for something
- Ferentin policies
- Notion (local) MCP serverRuns on the developer's Mac
- Governed resultChecked, logged, returned
About Notion (local)
Notion's own MCP server reads and writes pages and databases with an integration token.
Frequently asked about Notion (local)
- How do I connect Notion (local) to Ferentin?
- Enroll your Macs with the Ferentin endpoint agent, then add Notion (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
- Is the Notion (local) integration generally available?
- The Notion (local) integration is currently beta on Ferentin.
Related integrations
3
Time (local)
The reference time and timezone server, with no network, credentials or file access.
Atlassian (local)
A community-maintained Jira and Confluence server that reads and writes issues, pages and comments with a user's API token. It is not published by Atlassian.
Figma (local)
A community-maintained server that pulls Figma design files and layout data into the agent with a personal access token. It is not published by Figma.