MCP integration

Connect Lead Gatherer to the AI tools your team already uses.

Give compatible AI systems controlled access to searches and results through your Lead Gatherer workspace. Every request follows the permissions on your API key and plan.

Open API settings Read REST API docs

Illustrative product preview

Grouped research

Ready

three related markets

One campaign

Records

Structured

Contacts

When found

Export

CSV

Chicago dentistsReady

Evanston dentistsReview

Oak Park dentistsReview

Connection

One authenticated MCP endpoint.

Streamable HTTP endpoint

https://leadsgatherer.com/mcp

Copy the complete URL above. The connection authenticates every request. A localhost address is reachable only by clients on the same computer. Cloud-hosted clients require your public HTTPS deployment URL.

Authentication

Create a scoped key in Dashboard → API & integrations, then save it in your AI client's encrypted connection settings.

Authorization: Bearer lg_…

Plan access

Tools follow your plan and key permissions.

Growth · read access

list_research_jobs
get_research_job
preview_results
list_campaigns
get_usage

Professional · read and create

list_research_jobs
get_research_job
preview_results
list_campaigns
get_usage
create_research_job

Setup

Add Lead Gatherer as a remote MCP connection.

01
Create an API key with only the permissions the connection needs.
02
Choose Streamable HTTP in your AI client’s MCP or connector settings.
03
Paste the copied MCP URL. Add Authorization: Bearer followed by your API key.
04
Connect and confirm list_research_jobs appears. Start with a read-only request before enabling create actions.

Your AI client must support remote MCP over Streamable HTTP and a custom Authorization header. Menu names and availability vary by client. Keep API keys in the client's secret store and never paste them into a chat message.

Generic remote connection

{
  "url": "https://leadsgatherer.com/mcp",
  "headers": {
    "Authorization": "Bearer lg_YOUR_KEY"
  }
}

Replace lg_YOUR_KEY with your key in the client’s secret settings. This example is a connection description, not a configuration file accepted by every client.

VS Code

Configure a local VS Code connection.

Save this as .vscode/mcp.json, then open the Command Palette and run MCP: List Servers. Start lead-gatherer, enter your API key when prompted, and review its tools. This uses the local extension-host configuration; agent-host sessions do not forward interactive input variables.

.vscode/mcp.json

{
  "servers": {
    "lead-gatherer": {
      "type": "http",
      "url": "https://leadsgatherer.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:lead-gatherer-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "lead-gatherer-key",
      "description": "Lead Gatherer API key",
      "password": true
    }
  ]
}

VS Code configuration reference

Troubleshooting

Know what to check if the connection fails.

Cannot connect: confirm the URL ends in /mcp and is reachable from the client’s computer. A cloud client cannot access this PC’s localhost.
Unauthorized: use an active API key, not your account password. Check the Bearer prefix and replace a revoked key.
No create tool: Growth is read-only. Professional also requires jobs:write permission and an owner/admin workspace role for creating searches.
Opening the URL shows an error: normal browser navigation sends GET. MCP clients use POST; a 405 response in your browser alone does not mean the connection is broken.
Client asks for OAuth: this endpoint uses API-key authentication. Use a client that accepts a custom Authorization header; an OAuth-only connector is not supported.

Get connection help

Protocol

Connection requirements.

Required headers

Authorization: Bearer lg_YOUR_KEY
Content-Type: application/json
Accept: application/json, text/event-stream

Initialization sequence

01. Send an initialize request.
02. Send notifications/initialized.
03. Call tools/list to confirm available tools.
04. Start tool calls using the same authorization header.

Security

Workspace boundaries remain enforced.

Cannot switch workspaces

Cannot read infrastructure credentials

Cannot access administrator diagnostics

Cannot create or reveal API keys

Cannot change billing or team roles

Returns bounded result previews

For endpoint examples, continue to the REST API documentation.

Ready when you are

Bring business research into your AI-assisted workflows.

Open API & integrations to create a scoped key, then add the remote MCP connection in a compatible AI client.

Open API settings Review pricing