Mcp Notion
Connect Notion workspaces so your agent can search docs, read blocks, query databases, and create pages while you ship product specs and runbooks.
Overview
mcp-notion is a MCP server for the Build phase that lets AI agents search Notion, read pages and blocks, query databases, and create pages via the Notion API.
What is this MCP server?
- Search Notion workspace content from the agent
- Read pages and blocks for grounding answers in your wiki
- Query Notion databases with structured filters
- Create new pages from agent-driven workflows
- npm @infoinlet/mcp-notion v0.1.1 with stdio MCP transport
- Published version 0.1.1 as @infoinlet/mcp-notion on npm
- MCP transport type stdio per server manifest
- Source repository subfolder services/mcp-notion
What problem does it solve?
Your specs and tasks are in Notion but your agent cannot see them unless you manually paste pages into every thread.
Who is it for?
Builders who run product docs, backlogs, or wikis in Notion and want agent workflows that read and update that source of truth.
Skip if: Teams on Confluence/Google Docs only, or workflows that forbid API write access to knowledge bases.
What do I get? / Deliverables
Once the MCP server and Notion token are configured, the agent pulls live workspace content and can file new pages without leaving the IDE.
- Agent tools for Notion search, read, database query, and page create flows
- stdio MCP package wired from infoinlet marketplace services/mcp-notion
- Live workspace grounding for implementation and PM tasks
Recommended MCP Servers
Journey fit
Build-phase PM and docs are where Notion already lives for specs, tasks, and wikis—agents need first-class read/write there instead of paste-heavy chat. Search, database queries, and page creation are core PM and documentation workflows during implementation, not just marketing content.
How it compares
Live Notion API MCP integration, not a static markdown export or generic note-taking skill.
Common Questions / FAQ
Who is mcp-notion for?
Solo founders and indie devs using Notion for PM docs who want Claude Code, Cursor, or Codex to search and update those pages through MCP.
When should I use mcp-notion?
Use it during build and PM when implementing from specs, syncing database views, or drafting new doc pages from agent sessions.
How do I add mcp-notion to my agent?
Create a Notion internal integration, share relevant pages/databases with it, install @infoinlet/mcp-notion (v0.1.1), and register the stdio MCP server with your NOTION_TOKEN in environment config.