mcpField
N
navisworks

navisworks

Remote
github.com/ScanBIM-LabsMedia & Design0Updated 27w ago
Repository

About navisworks

navisworks is an MCP server for Navisworks coordination through APS. It lets AEC teams upload NWD files, inspect clashes and model objects, and retrieve viewpoints or reports.

Key features

  1. 01Upload NWD files
  2. 02Extract clash results
  3. 03Export PDF, XLSX, and HTML reports
  4. 04Retrieve saved viewpoints
  5. 05List model objects and properties

Use cases

  1. 01Review clash detection results
  2. 02Create coordination reports
  3. 03Inspect model objects and properties

MCP support

Exposes Navisworks file upload, clash extraction, report export, viewpoint retrieval, and object listing as tools for MCP clients.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.scanbimlabs.io/navisworks
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

All endpoints
Streamable HTTPhttps://mcp.scanbimlabs.io/navisworksAuth required

Tools

Details

From the project README

Navisworks MCP

Navisworks coordination and clash detection via APS — Upload NWD files, extract clashes, generate reports, retrieve viewpoints.

Live MCP

Tools (5)

ToolDescription
nwd_uploadUpload NWD files for coordination
nwd_get_clashesExtract clash detection results
nwd_export_reportGenerate coordination reports (PDF/XLSX/HTML)
nwd_get_viewpointsRetrieve saved viewpoints
nwd_list_objectsList model objects and properties

Quick Start

{
  "mcpServers": {
    "navisworks": {
      "url": "https://navisworks-mcp.itmartin24.workers.dev/mcp"
    }
  }
}

Architecture

  • Runtime: Cloudflare Workers
  • Auth: APS OAuth2 (client_credentials)

Part of ScanBIM Labs AEC MCP Ecosystem

MIT — ScanBIM Labs LLC

Authentication

Two accepted header formats. Use one, do NOT mix:

  1. x-scanbim-api-key: <your_user_key> — value is the user_key verbatim.
  2. Authorization: Bearer sk_scanbim_<your_user_key> — value is the entire string including the sk_scanbim_ prefix; the D1 user_key column must match this full string.

Mixing formats auto-creates a fresh free-plan row for the alternate key (you'll silently get a new 50-credit account on each switch).

Get your user_key at scanbim.app/settings/billing.

Example
curl -X POST https://mcp.scanbimlabs.io/unified/mcp \
  -H "content-type: application/json" \
  -H "x-scanbim-api-key: $SCANBIM_USER_KEY" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"list_models","arguments":{}}}'
Response codes
  • 200 — tool call proceeded; credits debited.
  • 401 — missing or malformed auth header (middleware returns JSON-RPC error code -32001).
  • 402 — insufficient credits; response body includes checkout_urls for all 5 credit packs and top_up_url for the billing page.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.