Connect an MCP client

Every client needs two things: the server URL https://core.leadveyor.com/mcp and an API key sent as Authorization: Bearer lv_live_….

1. Create a key

In the console, open API keys and create a key for the assistant:

  • Permission — read to look only, write to also process messages, record outcomes and edit profiles. See Permissions.
  • Workspace — keep the key to the current workspace unless the assistant must work across several businesses.
  • Test key — on while you try things out; the assistant's changes then stay in test data.

Copy the key: it is shown once.

2. Add the server to your client

Claude Code

claude mcp add --transport http leadveyor https://core.leadveyor.com/mcp \
  --header "Authorization: Bearer lv_live_…"

Add --scope user to use it in every project. Check the connection with /mcp inside Claude Code.

Cursor

In ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "leadveyor": {
      "url": "https://core.leadveyor.com/mcp",
      "headers": { "Authorization": "Bearer lv_live_…" }
    }
  }
}

VS Code

In .vscode/mcp.json. The input prompts for the key once and keeps it out of the file:

{
  "inputs": [
    { "type": "promptString", "id": "leadveyor-key", "description": "Leadveyor API key", "password": true }
  ],
  "servers": {
    "leadveyor": {
      "type": "http",
      "url": "https://core.leadveyor.com/mcp",
      "headers": { "Authorization": "Bearer ${input:leadveyor-key}" }
    }
  }
}

Claude Desktop

Claude Desktop's configuration file starts local servers, so connect through the mcp-remote bridge (needs Node.js). In claude_desktop_config.json (Settings → Developer → Edit config):

{
  "mcpServers": {
    "leadveyor": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://core.leadveyor.com/mcp",
        "--header", "Authorization:${LEADVEYOR_AUTH}"
      ],
      "env": { "LEADVEYOR_AUTH": "Bearer lv_live_…" }
    }
  }
}

Restart Claude Desktop; Leadveyor's tools appear in the tools menu.

Claude API (MCP connector)

Claude can call Leadveyor's tools directly from a Messages API request — Anthropic connects to the server for you:

curl https://api.anthropic.com/v1/messages \
  -H "x-api-key: $ANTHROPIC_API_KEY" \
  -H "anthropic-version: 2026-10-21" \
  -H "anthropic-beta: mcp-client-2025-11-20" \
  -H "content-type: application/json" \
  -d '{
    "model": "claude-opus-5-5",
    "max_tokens": 16000,
    "mcp_servers": [
      { "type": "url", "url": "https://core.leadveyor.com/mcp", "name": "leadveyor", "authorization_token": "lv_live_…" }
    ],
    "tools": [ { "type": "mcp_toolset", "mcp_server_name": "leadveyor" } ],
    "messages": [ { "role": "user", "content": "Summarise the hot leads that have no outcome yet." } ]
  }'

authorization_token is sent to Leadveyor as the bearer token.

Your own agent

Any MCP client library works. With the official TypeScript SDK:

import { Client } from '@modelcontextprotocol/sdk/client/index.js'
import { StreamableHTTPClientTransport } from '@modelcontextprotocol/sdk/client/streamableHttp.js'

const client = new Client({ name: 'my-agent', version: '1.0.0' })
await client.connect(
  new StreamableHTTPClientTransport(new URL('https://core.leadveyor.com/mcp'), {
    requestInit: { headers: { Authorization: `Bearer ${process.env.LEADVEYOR_API_KEY}` } },
  }),
)

const { tools } = await client.listTools()
const result = await client.callTool({ name: 'search_leads', arguments: { tier: 'hot', outcome: 'none' } })
console.log(result.content[0].text)

Other clients

Use these settings in any client that supports remote MCP servers over HTTP:

SettingValue
Type / transportStreamable HTTP (sometimes called "http")
URLhttps://core.leadveyor.com/mcp
HeaderAuthorization: Bearer lv_live_…
Optional headerLeadveyor-Workspace: ws_… — default workspace for an account-wide key

Clients that connect only with an OAuth sign-in — such as custom connectors in the Claude and ChatGPT web apps — can't use an API key. Use one of the clients above, or the mcp-remote bridge where the app can start local servers.

3. Try it

Ask the assistant something simple first:

  • "List my Leadveyor profiles."
  • "Show the last five leads with their tier and score."
  • "Score this message without saving it: Hi, we're planning a wedding for 120 guests on 14 March in Paddington, budget around $15k."

If the tools don't show up, check the key: the server answers 401 to a missing, mistyped or revoked key, and most clients then show the server as failed. A 403 permission_error on a tool call means the key's permission is too low for that tool.

Account-wide keys

With an account-wide key, either add Leadveyor-Workspace: ws_… to the headers above, or tell the assistant which workspace to use — it passes workspaceId to each tool and can list workspaces with manage_workspaces.

Was this page helpful?