A side-by-side look at the A2atlassian and Anytype MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose A2atlassian for workplace & productivity work as a local process; choose Anytype MCP for workplace & productivity as a local process. You can also run both side by side in one mcpServers block.
login, logout, list_connections.OPENAPI_MCP_HEADERS.Authorization, Anytype-Version, OPENAPI_MCP_HEADERS.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 47/100 · Fair | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | OPENAPI_MCP_HEADERS |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 526 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 39 | 11 |
| Full listing | View A2atlassian | View Anytype MCP |
loginSave a connection — validates by calling /myself firstlogoutRemove a saved connectionlist_connectionsList connections (no secrets exposed)jira_get_issueGet issue by key — full fields, status, assigneejira_searchSearch by JQL with pagination — compact TSV output by defaultjira_search_countCount-only JQL — cheap pre-check for "is this going to be huge?"jira_search_fieldsDiscover custom-field IDs by namejira_get_field_optionsList allowed values for a select / multi-select fieldjira_get_commentsGet all comments for an issuejira_get_worklogsGet all worklogs for an issuejira_get_transitionsDiscover available status transitionsjira_get_link_typesList available issue-link typesAuthorizationAnytype-VersionOPENAPI_MCP_HEADERSexpected_etagIf-Matchrequest_metadatarequest_keyIdempotency-Keydry_runcreate_missing_optionsauth_whoamiPaste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"a2atlassian": {
"command": "uvx",
"args": [
"--from",
"a2atlassian",
"a2atlassian-mcp"
]
}
}
}
{
"mcpServers": {
"anytype-mcp": {
"command": "npx",
"args": [
"-y",
"@anyproto/anytype-mcp"
],
"env": {
"OPENAPI_MCP_HEADERS": "YOUR_OPENAPI_MCP_HEADERS_HERE"
}
}
}
}