LeadIQ

Live

API KEY

PROSPECTING

CRM & Sales

Every verified contact, company insight, and buyer signal your team captures lives in LeadIQ. LeadIQ MCP gives your agent authenticated access to prospecting data scoped to the user who authorized it.

  • Acts as the user: Access and write actions stay tied to the LeadIQ account that authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: User permissions enforced. 90-day audit trail.
LeadIQ
agent · Acme Q3
Run
Find all VP of Engineering prospects at Series B fintech companies with verified email.
S
leadiq_prospects_search
88ms
Prospecting agent
14 prospects found. Top: James Park (VP Eng, FinFlow, james@finflow.io, 180 employees), Sarah Chen (VP Eng, PayStack Pro, verified), Maria Santos (VP Eng, LoanBridge, verified). All have LinkedIn confirmed.
Sources: 14 prospects, Series B fintech
leadiqmcp
14 prospects
18:29
Message Claude...

Tools your prospecting agent reaches for on LeadIQ, scoped per user.

CALL ANY TOOL
Search and enrich prospects, get company data, track accounts, and surface buyer signals.
leadiq_prospects_search
Search prospects
Search for prospects by title, company, or keyword.
Parameters
Name
Type
Required
Description
query
string
Optional
Search query
title
string
Optional
Job title filter
company
string
Optional
Company name filter
limit
integer
Optional
Max results
leadiq_contact_enrich
Enrich contact
leadiq_company_get
Get company data
leadiq_account_track
Track account
leadiq_signals_get
Get buyer signals
Build your Agent
Drop the toolkit in, point it at the user, and your prospecting agent can use LeadIQ from the first run.
import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["leadiq"], toolNames: ["leadiq_prospects_search", "leadiq_contact_enrich", "leadiq_company_get"] },
pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
name: t.tool.definition.name,
description: t.tool.definition.description,
schema: z.object({}).passthrough(),
func: async (args) => {
const { data } = await sk.tools.executeTool({
toolName: t.tool.definition.name,
identifier: "user_123",
params: args,
});
return JSON.stringify(data);
},
}));

const agent = createReactAgent({ llm, tools: lcTools });
import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["leadiq"], toolNames: ["leadiq_prospects_search", "leadiq_contact_enrich", "leadiq_company_get"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
type: "function",
function: {
name: t.tool.definition.name,
description: t.tool.definition.description,
parameters: t.tool.definition.input_schema,
},
}));

const resp = await openai.responses.create({
model: "gpt-4o", input: prompt, tools: llmTools,
});
import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["leadiq"], toolNames: ["leadiq_prospects_search", "leadiq_contact_enrich", "leadiq_company_get"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
name: t.tool.definition.name,
description: t.tool.definition.description,
input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
model: "claude-sonnet-4-6", max_tokens: 1024,
tools: llmTools,
messages: [{ role: "user", content: prompt }],
});
import { Agent } from "@google/adk/agents";
import {
MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
connectionParams: new StreamableHTTPConnectionParams({
url: "https://mcp.scalekit.com/leadiq",
headers: { Authorization: `Bearer ${userScopedToken}` },
}),
});

const agent = new Agent({
name: "agent", model: "gemini-2.0-flash",
tools: await toolset.getTools(),
});
Try these prompts
Paste any prompt into your agent to start using LeadIQ.
Prospecting
Copy the prompt
Copied
Find VP of Engineering prospects at Series B companies.
Copy the prompt
Copied
Enrich contact [email] with company data.
Copy the prompt
Copied
Search for [title] at [company].
Copy the prompt
Copied
Get company profile for [domain].
Signals & tracking
Copy the prompt
Copied
Which tracked accounts have job change signals this week?
Copy the prompt
Copied
Add [company] to tracking list.
Copy the prompt
Copied
Find new hires at [account] this month.
Copy the prompt
Copied
Which accounts have expansion signals?
Reporting
Copy the prompt
Copied
How many enrichments used this month?
Copy the prompt
Copied
Top 10 prospects by fit score.
Copy the prompt
Copied
Find prospects at companies hiring for [role].
Copy the prompt
Copied
List tracked accounts with no signals in 30 days.
SEE HOW AUTH WORKS
Users authorize LeadIQ once. Their credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
LeadIQ
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
LeadIQ
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
LeadIQ
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
LeadIQ
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
Same per-user auth pattern across other prospecting agents and MCP connectors. Working code, live demos, fork what fits.
SALES
Outbound prospecting agent
Build targeted prospect lists with Apollo, enrich with firmographic data, and draft personalised outreach. Runs on a schedule.
SALES
Sales call prep agent
Pull Granola notes and Attio contact history to draft a pre-call brief before every sales meeting. Zero rep input.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.
// shared token
 audit → bot_service_account
 user_filter → broken

 // scalekit
 audit → user_abc
 scope → enforced ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
LeadIQ today. Others tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access LeadIQ as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.
Where is the LeadIQ api key stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.
Can I limit what the agent is allowed to do in LeadIQ?
Yes. Pass a tool name filter to listScopedTools so the prospecting agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches LeadIQ.
What happens when a user revokes LeadIQ access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.
Do enrichment credits apply per user or are they shared across the workspace?
Credit usage applies to the account the authorizing user's API key belongs to. Scalekit does not pool or share credits across tenants. Each connected account tracks its own LeadIQ usage independently.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""leadiq"": {
""url"": ""https://mcp.scalekit.com/leadiq"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.leadiq]
url = ""https://mcp.scalekit.com/leadiq""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""leadiq"": {
""url"": ""https://mcp.scalekit.com/leadiq"",
""type"": ""http""
}
}
}