Apps & connectors

Connect Cursor, Claude Code and other MCP clients

The same server, added from an editor, a terminal, or anything else that speaks MCP.

3 min read

Any client that speaks Model Context Protocol can use Vectra. They all need the same two facts — the URL and your key — and differ only in where you put them.

Claude Code

claude mcp add --transport http vectra https://api.vectragps.com/mcp \
  --header "X-API-Key: vgps_your_key_here"

Then run /mcp inside Claude Code — vectra should list as connected.

Cursor

Settings → MCP → Add new MCP server, or edit ~/.cursor/mcp.json directly with the block below.

{
  "mcpServers": {
    "vectra": {
      "url": "https://api.vectragps.com/mcp",
      "headers": { "X-API-Key": "vgps_your_key_here" }
    }
  }
}

The same file shape most desktop MCP clients use.

Anything else

Transport: streamable HTTP, stateless. No session id to hold.
Endpoint: POST https://api.vectragps.com/mcp. GET and DELETE answer 405 by design.
Auth: X-API-Key, or Authorization: Bearer with the same vgps_ key.
Rate limit: 120 requests a minute per key, which no interactive assistant will reach.

Keys end up in config files

An mcp.json usually sits in a repo or a home directory that gets backed up. Give editors a read-only key, and rotate it when a machine changes hands.

NextConnect your own JT808 tracker

Something here wrong or missing? Tell us — these pages are maintained by the people who answer the phone.