Side-by-Side Model Context Protocol Comparison
MCP Server Atlassian Confluence vs Clickup Cli
In-depth architectural comparison of the MCP Server Atlassian Confluence and Clickup Cli MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
MCP Server Atlassian Confluence
Workplace & Productivity · Local stdio
Quality: 59/100 (Good) | Auth: API Key required
Clickup Cli
Workplace & Productivity · Remote HTTP/SSE
Quality: 53/100 (Good) | Auth: API Key required
Verdict Summary: Choose MCP Server Atlassian Confluence if you need specialized Workplace & Productivity tools running via a local process. Choose Clickup Cli if your workspace requires Workplace & Productivity integration with remote web transport. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
Choose MCP Server Atlassian Confluence when:
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
- You have access to required keys:
ATLASSIAN_SITE_NAME, ATLASSIAN_USER_EMAIL, ATLASSIAN_API_TOKEN, DEBUG. - Primary tools included: conf_get, conf_post, conf_put.
Choose Clickup Cli when:
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer remote streaming HTTP/SSE transport architecture.
- Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
- You have access to required keys: .
Feature & Specification Comparison
Tools & Capabilities Breakdown
MCP Server Atlassian Confluence Tools (5)
conf_get
Read any Confluence data. Returns TOON format by default (30-60% fewer tokens than JSON).
**IMPORTANT - Cost Optimization:**
- ALWAYS use `jq` param to filter response fields. Unfiltered responses are very expensive!
- Use `limit` query param to restrict result count (e.g., `limit: "5"`)
- If unsure about available fields, first fetch ONE item with `limit: "1"` and NO jq filter to explore the schema, then use jq in subsequent calls
**Schema Discovery Pattern:**
1. First call: `path: "/wiki/api/v2/spaces", queryParams: {"limit": "1"}` (no jq) - explore available fields
2. Then use: `jq: "results[*].{id: id, key: key, name: name}"` - extract only what you need
**Output format:** TOON (default, token-efficient) or JSON (`outputFormat: "json"`)
**Common paths:**
- `/wiki/api/v2/spaces` - list spaces
- `/wiki/api/v2/pages` - list pages (use `space-id` query param)
- `/wiki/api/v2/pages/{id}` - get page details
- `/wiki/api/v2/pages/{id}/body` - get page body (`body-format`: storage, atlas_doc_format, view)
- `/wiki/rest/api/search` - search content (`cql` query param)
**JQ examples:** `results[*].id`, `results[0]`, `results[*].{id: id, title: title}`
API reference: https://developer.atlassian.com/cloud/confluence/rest/v2/
conf_post
Create Confluence resources. Returns TOON format by default (token-efficient).
**IMPORTANT - Cost Optimization:**
- Use `jq` param to extract only needed fields from response (e.g., `jq: "{id: id, title: title}"`)
- Unfiltered responses include all metadata and are expensive!
**Output format:** TOON (default) or JSON (`outputFormat: "json"`)
**Common operations:**
1. **Create page:** `/wiki/api/v2/pages`
body: `{"spaceId": "123456", "status": "current", "title": "Page Title", "parentId": "789", "body": {"representation": "storage", "value": "<p>Content</p>"}}`
2. **Create blog post:** `/wiki/api/v2/blogposts`
body: `{"spaceId": "123456", "status": "current", "title": "Blog Title", "body": {"representation": "storage", "value": "<p>Content</p>"}}`
3. **Add label:** `/wiki/api/v2/pages/{id}/labels` - body: `{"name": "label-name"}`
4. **Add comment:** `/wiki/api/v2/pages/{id}/footer-comments`
API reference: https://developer.atlassian.com/cloud/confluence/rest/v2/
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
MCP Server Atlassian Confluence Configuration
Clickup Cli Configuration
Frequently Asked Questions
More alternatives to MCP Server Atlassian ConfluenceMore alternatives to Clickup CliWorkplace & Productivity category hub