Two env vars and a JSON block

The server is a single stdio process — point your client at it, give it the API base and optionally a key, and the tools appear.

Install

npx -y @vectr/mcp

Node 18+ is enough — there is no daemon and no port; the client spawns the process and talks to it over stdio.

Environment

VECTR_API_URL: Backend base URL — https://api.vectr.bot for mainnet (the default is a localhost dev backend)
VECTR_API_KEY: Your vectr_ key — required only for the vectr_agent tool

Claude Desktop

{
  "mcpServers": {
    "vectr": {
      "command": "npx",
      "args": ["-y", "@vectr/mcp"],
      "env": {
        "VECTR_API_URL": "https://api.vectr.bot",
        "VECTR_API_KEY": "vectr_…"
      }
    }
  }
}

Cursor and other clients take the same block under their own MCP config key. Restart the client after saving — tools are listed at startup.

What works without a key

The four read tools — vectr_get_price, vectr_get_tokens, vectr_search_token, vectr_get_token — call public endpoints and work with no key at all. Only vectr_agent needs VECTR_API_KEY, because jobs are scoped to a wallet.

The key lives in the client, not in chat

Put the key in the MCP config env block — never paste it into a conversation. The server reads it at startup; the model never sees it, and every request goes out over the one connection the process owns.