Notion MCP tool access by plan — the full map
23/6/2026 · 10:24

Notion MCP tool access by plan — the full map

As of June 22, 2026, Notion's MCP server shows all 17 tools on every plan — but visibility ≠ access. This article maps each tool against plan tier, documents the one concrete access improvement (notion-query-data-sources dropped from Enterprise to Business+Notion AI), and gives Free/Plus users two working workarounds.

As of June 22, 2026, Notion's MCP server shows every tool in its catalog to every plan — Free, Plus, Business, and Enterprise. 1 Before this change, Free and Plus users saw only the two tools their plan supported (notion-search and notion-fetch). Claude, when connected via MCP, had no way to know the other 15 tools existed.
Now it knows. When a Free-plan user asks Claude to query a database, Claude will attempt notion-query-database-view — and immediately return an upgrade prompt instead of a silent error. That's the actual change: visibility, not access. The gates are still in place.

The full tool map by plan

ToolFreePlusBusiness + Notion AIEnterprise + Notion AI
notion-search
notion-fetch-page
notion-fetch-database
notion-create-page
notion-update-page-properties
notion-add-content-to-page
notion-create-database
notion-update-database
notion-create-comment
notion-list-users
notion-query-database-view⬆️ Business⬆️ Business✅ (Notion AI)
notion-query-meeting-notes⬆️ Business⬆️ Business✅ (Notion AI)
notion-query-data-sources (single source)⬆️ Business⬆️ Business✅ (Notion AI)
notion-query-data-sources (multi-source)⬆️ Enterprise⬆️ Enterprise⬆️ Enterprise
notion-get-comments
notion-update-page
notion-delete-block
The three query tools — notion-query-database-view, notion-query-meeting-notes, and notion-query-data-sources (single source) — are the gated ones that matter for PM workflows. All three now require Business + Notion AI as a minimum. 1 2
The notion-query-data-sources downgrade is the one concrete access change in this changelog: single-source queries dropped from Enterprise to Business+Notion AI. Cross-source queries remain Enterprise-only. 1
Cargando tarjeta de estadísticas…

If you're on Free or Plus and need database queries

The upgrade prompt is new; the underlying constraint is not. Free and Plus users have never been able to use notion-query-database-view via the official MCP server. Two workarounds exist, each with different tradeoffs:
Cargando tarjeta de contenido…
Option 1 — easy-notion-mcp (recommended for recurring use)
easy-notion-mcp (GitHub: Grey-Iris/easy-notion-mcp) is an open-source MCP server that talks directly to the standard Notion API instead of routing through Notion's first-party MCP layer. Database filtering and querying work on the Free plan, since they call the Notion API directly rather than the plan-gated MCP tools. 3
Install it with your API token and point Claude Desktop at it in place of (or alongside) the official @notionhq/notion-mcp-server. The author disclosed they built the tool while recommending it in the Reddit thread — factor that into your evaluation, but the approach itself is sound: direct API calls have no plan restriction on read operations.
Option 2 — Let Claude write the query script (one-off use)
Give Claude your Notion API token and ask it to write a script that queries your database directly. The tradeoff: Claude Desktop will prompt you to approve each API call individually rather than running silently. 3
As one commenter put it: "make a notion token, make claude build you a script that does what the mcp doesn't. simple as that, and free." 3 That approval step makes it impractical for scheduled or fully automated runs, but it works fine when you're sitting at the keyboard and running ad-hoc queries.

What this means if you're on Business + Notion AI

The notion-query-data-sources downgrade is the only thing that moved in your favor. If you were on Enterprise specifically to access single-source queries via MCP, you can now do it on Business — provided you have Notion AI on that plan.
The multi-source variant of notion-query-data-sources still requires Enterprise. That's the one that lets Claude query across two or more databases in a single call — useful for cross-database rollup queries (e.g., pulling from both a Roadmap DB and a Bugs DB in one MCP tool call). If that's your use case, the plan requirement hasn't changed.

The visibility change makes MCP integrations easier to debug: when something doesn't work, Claude now tells you explicitly which plan tier would unlock it rather than acting as if the tool doesn't exist. That's a real quality-of-life improvement, even if no new capabilities came with it.
Cover image: AI-generated illustration.

Añade más opiniones o contexto en torno a este contenido.

  • Inicia sesión para comentar.