Connect from Claude Code

The MCP server speaks streamable HTTP, which Claude Code connects to with a single command.

1. Get an API key

Create a workspace API key (vld_…) from the dashboard or the API-keys endpoints. Copy it — the plaintext is shown only once.

2. Add the server

claude mcp add --transport http veleads http://localhost:4000/mcp \
  --header "Authorization: Bearer vld_your_key_here"

• veleads is the local name for the connection (use anything you like).
• Swap the URL for your deployed host in non-local environments, e.g. https://api.velead.io/mcp.

To scope the connection to just the current project instead of your user config, add --scope local (the default) or --scope project to share it via a committed .mcp.json. Never commit a real API key — use --scope local for keys, or reference an environment variable.

3. Verify

claude mcp list

You should see veleads listed. Inside a Claude Code session you can then ask it to use the research_company tool, or list tools to confirm it's wired up.

4. Try it

Ask Claude Code something like:

Use the veleads research_company tool to research list list_abc123.

Claude Code will call the tool, which starts research across the list's records. See research_company for the full argument reference and what happens next.

Troubleshooting

Symptom	Likely cause
401 Could not resolve a workspace	The key isn't a valid workspace API key, or the header is missing.
Invalid or expired API key	Key revoked/expired, or Unkey isn't configured on the server.
405 Method not allowed	Something issued a GET/DELETE; the endpoint is POST-only (stateless).
Tool runs but cells never fill	The Hatchet worker isn't running (bun run worker:dev), or the AI gateway is disabled.