Developers

MCP server

Early access

The server is not live yet. The address below is where it will answer.

Server URLhttps://mcp.voxelspatiallabs.com/mcp

What an agent can do

Create a design from a sentence, follow the run, read the gate report, propose a change and see what it would re-run and cost, then apply it with the user's approval. Anything that spends credits or requests a release is marked as consequential.

01
create_design
The agent sends the user's description. It gets a design id and a task handle for the first run.
02
get_run_status
It polls the task until the run completes or a gate blocks it.
03
get_gate_report
A gate is blocked. The report names the check, the measured value, the threshold and a suggested fix.
04
propose_change
The agent turns the suggested fix into a change plan: what changes, which stages and gates re-run, the estimated credits.
05
apply_change
This tool is consequential, so the client asks the user before calling it. On approval the affected stages re-run.
06
get_bom
With every gate passing, the agent fetches the bill of materials for the user.

Connect

Pick your client. Each snippet uses the server URL from this site's configuration.

Claude Code

Adds the server to the current project. Use the second form to make it available in every project.

shell

claude mcp add --transport http anubis https://mcp.voxelspatiallabs.com/mcp

shell, all projects

claude mcp add --transport http anubis --scope user https://mcp.voxelspatiallabs.com/mcp

Claude on the web and Claude Desktop

Open Customize, then Connectors.
Click Add, then Add custom connector.
Name it Anubis and paste the server URL, then Continue.
Review the detected authentication settings and click Add.

Remote connectors are configured through your Claude account, so one setup covers the web app and the desktop app. On Team and Enterprise plans an owner adds it under Organization settings first.

Cursor

Save as .cursor/mcp.json in the project, or ~/.cursor/mcp.json for every project.

.cursor/mcp.json

{
  "mcpServers": {
    "anubis": {
      "url": "https://mcp.voxelspatiallabs.com/mcp"
    }
  }
}

Codex

One command, or the same entry in ~/.codex/config.toml.

shell

codex mcp add anubis --url https://mcp.voxelspatiallabs.com/mcp

~/.codex/config.toml

[mcp_servers.anubis]
url = "https://mcp.voxelspatiallabs.com/mcp"

Tools

Tools carry read-only or consequential annotations. Clients are expected to ask the user before calling a consequential tool.

MCP tools
Tool	Annotation	What it does
create_design	Consequential	Create a design from a natural-language spec and start its first run.
get_run_status	Read-only	Status per stage and gate for a run. Long runs return a task handle.
propose_change	Read-only	Turn a natural-language change into a change plan. Nothing is applied.
apply_change	Consequential	Apply a change plan. Spends credits; clients ask the user first.
get_assumptions	Read-only	Every value Anubis filled in, with its source.
get_gate_report	Read-only	Gate results with evidence.
get_bom	Read-only	Bill of materials.
list_artifacts	Read-only	Artifacts by domain.
get_artifact	Read-only	Fetch one artifact (a review copy until the design is released).
request_release	Consequential	Start an authorized engineering review. Clients ask the user first.

Transport, authorization and credits

Transport: Streamable HTTP, targeting the current MCP specification. Long runs use the MCP Tasks extension, so an agent gets a task handle instead of a timed-out call.
Authorization: OAuth 2.1. Clients discover the authorization server from the protected-resource metadata at /.well-known/oauth-protected-resource and sign in with the same account as the workspace.
Credits: Billed in the same credits as the workspace. A change plan states its estimated cost before anything runs, and manufacturing files stay locked until a release is approved.

Later, MCP Apps will let a client show the workspace tabs inline. The same actions are available over HTTP today. See the REST API.