In-depth architectural comparison of the MCP Server Atlassian Confluence and CasaCaddy 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: 63/100 (Good) | Auth: API Key required
CasaCaddy
Workplace & Productivity · Remote HTTP/SSE
Quality: 69/100 (Great) | Auth: OAuth 2.0
Verdict Summary: Choose MCP Server Atlassian Confluence if you need specialized Workplace & Productivity tools running via a local process. Choose CasaCaddy 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.
Atlassian Confluence Cloud integration. Enables AI systems to interact with Confluence spaces, pages, and content with automatic ADF to Markdown conversion.
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 is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, CasaCaddy belongs to Workplace & Productivity using remote streaming HTTP/SSE transport. Select MCP Server Atlassian Confluence when you need capabilities focused on workplace & productivity and CasaCaddy when you require tools for workplace & productivity.
Replace Confluence resources (full update). Returns TOON format by default.
**IMPORTANT - Cost Optimization:**
- Use `jq` param to extract only needed fields from response
- Example: `jq: "{id: id, version: version.number}"`
**Output format:** TOON (default) or JSON (`outputFormat: "json"`)
**Common operations:**
1. **Update page:** `/wiki/api/v2/pages/{id}`
body: `{"id": "123", "status": "current", "title": "Updated Title", "spaceId": "456", "body": {"representation": "storage", "value": "<p>Content</p>"}, "version": {"number": 2}}`
Note: version.number must be incremented
2. **Update blog post:** `/wiki/api/v2/blogposts/{id}`
Note: PUT replaces entire resource. Version number must be incremented.
API reference: https://developer.atlassian.com/cloud/confluence/rest/v2/
conf_patch
Partially update Confluence resources. Returns TOON format by default.
**IMPORTANT - Cost Optimization:** Use `jq` param to filter response fields.
**Output format:** TOON (default) or JSON (`outputFormat: "json"`)
**Common operations:**
1. **Update space:** `/wiki/api/v2/spaces/{id}`
body: `{"name": "New Name", "description": {"plain": {"value": "Desc", "representation": "plain"}}}`
2. **Update comment:** `/wiki/api/v2/footer-comments/{id}`
Note: Confluence v2 API primarily uses PUT for updates.
API reference: https://developer.atlassian.com/cloud/confluence/rest/v2/
conf_delete
Delete Confluence resources. Returns TOON format by default.
**Output format:** TOON (default) or JSON (`outputFormat: "json"`)
**Common operations:**
- `/wiki/api/v2/pages/{id}` - Delete page
- `/wiki/api/v2/blogposts/{id}` - Delete blog post
- `/wiki/api/v2/pages/{id}/labels/{label-id}` - Remove label
- `/wiki/api/v2/footer-comments/{id}` - Delete comment
- `/wiki/api/v2/attachments/{id}` - Delete attachment
Note: Most DELETE endpoints return 204 No Content on success.
API reference: https://developer.atlassian.com/cloud/confluence/rest/v2/
CasaCaddy Tools (3)
get_connected_installation
Identify the linked CasaCaddy Pro installation and its current maintenance-guide allowance. No device identifier, billing data, on-device home library, appliance list or task history is exposed.
get_maintenance_guide
Use the linked Pro installation to request a maintenance guide for the appliance details and question the user supplied. Ask for confirmation before using existing Pro allowance; a fresh guide uses that allowance and the existing external model pipeline. Existing exact-input cached guides are unmetered. Supply a fresh UUID request_key and reuse it for retries: identical-key results are persisted, so a retry never starts a second provider request. Preserve safetyWarnings, step cautions, whenToCallPro and call_a_pro difficulty. This does not read on-device appliances or schedule tasks.
get_saved_guide_request
Recover one maintenance-guide request made through MCP by the linked installation, using its exact request_key. Only that installation’s request records are returned, for up to 30 days. Does not start generation, consume allowance or read the on-device library. Keep all safety warnings and professional-help boundaries intact.