Notion MCP Server vs Obsidian MCP

Notion MCP Server

MCP Servers

Obsidian MCP

MCP Servers

Tagline

Notion MCP Server

The official Notion MCP server: give Claude, Cursor, and Copilot typed access to your Notion pages, databases, and comments.

Obsidian MCP

A local Model Context Protocol server that lets MCP-compatible assistants safely read and modify explicitly configured Obsidian vaults.

Pricing

Notion MCP Server

Free· Server is free and MIT-licensed; a paid Notion workspace is only required for features gated behind Notion's own plans. Notion tiers: Free / Plus $10 per user/mo / Business $18 per user/mo / Enterprise (custom).

Obsidian MCP

Free· Free and open-source (MIT). No paid tiers; users only pay for their own Obsidian license if they choose Commercial/Sync/Publish add-ons.

API

Notion MCP Server

Yes

Obsidian MCP

Not listed

Open source

Notion MCP Server

Yes · MIT

Obsidian MCP

Yes · MIT

GitHub stars

Notion MCP Server

4,686

checked 2026-10-29

Obsidian MCP

747

checked 2026-10-29

Last GitHub push

Notion MCP Server

2026-10-28

Obsidian MCP

2026-10-08

First commit

Notion MCP Server

2025-03

Obsidian MCP

2024-12

Package downloads (30 d)

Notion MCP Server

—

Obsidian MCP

13,558 · npm obsidian-mcp

checked 2026-10-17

Best for

Notion MCP Server

Teams already living in Notion who want Claude, Cursor, or Copilot to read specs, query project databases, draft pages, and leave comments through a standard MCP surface without building a custom API client.

Obsidian MCP

—

Not for

Notion MCP Server

Users who need OAuth-based per-user login rather than a shared integration token, or workflows that require destructive admin operations (deleting databases, bulk workspace migrations) not exposed by the server.

Obsidian MCP

—

Editorial score

Notion MCP Server

—

Obsidian MCP

—

Use cases

Notion MCP Server

AI agent drafting weekly status reports into a Notion pageResearch assistant querying a projects database and appending findingsMeeting-notes pipeline inlining transcripts as Markdown blocksClaude Code reading a spec page and filing follow-up commentsCross-workspace search from a chat clientAutomated triage that comments on pages by title matchTemplate-driven page creation under a specified parentKnowledge-base RAG grounding pulled live from Notion pages

Obsidian MCP

Reading notes and retrieving their SHA-256 etagsCreating new notes atomically without overwriting existing contentSearching vault content, filenames, or tagsAdding tags to notes

Pros

Notion MCP Server

• Official and actively maintained by Notion, so the tool surface tracks the real API rather than a community reverse-engineering
• Markdown read/write endpoints make page editing dramatically more token-efficient than raw block JSON
• Runs via npx or Docker with no build step; wiring into Claude Desktop, Cursor, or Copilot CLI is a small JSON snippet
• Both stdio and streamable HTTP transports, with bearer-token auth and per-request token passthrough for multi-tenant hosting
• Permission scope is bounded by which pages you share with the integration in Notion, giving fine-grained blast-radius control
• MIT-licensed and easy to fork if you need custom tool shapes or additional guardrails
• Broad coverage: pages, blocks, data sources, comments, search, templates, and content moves

Obsidian MCP

• The server runs locally without listening on a network interface or sending telemetry.
• File mutations are journaled, conflict-checked, atomically replaced, and rolled back as a single transaction.
• The vendor says that all tool schemas are strict JSON Schema 2020-12 contracts generated from Zod.
• The server works directly with Markdown files, so the Obsidian application does not need to be running.

Cons

Notion MCP Server

• Internal-integration tokens are static secrets; there is no first-party OAuth flow in the local server yet (a remote OAuth version is hinted but not shipped)
• V2.0 dropped the old database_id tools in favour of data_source_id, so older agent prompts and any scripts that hard-coded the previous tool names need to be updated
• Intentionally omits destructive operations like deleting databases, which is safe but occasionally frustrating for cleanup workflows
• README itself flags a non-zero risk of exposing workspace data to an LLM; you need to think about read-only integrations for sensitive spaces
• Requires a per-page or per-database access grant in Notion for every resource the agent should see — easy to forget and a common cause of empty query results
• Rate limits, pagination quirks, and schema oddities are inherited from the underlying Notion API and are not smoothed over by the server

Obsidian MCP

• The server requires Node.js 22 or newer to run.

Website

Notion MCP Server

github.com

Obsidian MCP

github.com

Editorial score: rule-based, 0–10, from AI-assisted profile inputs (see /methodology) — not a user rating; “—” means unscored. “Not listed” means we have no record of it, not that it is absent. GitHub figures and prices carry the date they were checked or captured; prices are shown as published, unconverted.