Because access is whatever the integration was granted, limiting the blast radius is a matter of sharing one page rather than trusting a server setting — and that step is easy to forget, which is why the README puts it before the install instructions. Mirroring the whole SDK is a real trade: broad coverage, but a wide tool surface for a model to choose from.
A Notion server that exposes the API SDK as tools rather than curating a smaller set. It authenticates with a Notion integration token you create, and reaches whatever pages you have shared with that integration.
- The Notion API surface as tools — reading, creating, updating and deleting pages through natural-language instructions
- Access follows the integration's permissions, so what the assistant can touch is decided in Notion rather than in the server config
- The token is passed on the command line with -t, which keeps it in the client's config rather than a file in the repository
- Runs straight from npm with npx, so there is nothing to clone or build
A Notion integration and its token, created by following Notion's integration setup, plus explicit permission granted to each page you want reachable. Run as `npx -y @orbit-logistics/notion-mcp-server -t <notion_integration_token>`. Nothing else to install.
One command plus a key — npx -y @orbit-logistics/notion-mcp-server -t <notion_integration_token>, then supply credentials