Model Context Protocol

Vecaria MCP Server

Vecaria exposes 136 engineering file tools — CAD, EDA, GIS, 3D, point clouds and PDF — as a single MCP server. Agents in Claude, Cursor or ChatGPT can list and call the tools over Streamable HTTP. Read-only tools work anonymously; write and export operations require an API token.

API & MCP docs OpenAPI spec Browse all tools

Endpoint

Streamable HTTP (JSON-RPC), no client state required:

https://vecaria.com/api/mcp

Quick start

Claude Code — run:

claude mcp add --transport http vecaria https://vecaria.com/api/mcp

Cursor — Settings → Tools & MCP → Add Custom MCP, paste:

{
  "vecaria": {
    "url": "https://vecaria.com/api/mcp",
    "transport": "http"
  }
}

ChatGPT / other clients — point the client at the endpoint above; the server speaks standard MCP initialize / tools/list / tools/call.

What agents can do

List all 136 tools with generated input schemas (tools/list).
Call server-side tools (e.g. DXF→SVG, STEP→STL, Gerber DFM) anonymously in read-only mode.
Authenticate with an API token (vk_…, Bearer header) to unlock write/export operations and queue-based execution.
Manage batches and workflows through MCP with a mcp:write-scoped token.

Privacy posture

The interactive tools on vecaria.com parse files locally in your browser. MCP-invoked server-side tools are the documented exception: files are uploaded to the processing queue and deleted after processing. See Privacy and Security.