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 AccountAtlassian Rovo MCP ServerSecurely connect Atlassian Cloud to AI tools.
FMRS61 / 100 · C66 / 100 · C
Reliability10 / 208 / 20
Security and permissions11 / 2015 / 20
Maintenance13 / 2015 / 20
Documentation14 / 2015 / 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
  • Developers, content creators, and project teams using Atlassian Cloud
  • Teams that want Atlassian access inside ChatGPT, Claude, Cursor, or VS Code
  • Users who need natural-language search, write, and cross-product workflows
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 without an Atlassian Cloud site or relevant product permissions
  • Deployments requiring a self-hosted MCP server
  • Users unwilling to grant an AI client access to Atlassian data or actions
  • Jira Service Management or Bitbucket Cloud workflows requiring OAuth authentication
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
  • Jira and Confluence provide read, write, and search permission groups
  • Jira Service Management provides read and write access through API tokens only
  • Bitbucket Cloud provides read and write access through scoped API tokens only
  • Compass is available through OAuth 2.1 only
  • The first OAuth installer for a site must have access to the Atlassian apps requested by the MCP scopes
  • Organization administrators can manage domain controls, API-token authentication, app access, and audit logs
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
  • AI clients can perform Jira, Confluence, Jira Service Management, Bitbucket, and Compass actions on the user’s behalf
  • Prompt injection, indirect prompt injection, and tool-poisoning attacks may cause data exfiltration or unintended changes
  • Use least privilege, scoped tokens, and minimal project or workspace access
  • Require human confirmation for high-impact or destructive actions and monitor audit logs
Supported clientsClaude Desktop, ClineOpenAI ChatGPT, Claude, Cursor, GitHub Copilot, GitHub Copilot CLI, Google Gemini CLI, Amazon Quick Suite, Local MCP-compatible clients via mcp-remote
Tools120