API KEY
CRM & SALES
Connect to Lusha MCP. Search and enrich B2B contacts and companies, find lookalikes, run prospecting searches, and access intent and activity signals from...
from langchain_mcp_adapters.client import MultiServerMCPClient
from scalekit import ScalekitClient
client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="lushamcp")
mcp = MultiServerMCPClient({
"lushamcp": {
"url": "https://mcp.scalekit.com/lushamcp",
"headers": {"Authorization": "Bearer " + token}
}
})
tools = await mcp.get_tools()import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";
const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "lushamcp" });
const openai = new OpenAI();
// Connect to MCP at https://mcp.scalekit.com/lushamcp
// Pass: Authorization: Bearer + tokenimport Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";
const client = new ScalekitClient({ envUrl, clientId, clientSecret });
const token = await client.agent.getToken({ userId: "user_id", connector: "lushamcp" });
const anthropic = new Anthropic();
// Connect to MCP at https://mcp.scalekit.com/lushamcp
// Pass: Authorization: Bearer + tokenfrom google.adk.agents import LlmAgent
from scalekit import ScalekitClient
client = ScalekitClient(env_url=ENV_URL, client_id=CLIENT_ID, client_secret=SECRET)
token = client.agent.get_token(user_id="user_id", connector="lushamcp")
# Connect to MCP at https://mcp.scalekit.com/lushamcp
# Pass: Authorization: Bearer + token
.svg)
// shared token
audit → bot_service_account
// scalekit
audit → user_abc ✓
Does the agent access Lusha 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 Lusha 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 Lusha?
Yes. Pass a tool name filter to listScopedTools so the marketing agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Lusha.
What happens when a user revokes Lusha 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.
Whose Lusha credits do contact enrichments spend?
The authorizing user's. Contact and company searches, lookalikes, and intent signals draw from that user's Lusha quota, so prospecting spend maps to the rep who triggered it.
