Mcp Server Atlassian… vs Horizun Revit MCP | AllMCPs
Side-by-Side Model Context Protocol Comparison
Mcp Server Atlassian Confluence vs Horizun Revit MCP
In-depth architectural comparison of the Mcp Server Atlassian Confluence and Horizun Revit MCP 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: 60/100 (Good) | Auth: API Key required
Horizun Revit MCP
Workplace & Productivity · Remote HTTP/SSE
Quality: 53/100 (Good) | Auth: No auth required
Verdict Summary: Choose Mcp Server Atlassian Confluence if you need specialized Workplace & Productivity tools running via a local process. Choose Horizun Revit MCP 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.
Atlassian Confluence Cloud integration. Enables AI systems to interact with Confluence spaces, pages, and content with automatic ADF to Markdown conversion.
Open-source MCP server for Autodesk Revit: typed BIM edits, families, exports and Power BI.
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, Horizun Revit MCP belongs to Workplace & Productivity using remote streaming HTTP/SSE transport. Select Mcp Server Atlassian Confluence when you need capabilities focused on workplace & productivity and Horizun Revit MCP 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/
Horizun Revit MCP Tools (46)
horizun_health
Is the bridge alive, and WHICH Revit is on the other end — year, build, our own version and commit, and the document active right now (an explicit null when none is).
get_document_info
The open document, its counts and identity.
horizun_open_document
Open a model, refusing a file saved in another Revit version (opening upgrades it irreversibly) and refusing a workshared central unless asked twice.
horizun_save_document
Save, then prove it: the file's timestamp and size before and after. On a workshared model it says, loudly, that this is not a synchronize.
horizun_relinquish_all
Give back everything this user owns, and count what is still owned afterwards rather than assume zero.
horizun_capture_view
Export a view and hand the IMAGE back, so the caller can look at the model instead of only reading it.
horizun_execute_python
The execution fallback: Python against the whole API on the UI thread, stdlib included. **Enabled by default**; an explicit off in `settings.json` is respected. `preflight=true` validates permission, document, size, hash and syntax without executing; the structured `__output__` evidence contract cl…
horizun_model_scan
The census, under the honesty contract.
horizun_write_params_verified
Parameter writes, each re-read after commit.
horizun_delete_verified
Deletion with the cascade counted, `dry_run` first.