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.

DimensionLINE Bot MCP ServerMCP server that connects an AI Agent to your LINE Official AccountNotion MCP ServerOfficial Notion MCP server for querying, editing, and managing Notion pages and databases via AI agents.
FMRS61 / 100 · C64 / 100 · C
Reliability10 / 208 / 20
Security and permissions11 / 2017 / 20
Maintenance13 / 2010 / 20
Documentation14 / 2016 / 20
Setup experience13 / 2013 / 20
Best for
  • Developers or operations teams that already have a LINE Official Account with the Messaging API enabled
  • Teams that want an AI Agent to automate LINE messaging and account operations
  • Users of MCP-capable clients such as Claude Desktop or Cline who need LINE integration
  • 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
  • Users without a LINE Official Account or without the Messaging API enabled
  • Scenarios needing stable, fully supported production functionality beyond a preview release
  • Environments stuck below Node.js v22 that cannot use Docker
  • 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 CHANNEL_ACCESS_TOKEN (Channel Access Token) to call the LINE Messaging API
  • Optionally requires DESTINATION_USER_ID as the default recipient
  • Requires network access to the LINE Messaging API
  • 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
  • CHANNEL_ACCESS_TOKEN is a sensitive credential; if leaked, others could send messages or read data on behalf of the Official Account
  • Broadcast messages reach all followers, so misuse can cause spam or an irreversible mass send
  • Operations such as create_rich_menu, delete_rich_menu and set_rich_menu_default directly change the Official Account's rich menu configuration
  • The repository is a preview version and may not include complete functionality or comprehensive support
  • 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 Desktop, ClineClaude Desktop, Cursor, Zed, GitHub Copilot CLI
Tools129