Side-by-Side Model Context Protocol Comparison
Address vs Navisworks
In-depth architectural comparison of the Address and Navisworks 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
Address
Developer Tools · Local stdio
Quality: 41/100 (Fair) | Auth: No auth required
Navisworks
Developer Tools · Remote HTTP/SSE
Quality: 45/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Address if you need specialized Developer Tools tools running via a local process. Choose Navisworks if your workspace requires Developer Tools integration with remote web transport. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
A
Choose Address when:
- You need dedicated capabilities in the Developer Tools domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
N
Choose Navisworks when:
- You need dedicated capabilities in the Developer Tools domain.
- You prefer remote streaming HTTP/SSE transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- Primary tools included: nwd_upload, nwd_get_clashes, nwd_export_report.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Address Tools (0)
No explicit tool names declared in metadata yet. Check project README on main listing page.
Navisworks Tools (5)
nwd_upload
Upload NWD files for coordination
nwd_get_clashes
Extract clash detection results
nwd_export_report
Generate coordination reports (PDF/XLSX/HTML)
nwd_get_viewpoints
Retrieve saved viewpoints
nwd_list_objects
List model objects and properties
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).
Address Configuration
Navisworks Configuration