M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionHackMD MCP ServerA Model Context Protocol server for integrating HackMD's note-taking platform with AI assistants.Notion MCP ServerOfficial Notion MCP server for querying, editing, and managing Notion pages and databases via AI agents.
FMRS58 / 100 · C64 / 100 · C
Reliability7 / 208 / 20
Security and permissions10 / 2017 / 20
Maintenance12 / 2010 / 20
Documentation15 / 2016 / 20
Setup experience14 / 2013 / 20
Best for
  • Developers who want to integrate HackMD note management into AI workflows
  • Individuals or teams who prefer natural language interaction with their notes
  • Users who need cloud deployment of MCP servers
  • Teams and individuals who already manage docs/wikis in Notion and want AI clients (Claude Desktop, Cursor, etc.) to operate on that content directly
  • Developers who want to self-host a local MCP server rather than use a remote hosted option
  • Automation/agent workflows that need to query or update Notion database records programmatically
Not for
  • Not suitable for users without a HackMD API token
  • Not suitable for offline access to notes (server depends on network API)
  • Not for scenarios requiring advanced collaboration features like real-time co-editing, as the server provides mainly CRUD operations
  • Users who want the standard-OAuth, zero-JSON-config install with active official support — Notion recommends its newer remote Notion MCP server for that
  • Users uncomfortable handing a Notion integration token to a locally-run LLM client
  • Use cases needing capabilities the integration deliberately excludes, such as deleting databases
  • Long-term production deployments that need guaranteed maintenance, given this repo may be sunset
Required permissions
  • Requires HackMD API token (HACKMD_API_TOKEN) to authenticate all operations
  • Server can read and modify user profile, notes, teams, history, etc., depending on token permissions
  • A Notion internal integration token (NOTION_TOKEN or the Authorization value in OPENAPI_MCP_HEADERS), scoped by that integration's Capabilities (can be limited to read-only)
  • Access limited to the specific pages/databases explicitly connected to the integration, not the whole workspace
  • A separate bearer auth token when using the Streamable HTTP transport (--auth-token / AUTH_TOKEN)
  • Network access to the Notion API
Risks and side effects
  • API token leakage could lead to unauthorized account access; never commit it to version control
  • For HTTP transport, if the server is hosted without endpoint protection, anyone could use your token
  • Server modifies user data (create, update, delete notes); confirm before operations
  • If the integration is granted broad read/write capabilities and connected to many pages, that content is effectively exposed to the LLM, risking data leakage or unintended edits
  • Running with --unsafe-disable-auth removes bearer authentication on the HTTP transport, potentially making it reachable via DNS rebinding from pages a user visits — the README says to only use it on an isolated network
  • Multi-tenant token passthrough requires careful TLS/gateway configuration; misconfiguration risks leaking or misrouting Notion tokens between tenants
  • The README states this local server may be sunset in favor of the remote Notion MCP, and that issues/PRs here are not actively monitored, so long-term maintenance and security fixes are not guaranteed
  • Storing NOTION_TOKEN or OPENAPI_MCP_HEADERS directly in shared client config files risks leaking the secret
Supported clientsClaude DesktopClaude Desktop, Cursor, Zed, GitHub Copilot CLI
Tools129