Skip to main content
Yes. The Lusha MCP server is live at https://mcp.lusha.com, with both OAuth-based connections (Claude, ChatGPT, Codex) and API-key connections (VS Code, Cursor, Gemini CLI, n8n, and other MCP clients). See MCP setup for client-specific steps.
The Model Context Protocol (MCP) is an open standard that lets AI assistants and agents call external tools in a structured, consistent way. It means you can ask an MCP-compatible client to “enrich this contact” or “find decision makers at Acme Corp” and have it call the Lusha API automatically - no manual API calls required.
Lusha documents setup for Claude, ChatGPT, and Codex (via OAuth), and VS Code (GitHub Copilot), Cursor, Gemini CLI, and n8n (via API key). Any other MCP-compatible client can connect using the API-key method against https://mcp.lusha.com. See the MCP setup guide for exact steps.
No - MCP uses the same API key and credit pool as the REST API. Any plan that includes API access can use the MCP server. One exception: the recommendations tools are only available over an OAuth connection (Claude, ChatGPT, Codex) - API-key sessions get a 403 on those specific tools.
No. MCP tool calls translate into the same underlying Lusha API requests, and credits are deducted the same way - generally per successful, matched result. Filter-lookup tools and a few read-only tools (like checking your account usage) don’t consume credits. See available tools for which tools do and don’t charge credits.
Not confirmed yet - check with Product or DevRel before publishing an answer here.