Smithery Notion
Let Claude Code or Cursor read and update your Notion pages and databases while you ship specs, roadmaps, and launch checklists from one workspace.
Overview
Smithery Notion is a Build-phase MCP server that connects AI agents to a live Notion workspace over Smithery’s hosted streamable-http endpoint.
What is this MCP server?
- Streamable HTTP MCP at server.smithery.ai with Bearer Smithery API key auth
- Targets full Notion workspace context for organizing work and managing projects
- Version 1.0.0; upstream source in smithery-ai/mcp-servers notion subfolder
- Fits agent-driven doc updates alongside human-edited Notion databases
- No local Notion MCP binary—connect through Smithery remotes in Claude Desktop or compatible clients
- Server version 1.0.0 per server.schema.json
- Single streamable-http remote endpoint on server.smithery.ai
- Repository source: github.com/smithery-ai/mcp-servers (notion subfolder)
What problem does it solve?
Copy-pasting Notion pages into the agent breaks context and you lose structured updates back to the database you actually run the business from.
Who is it for?
Builders who treat Notion as the system of record for specs, tasks, and docs and want one MCP remote instead of self-hosting notion-mcp.
Skip if: Teams that need offline-only vaults, strict data residency without Smithery in path, or deep custom Notion automations better handled by direct API scripts.
What do I get? / Deliverables
After you add the remote with a Smithery API key, your agent can work against Notion workspace content in line with coding and shipping tasks.
- Agent-accessible Notion workspace over MCP
- Centralized Smithery-authenticated remote configuration
- Live project and doc context during agent sessions
Recommended MCP Servers
Journey fit
Notion is where solo builders store build-time artifacts—PRDs, task boards, and integration notes—so the canonical shelf is Build before Ship or Grow content workflows. This Smithery-hosted remote MCP bridges the agent to Notion’s API as an external system, which maps directly to integrations rather than frontend or backend code in-repo.
How it compares
Hosted Notion MCP integration via Smithery—not a planning skill or a static export of your wiki.
Common Questions / FAQ
Who is Smithery Notion for?
Solo builders and small teams that centralize roadmaps and documentation in Notion and use Claude Code, Cursor, or other MCP clients daily.
When should I use Smithery Notion?
Use it during build and operate work when the agent must read current pages or write structured updates into your existing Notion workspace.
How do I add Smithery Notion to my agent?
Register the remote URL https://server.smithery.ai/@smithery/notion/mcp with streamable-http transport and set Authorization to Bearer your Smithery API key.