This an Model Context Protocol (MCP) server that integrates Notion into your AI workflows. This server enables seamless access to Notion through MCP
If you already use Systemprompt, the systemprompt mcp server is the piece that lets your assistant work with it directly. This an Model Context Protocol (MCP) server that integrates Notion into your AI workflows. This server enables seamless access to Notion through MCP, allowing AI agents to interact with pages, databases, and comments.
@smithery/cli on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
Setup — 3. Set up environment: bash cp .env.example .env # Edit .env with your API keysTesting — The Testing tool exposed by this serverConfiguration is passed through the environment: SYSTEMPROMPT_API_KEY, NOTION_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Before using this server, you'll need: 1. Systemprompt API Key (Free) - Sign up at systemprompt.io/console - Create a new API key in your dashboard 2. Notion Account and Workspace - Active Notion account - Workspace with content you want to access 3. Notion Integration - Create at notion.so/my-integrations -
Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Systemprompt's toolset — Setup, Testing — is a fair guide to whether it matches your workflow. It is maintained by Ejb503; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Setup | 3. Set up environment: bash cp .env.example .env # Edit .env with your API keys |
| Testing | The Testing tool exposed by this server. |
{
"mcpServers": {
"systemprompt-mcp-notion": {
"command": "npx",
"args": ["-y", "@smithery/cli"],
"env": {
"SYSTEMPROMPT_API_KEY": "your-value",
"NOTION_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Before using this server, you'll need: 1. Systemprompt API Key (Free) - Sign up at systemprompt.io/console - Create a new API key in your dashboard 2. Notion Account and Workspace - Active Notion account - Workspace with content you want to access 3. Notion Integration - Create at notion.so/my-integrations -
| Variable | Description | Required |
|---|---|---|
| SYSTEMPROMPT_API_KEY | Credential the server authenticates with. | Yes |
| NOTION_API_KEY | Credential the server authenticates with. | Yes |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.