Skip to main content
hc
Submit
3 compared

Knowledge base MCP servers compared

Note and knowledge-base MCP servers that give Claude access to your docs, compared on trust, setup, and safety.

Open in the interactive comparison tool
FieldNotion MCP Server for Claude

Read docs, update pages, and manage tasks in Notion workspaces

Open dossier 		Obsidian MCP Server

MCP server that lets Claude interact with an Obsidian vault through the Obsidian Local REST API community plugin.

Open dossier 		AFFiNE MCP Server

MCP server for connecting Claude to AFFiNE Cloud or self-hosted AFFiNE workspaces, documents, databases, comments, collections, folders, tags, notifications, blobs, access tokens, semantic page composition, templates, edgeless canvas data, and workspace organization workflows over stdio or HTTP.

Open dossier
Trust
Install riskLow riskReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Categorymcpmcpmcp
Sourcefirst-partysource-backedsource-backed
AuthorNotionMarkus PfundsteinDAWNCR0W
Added2025-09-182026-06-052026-06-06
Platforms
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo———
Safety notes✓Share only intended Notion pages or databases and review writes that alter docs, tasks, or workspace records.✓Obsidian MCP Server can read, search, append, patch, and delete files in the configured vault. Patch and append operations can change existing notes, create new notes, and insert content relative to headings, block references, or frontmatter fields. Delete operations can remove files or directories from the vault. Keep vault backups and require human review before allowing broad edits, deletes, generated summaries, or note reorganizations.✓The full tool surface can create, update, publish, revoke, move, replace, and delete AFFiNE workspaces, documents, folders, collections, comments, database rows, blobs, surface elements, tags, and access tokens. Start with AFFINE_TOOL_PROFILE=read_only or disable groups such as destructive, admin, blobs, users, access_tokens, docs.database, or write when the assistant only needs discovery or reading. HTTP mode exposes MCP endpoints and must be protected with bearer or OAuth authentication, HTTPS, allowed origins, and deployment-level access controls. AFFiNE Cloud requires API tokens for MCP usage; avoid trying to automate email/password login against Cloud deployments. Cookie and password-based auth can grant broad account access and should be avoided for unattended or shared deployments.
Privacy notes✓Page contents, database rows, comments, attachments, user names, and workspace metadata may be sent through model context.✓Obsidian vaults often contain private notes, meeting records, research, personal data, API keys, customer details, drafts, and internal decisions. Vault paths, note names, note contents, search terms, prompts, tool arguments, and generated notes may be visible to the MCP client and model provider. Treat the Obsidian API key as a secret and avoid exposing the Local REST API beyond the trusted host and port configuration.✓Workspaces, document titles, document bodies, comments, tags, database schemas, database rows, edgeless canvas data, notifications, user profiles, access-token metadata, blobs, and exported markdown can be sent to the MCP client and model. API tokens, cookies, passwords, bearer tokens, OAuth config, and saved config files should be treated as secrets and kept out of prompts, logs, screenshots, issues, and committed MCP config. Generated or modified documents can persist in AFFiNE and may become visible to collaborators depending on workspace permissions and sharing state. Blob upload, cleanup, export, and publish/revoke workflows can expose files, generated content, or collaboration state beyond the current prompt.
Prerequisites
  • Notion workspace account (not Guest workspace - Guest workspaces don't support integrations)
  • OAuth 2.0 integration (create public integration in Notion with client ID and client secret)
  • HTTP transport support (remote MCP server at https://mcp.notion.com/mcp)
  • Internet connection (remote Notion API access required)
  • Python 3.11 or newer available to the MCP client runtime.
  • uvx available for package execution.
  • Obsidian installed with a vault you want Claude to access.
  • Obsidian Local REST API community plugin enabled with an API key.
  • Node.js and npm for installing the affine-mcp-server package.
  • AFFiNE Cloud API token or approved self-hosted AFFiNE credentials.
  • AFFiNE base URL for the Cloud or self-hosted deployment.
  • Clear workspace scope and least-privilege tool profile before enabling write, admin, destructive, blob, or access-token tools.
Install
claude mcp list && claude mcp status notion
uvx mcp-obsidian
npm i -g affine-mcp-server
Config
{
  "mcpServers": {
    "notion": {
      "url": "https://mcp.notion.com/mcp",
      "type": "http"
    }
  }
}
{
  "mcpServers": {
    "mcp-obsidian": {
      "command": "uvx",
      "args": ["mcp-obsidian"],
      "env": {
        "OBSIDIAN_API_KEY": "YOUR_OBSIDIAN_API_KEY",
        "OBSIDIAN_HOST": "127.0.0.1",
        "OBSIDIAN_PORT": "27124"
      }
    }
  }
}
{
  "mcpServers": {
    "affine": {
      "command": "affine-mcp",
      "env": {
        "AFFINE_BASE_URL": "<affine-base-url>",
        "AFFINE_API_TOKEN": "<affine-api-token>",
        "AFFINE_TOOL_PROFILE": "read_only"
      }
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimed
More comparisons, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.