| FMRS | 58 / 100 · C | 66 / 100 · C |
|---|
| Reliability | 7 / 20 | 8 / 20 |
|---|
| Security and permissions | 10 / 20 | 15 / 20 |
|---|
| Maintenance | 12 / 20 | 15 / 20 |
|---|
| Documentation | 15 / 20 | 15 / 20 |
|---|
| Setup experience | 14 / 20 | 13 / 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
| - 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 | - 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 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 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
| - 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 | - 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
| - 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 | OpenAI ChatGPT, Claude, Cursor, GitHub Copilot, GitHub Copilot CLI, Google Gemini CLI, Amazon Quick Suite, Local MCP-compatible clients via mcp-remote |
|---|
| Tools | 12 | 0 |
|---|