Notion

The @modelcontextprotocol/server-notion package was never official. Notion ships @notionhq/notion-mcp-server, maintained in makenotion/notion-mcp-server. It targets the Notion API revision 2025-09-03 which introduces the data-sources abstraction over classic databases. What it does: - Page search, create, update, and archive via the Notion API - Database queries with filter and sort objects, including compound filters - Block-level read and append for building agents that work inside a page - Uses Notion API 2025-09-03 data sources as the primary abstraction - Integration-token auth with scoped workspace access - Handles pagination and the 100-block request cap transparently Example: Wire it into a meeting-notes agent. The agent creates a page, appends block children in the target data-source, and later queries the data-source by a filter like "status is Open" — all without the human touching the Notion UI. Setup: Create a Notion integration in your workspace, share the relevant pages or data-sources with it, then set NOTION_API_KEY. The npm package is @notionhq/notion-mcp-server; "npx -y @notionhq/notion-mcp-server" is the full local install. Transport: stdio today. Notion has signalled the local binary may be sunset in favour of their remote MCP endpoint, so plan for a migration to mcp-remote style integration if you adopt this long term. Notes: Integration tokens are per-workspace. If your company has more than one workspace you will end up running more than one instance of the server, one per workspace — there is no multi-workspace token. Page and data-source access is explicit: the integration sees only what has been shared with it, which is the right default for production but sometimes surprising during first setup.