# LeadIQ MCP connector The LeadIQ connector brings your saved contacts, companies, and prospect search to Claude, ChatGPT, Cursor, and the Elaichi Agent, so each rep searches and reviews prospects inside their own LeadIQ access, with every call logged. Source: https://elaichi.ai/connectors/leadiq/ ## Facts | | | | --- | --- | | Application | LeadIQ | | Category | Sales Intelligence | | AI tools | 4 | | Authentication | Connects with an API key | | Bring your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead | ## What you can ask once LeadIQ is connected - Find VP of Sales contacts at fintech companies in Boston - Which companies in LeadIQ have more than 500 employees? - List the contacts we saved at Acme Corp this month ## Connect LeadIQ in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick LeadIQ. 2. Optionally set Share with, then press Connect. 3. Paste a LeadIQ API key. One person generates a token in LeadIQ and pastes it once. Everyone else works through Share with, and never sees it. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which LeadIQ tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## LeadIQ MCP connector for Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## LeadIQ MCP connector for Claude Code Endpoint: https://api.elaichi.ai/mcp 1. In a terminal, run `claude mcp add` with the endpoint. 2. Start Claude Code and run `/mcp`. 3. Pick elaichi, then sign in and approve in the browser. ```bash claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp ``` Use `--scope project` instead to share it with the repository through `.mcp.json`. ## LeadIQ MCP connector for ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 3. Leave Authentication on OAuth, then tick the risk acknowledgement. 4. Press Create, then sign in and approve. Works on the web today. The plugin directory lives at chatgpt.com/plugins. ## LeadIQ MCP connector for Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect LeadIQ to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Every scope the client asks for starts ticked except "Delete data and remove access", which you tick yourself. Calling a LeadIQ tool needs "Run your connected tools". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Run your connected tools, which can also delete in connected apps and cannot be undone. ## What teams do with LeadIQ through Elaichi ### Build a call list before the morning block Sales Development. Ask for decision makers at target companies in a region or industry and get a list of LeadIQ contacts to work through, without clicking through search filters one at a time. ### Research an account before a first call Sales. Pull up the LeadIQ company record and every contact saved against it, so the rep knows who else is in the room before the meeting starts. ### Pull a target company list for a campaign Marketing. Search LeadIQ companies by size, industry, or location and hand the list to the campaign owner in the shape they asked for. ### Check which companies are already saved Revenue Operations. List the companies in LeadIQ and compare them against the territory plan, so nobody prospects an account that is already covered. ### Find new contacts at an existing customer Account Management. Search LeadIQ people at a customer company to spot new leaders or role changes that open a renewal or expansion conversation. ### Map the right people at a prospective partner Partnerships. Search LeadIQ for the partnerships, alliances, and channel contacts at a company before reaching out, instead of guessing from a website. ## Elaichi vs Zapier MCP vs Composio for LeadIQ All three can connect LeadIQ to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay. | What to check | Elaichi | Zapier MCP | Composio | | --- | --- | --- | --- | | Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. | | Control over LeadIQ tools | Allow or restrict single LeadIQ tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. | | Record of calls | One audit entry per LeadIQ call. | A History tab of tool calls. | A log of every tool call. | | Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. | | Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. | Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026. Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/). ## Frequently asked questions ### How do I connect LeadIQ to Claude? Connect LeadIQ in Elaichi first by pasting your LeadIQ API key, which you copy from your LeadIQ account settings. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude signs you in as yourself and LeadIQ is ready to ask. ### Does LeadIQ work with ChatGPT and Cursor as well as Claude? Yes. Once LeadIQ is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect LeadIQ once and every client picks it up. ### What can an AI agent actually do with my LeadIQ data? It can search LeadIQ for people by title, company, or location, search for companies by industry, size, or region, and list the contacts and companies already saved in your LeadIQ account. That means asking for a call list, researching an account before a meeting, or checking whether a company is already covered, all in plain language. Short, concrete asks such as "VPs of Sales at fintech companies in Boston" work better than long paragraphs. ### Does connecting LeadIQ give the AI everything in my account? No. Every call to LeadIQ runs as the person who signed in, so the agent sees only the contacts, companies, and searches that person can already see in LeadIQ. Elaichi can narrow that further with roles and restrictions, and it never widens it beyond what LeadIQ itself allows. ### Can my team share one LeadIQ connection? Yes. One person connects LeadIQ with their API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in as themselves through OAuth, so the audit log names the actual person who ran each LeadIQ search. ### Can I stop an agent from deleting or changing things in LeadIQ? This LeadIQ connector only searches and lists people, contacts, and companies, so there is nothing for an agent to delete or edit. Restrictions in Elaichi still apply per action, so you can turn off company search or contact listing for a team if you want. A restricted action is left out of the AI client's list entirely and cannot be called, whatever the prompt says. ### What happens to a LeadIQ connection when someone leaves? Offboarding a person in Elaichi ends their LeadIQ access at once, in Claude, ChatGPT, Cursor, and every other client. A shared LeadIQ connection keeps working for everyone else on the team. If you want LeadIQ gone entirely, disconnecting it once in Elaichi removes it from every client. ### Does the LeadIQ MCP connector work with Gemini, Codex, Claude Code or other MCP clients? Yes. LeadIQ is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs. ### Is Elaichi an alternative to Zapier MCP for LeadIQ? Yes. Both let Claude, ChatGPT or Cursor use LeadIQ. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every LeadIQ call. ### How is Elaichi different from Composio for LeadIQ? Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to LeadIQ: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call. ## All 4 LeadIQ tools Every tool below is callable through https://api.elaichi.ai/mcp once LeadIQ is connected, subject to the toolbox it is in and the restrictions on the caller. - **LeadIQ people search** (Search). Look up one person by email, LinkedIn URL, or a name together with their company (name, or first_name and last_name, with company.name or company.domain), and return their profile. Always includes a work email when LeadIQ has one. Personal emails and phone numbers (work and personal) are included only when requested via with_personal_emails/with_phones, to control cost. Returns at most one result. - **LeadIQ companies search** (Search). Look up one company by domain, LinkedIn URL, or name (an identity lookup, not a filtered search). Returns the first matching result, or zero results on a miss. For filtered company search use companies.list instead. - **List all LeadIQ companies** (List). Search companies by domain, name, employee-count range or country (GroupedAdvancedSearch). Returns only the company half of each grouped result; the people in each group are not read or billed by this method. Offset-paginated (skip/limit), capped at 10,000 combined per LeadIQ's docs. - **List all LeadIQ contacts** (List). Search people by title, seniority, company domain or location (FlatAdvancedSearch). Never selects email or phone fields, unlike the existing persons.list method -- use person.enrich for contact info. Offset-paginated (skip/limit), capped at 10,000 combined per LeadIQ's docs.