Intent Leads

Intent Leads (intentleads.si): B2B intent data and leads for AI agents. See how many US decision-makers are researching your topics, get free quotes, and export leads with emails and mobiles. 100% usage-based: pay per lead, no subscription. Only intent_export_leads spends your balance.

Serveur MCP hébergé

npx add-mcp 'https://mcp.intentleads.si/mcp'

S’installe dans Claude Code, Codex, Cursor et plus

Documentation

MCP for AI agents

Let Claude, Cursor or your own agent check lanes, quote and run exports.

Intent Leads has an MCP server, so an AI agent can work with your lanes, counts, exports and leads in plain language: "How many new high-intent people does L3 have? Export 50 and give me the CSV."

https://mcp.intentleads.si/mcp

It uses streamable HTTP, and you sign in with one of your Intent Leads API keys (il_live_…) sent as a bearer token. There's no separate MCP key: create a key under Settings → API keys, or use one you already have. The agent then sees exactly what that key sees, so a workspace key only reaches its own workspace. To give an agent several workspaces, use an organization key and name the workspace in each tool call.

The API keys tab, with the Connect panel's API, CLI and AI agent tabs

Settings → API keys: create a key, then Connect → AI agent has the setup to copy.

Connect your agent

[tab] Claude Code

claude mcp add --transport http intent-leads https://mcp.intentleads.si/mcp \
  --header "Authorization: Bearer il_live_YOUR_API_KEY"

[tab] Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "intent-leads": {
      "url": "https://mcp.intentleads.si/mcp",
      "headers": { "Authorization": "Bearer il_live_YOUR_API_KEY" }
    }
  }
}

[tab] VS Code

Add to .vscode/mcp.json:

{
  "servers": {
    "intent-leads": {
      "type": "http",
      "url": "https://mcp.intentleads.si/mcp",
      "headers": { "Authorization": "Bearer il_live_YOUR_API_KEY" }
    }
  }
}

[tab] Claude Desktop

Claude Desktop connects to remote servers with a header through mcp-remote (needs Node.js). Add to claude_desktop_config.json:

{
  "mcpServers": {
    "intent-leads": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.intentleads.si/mcp", "--header", "Authorization: Bearer il_live_YOUR_API_KEY"]
    }
  }
}

How agents find the tools

The server keeps your agent's context small: it exposes a few general tools, and the agent looks up the Intent Leads tools it needs.

ToolWhat it's for
search_toolsFind tools by keyword, like search_tools("export").
get_tool_schemaThe exact parameters of one tool.
call_toolRun a tool by name, with its parameters as JSON.

A good first call is call_tool("intent_how_to_use_me", "{}"): it explains lanes, counts and exports to the agent.

Every Intent Leads tool takes an optional workspace (a workspace id). With an organization's key it says which workspace to work in; intent_list_workspaces lists them. A workspace's own key doesn't need it.

Intent Leads tools

ToolSpends your balanceWhat it does
intent_how_to_use_meNoStart here: how lanes, counts and exports work.
intent_list_lanesNoLanes with live keywords and how many new people are available now.
intent_get_laneNoOne lane: filters, keywords and the funnel.
intent_lane_sampleNoUp to 25 example matches, without names or contact details.
intent_quote_exportNoFree quote: how many people an export would get.
intent_export_leadsYesStarts an export. The only tool that spends your balance.
intent_list_exportsNoPast exports, newest first.
intent_get_exportNoOne export and its leads (JSON or CSV).
intent_pull_leadsNoLeads you haven't pulled yet, or everything since a date.
intent_list_suppressionsNoPeople who asked to be removed.
intent_get_balanceNoYour balance, this month per meter, and the prices.
intent_estimate_costNoWhat N more people would cost now (free).
intent_list_filter_valuesNoValid industries, seniority and strengths, and every field more filters can use.
intent_create_laneNoCreate a lane.
intent_update_laneNoChange a lane's filters, more filters (conditions) or settings.
intent_search_topicsNoTopics we already track, to use before adding new keywords.
intent_get_topicNoWhat one topic covers and its size.
intent_add_keywordNoAdd an existing topic (topic) or a new keyword to a lane, optionally to group B, C or D.
intent_move_keywordNoMove a keyword to another group.
intent_run_checkNoRe-size a lane now, after changing filters.
intent_remove_keywordNoRemove a keyword from a lane.
intent_get_exclusionsNoCompanies and people left out of every lane.
intent_add_exclusionsNoLeave out companies (domains) or people (emails) on every lane.
intent_remove_exclusionsNoStop leaving them out.
intent_list_workspace_membersNoWho can open a workspace (organization or workspace users) and its open invites. Admin key.
intent_list_webhooksNoYour webhook endpoints (URL, events, status, what's waiting) and the event types.
intent_test_webhookNoSend a signed test to one endpoint (a ping or a made-up sample) and get what it answered.

[!WARNING]

intent_export_leads spends your balance. Its description tells agents to run intent_quote_export first and get your go-ahead, but review what your agent is allowed to do without asking you.

Example prompts

  • "Which of my lanes has the most new high-intent people this week?"
  • "Show me a sample for L2. Do these look like VPs of sales at SaaS companies?"
  • "Quote an export of 100 from all lanes, then export it if it costs under $10, and save the CSV."
  • "Find existing topics about answering services and add the best two to L1."
  • "Add the keyword 'outbound agency pricing' to L1."
  • "In L2, only keep people in sales or business development at companies with $10M+ revenue, then re-check it."
  • "Did anyone ask to be removed since Monday? Give me their lead IDs."
  • "Leave out every company in this CSV of our current customers."

This documentation is built and hosted on Mintlify, a developer documentation platform.