Connect Velaro to Claude, Cursor, or another AI assistant (MCP)

Velaro's MCP server lets AI assistants (Claude Desktop, Claude Code, Cursor, VS Code Copilot, Moshky) read and take action in your Velaro account using natural language. You create a key once, paste a small config block into your client, and restart it.

Get your key first

1. Go to Settings → MCP Keys in Velaro.

2. Click Create MCP key, give it a label like "Claude Desktop" or "Cursor".

3. Copy the vel_live_... key that appears — it's shown only once. If you lose it, create a new one and revoke the old one.

One key per client. That way you can revoke Cursor without breaking Claude Desktop.

Hosted vs self-hosted — pick one

Hosted (recommended) — use Velaro's hosted endpoint. No Node.js install, always on the latest version. The client calls https://api-admin-us-east.velaro.com/mcp directly over HTTPS. Pick this unless you have a specific reason not to.

Self-hosted (npx) — the MCP server runs locally on your machine via npx @velaro/mcp-server. Pick this if you need the server to run inside a corporate/air-gapped network, want to pin a specific version, or prefer the server process to stay on-device. Requires Node.js 18+.

Both use the same key. You can switch anytime.

Claude Desktop

Config file:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Hosted block:

{
  "mcpServers": {
    "velaro": {
      "url": "https://api-admin-us-east.velaro.com/mcp",
      "headers": { "Authorization": "Bearer vel_live_..." }
    }
  }
}

Self-hosted block:

{
  "mcpServers": {
    "velaro": {
      "command": "npx",
      "args": ["-y", "@velaro/mcp-server"],
      "env": { "VELARO_MCP_KEY": "vel_live_..." }
    }
  }
}

Restart Claude Desktop. Ask it "list my Velaro conversations" to confirm.

Claude Code (CLI)

Run:

claude mcp add velaro --url https://api-admin-us-east.velaro.com/mcp --header "Authorization: Bearer vel_live_..."

Or hand-edit ~/.claude.json (macOS/Linux) or %USERPROFILE%\.claude.json (Windows). For project-local config, put a .mcp.json in the repo root.

Cursor

Config file: ~/.cursor/mcp.json (macOS/Linux) or %USERPROFILE%\.cursor\mcp.json (Windows). Same JSON shape as Claude Desktop above. Restart Cursor after editing.

VS Code (GitHub Copilot)

Config file: .vscode/mcp.json in the workspace root. Same JSON shape. Reload the window.

Moshky (Velaro's built-in AI Copilot)

Nothing to set up. Moshky already has access through your Velaro session. Just ask it things like "create an MCP key for me" or "walk me through connecting Claude Desktop" — it will guide you with these same steps.

Troubleshooting

"Invalid key" / 401 — regenerate the key in Settings → MCP Keys and paste the new value. Check you didn't include the quotes or trailing whitespace.

Client doesn't see the Velaro tools — most clients only reload MCP config on full restart. Quit the app completely (not just close the window) and reopen.

Key works but some actions fail — the key is site-isolated, so it can only touch data in the Velaro site it was created from. If you have multiple sites, create a separate key from each.

You want to revoke a key — Settings → MCP Keys, click Revoke next to the key. Takes effect immediately.