Notion MCP Server

Notion MCP Server is a MCP server built around notion's official MCP server, using an internal integration token to let agents read and work with authorized pages and databases. Its value is practical: read notion pages and search workspace content are available from one documented project, while the repository remains inspectable before it is added to an agent workflow.

Set up Notion MCP Server from its public GitHub instructions, keep the initial permission scope small, and verify it with a low-risk task before regular use.

Help me set up Notion MCP Server.
Project URL: https://github.com/makenotion/notion-mcp-server

Read the repository README and license first. Confirm the current host, prerequisites, destination paths, and permissions. Follow the repository's documented method, keep credentials out of files and logs, and start with the least-privilege or read-only option where available. Afterward, run a small verification and report the exact changes, commands, configuration path, and result. Ask before overwriting files or requesting broader access.

{"mcpServers":{"notion":{"command":"npx","args":["-y","@notionhq/notion-mcp-server"],"env":{"NOTION_TOKEN":"YOUR_NOTION_INTEGRATION_TOKEN"}}}}

1. 1
   Review prerequisites and scope

   Read the README, confirm the target host, and prepare these prerequisites: Create a Notion internal integration; Share required pages with the integration; Node.js and npx. Check destination paths and permissions before making changes.

2. 2
   Apply the documented setup

   Run the documented command: npx -y @notionhq/notion-mcp-server

3. 3
   Verify with a small task

   Restart the MCP host and confirm that Notion MCP Server appears in the server list. Call one low-risk read-only tool and check that it returns an expected result without authentication errors.

This assessment is based on the repository README, component documentation, license, and maintenance metadata. Maintained by Notion with a documented permission model; Only pages shared with the integration enter its scope. The main trade-offs are also clear: The integration token must be stored as a secret; Broad integration permissions expand the agent's access. No local installation or functional test was claimed during cataloging.