| FMRS | 59 / 100 · C | 66 / 100 · C |
|---|
| Reliability | 8 / 20 | 8 / 20 |
|---|
| Security and permissions | 14 / 20 | 15 / 20 |
|---|
| Maintenance | 13 / 20 | 15 / 20 |
|---|
| Documentation | 13 / 20 | 15 / 20 |
|---|
| Setup experience | 11 / 20 | 13 / 20 |
|---|
| Best for | - AI-first marketers running a LINE OA from their AI workspace
- SMB owners using LINE OA as their primary customer channel
- Marketing agencies managing many client OAs from one dashboard
- Developers building LINE-integrated SaaS, automations, or AI bots
| - 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 who only need to push a simple text or Flex message to one user (the official LINE Bot MCP server may be simpler)
- Users who prefer the LINE OA Manager web UI and do not want the extra complexity of an MCP server
| - 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 | - LINE Channel Access Token with full messaging, menu, audience, and coupon permissions
- Optional LINE MyShop API key for shopping tools
| - 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 | - A leaked Channel Access Token could allow an attacker to fully control your OA, including sending spam or deleting menus
- Sending large broadcasts may exceed LINE's quota limits
- HTTP transport without authentication could expose the service
- Image hosting depends on local machine or third-party services; if offline, images may become inaccessible
| - 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 clients | Claude Desktop, Claude Code, Claude Cowork, Cursor, Codex, ChatGPT, OpenClaw, Hermes | OpenAI ChatGPT, Claude, Cursor, GitHub Copilot, GitHub Copilot CLI, Google Gemini CLI, Amazon Quick Suite, Local MCP-compatible clients via mcp-remote |
|---|
| Tools | 50 | 0 |
|---|