Skip to main content
The hosted MCP endpoint is: 
https://vimaspatial.tech/mcp
Health check: 
curl -sf https://vimaspatial.tech/mcp/health
Use /mcp/health for curl and browser checks. The /mcp route is the streamable HTTP MCP endpoint, so a plain GET without MCP event-stream headers can return 406 Not Acceptable even when the service is healthy.

​
Tools

ToolPurpose
vima_doctorChecks API health, CII summary, and spatial zones
vima_analyze_frameAnalyzes a sample, image URL, or base64 image
vima_compare_frameCompares Vima prompting against baseline prompting
vima_cii_summaryReturns wrench-time summary stats
vima_cii_framesReturns frame-level CII rows, optionally filtered by P, C, or NC
vima_spatial_zonesReturns zone-level spatial productivity evidence
vima_evalReturns temporal eval claims and baseline comparison

​
Deployment Shape

Caddy -> /mcp* -> mcp:8766
MCP   -> backend:8765
The server lives in packages/vima-mcp and runs as a small Docker Compose service next to the frontend and backend. In production, VIMA_API_URL points the MCP container at http://backend:8765; public clients reach it through https://vimaspatial.tech/mcp.

Tiny Runtime

FastMCP plus standard-library HTTP forwarding. No local inference stack.

Same Evidence Surface

MCP tools wrap the same hosted API used by the CLI and dashboard.

​
What Not to Add

Do not add any of these to the production MCP container:
  • torch
  • transformers
  • open3d
  • SAM
  • Depth Anything
  • local COLMAP or reconstruction runtime