# ContactOut MCP connector

The ContactOut connector brings people search, email and phone enrichment, email verification and company lookups into Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, with every lookup run as the signed-in person and logged.

Source: https://elaichi.ai/connectors/contactout/

## Facts

| | |
| --- | --- |
| Application | ContactOut |
| Category | Sales Intelligence |
| AI tools | 23 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, 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 ContactOut is connected

- Find the work email for this LinkedIn profile
- Verify every email on the Q3 webinar list
- List VPs of engineering at fintech companies in Austin

## Connect ContactOut in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick ContactOut.
2. Optionally set Share with, then press Connect.
3. Paste a ContactOut API key. One person generates a token in ContactOut 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 ContactOut tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## ContactOut 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.

## ContactOut 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`.

## ContactOut 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. The plugin directory lives at chatgpt.com/plugins.

## ContactOut 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.

## ContactOut MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect ContactOut 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 things", which you tick yourself. Calling a ContactOut tool needs "Use your connected apps". 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 Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with ContactOut through Elaichi

### Find a verified email before first outreach

Sales. Give the agent a name and company, or a LinkedIn profile, and it returns the work email from ContactOut, checks that it is deliverable, and adds a phone number where one exists.

### Reach a candidate without waiting on InMail

Recruiting. Paste a LinkedIn profile and get the candidate's personal email and phone number from ContactOut, so the first message lands in an inbox they actually read.

### Clean a list before the campaign goes out

Marketing. Hand over a spreadsheet of contacts and the agent verifies every email in bulk through ContactOut, flagging the ones that will bounce before they hurt your sender reputation.

### Build a target list of decision makers

Business development. Ask for VPs of operations at logistics companies in Texas with 200 to 1,000 employees and get back named people with their titles, companies and contact details.

### Enrich inbound leads the moment they arrive

Revenue operations. Give the agent a form submission with only an email and it fills in the person's title, company, LinkedIn profile and company size from ContactOut, ready for the CRM. It can also report how much of the ContactOut allowance the team has used this month.

### Check a contact is still at the company

Account management. Before a renewal call, ask the agent to confirm your champion's current title and company and find their LinkedIn profile, so you are not pitching someone who left last quarter.

## Elaichi vs Zapier MCP vs Composio for ContactOut

All three can connect ContactOut 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 ContactOut tools | Allow or restrict single ContactOut 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 ContactOut 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 | Free for one person; $15 per user per month on Gold. | 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 ContactOut to Claude?

Connect ContactOut in Elaichi by pasting the API key from your ContactOut account, then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register in ContactOut and no client ID or secret to generate. Once added, Claude signs you into Elaichi and ContactOut lookups are available in your next conversation.

### Does ContactOut work with ChatGPT and Cursor as well as Claude?

Yes. ContactOut is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, is added to Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. There is nothing to set up separately for each client.

### What can an AI agent actually do with my ContactOut data?

It can find a person's work email, personal email and phone number from a name and company or a LinkedIn profile, verify whether an email address is deliverable, and search ContactOut for people by title, company, location or seniority, including decision makers at a target account. It can also look up company details, run bulk enrichment and verification jobs on a whole list, list your ContactOut campaigns and report how much of your allowance has been used. Short, specific asks such as find the work email for this LinkedIn profile work better than long paragraphs.

### Does connecting ContactOut give the AI my whole ContactOut account and credits?

The agent can only do what the ContactOut account whose API key was connected can do, and it draws on that account's ContactOut credits and limits. Elaichi can narrow that further by restricting individual actions, such as bulk enrichment, for a role or a person, and it can never grant anything the ContactOut account does not already have. Every lookup is recorded against the person who asked for it.

### Can my team share one ContactOut connection?

Yes. One person connects ContactOut with the API key and shares the connection with a team in Elaichi, and nobody else ever sees or handles the key. Each teammate still signs into Elaichi as themselves, so the audit log shows who searched for which person or verified which list, even though the ContactOut account is shared.

### Can I stop an agent from running bulk enrichment or spending ContactOut credits?

Yes. Restrictions in Elaichi apply per action, so you can restrict bulk contact enrichment or decision maker search in ContactOut for a role or for one person while leaving single lookups open. A restricted ContactOut action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to a ContactOut connection when someone leaves?

Offboarding the person in Elaichi ends their access to ContactOut through every client at once, with no need to rotate the ContactOut API key. A ContactOut connection they shared with a team keeps working for everyone else. Disconnecting ContactOut once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.

### Does the ContactOut MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. ContactOut 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, Microsoft Copilot, 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 ContactOut?

Yes. Both let Claude, ChatGPT or Cursor use ContactOut. 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 ContactOut call.

### How is Elaichi different from Composio for ContactOut?

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 ContactOut: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 23 ContactOut tools

Every tool below is callable through https://api.elaichi.ai/mcp once ContactOut is connected, subject to the toolbox it is in and the restrictions on the caller.

- **ContactOut people enrich** (Action). Enrich one person in ContactOut from linkedin_url, email or phone, or from a name plus company, company_domain, location or education. Contact data comes back only for the types listed in include. Returns status_code and profile. Costs 1 search credit per profile found, plus 1 email or phone credit when that data is found.
- **ContactOut people enrich by linkedin URL** (Action). Get the full ContactOut profile for one LinkedIn profile URL, with emails and phones when found; profile_only=true skips contact data. Returns status_code and profile (an empty array when nothing matched). Costs 1 email credit and 1 phone credit when found, or 1 search credit when profile_only=true or no contact data exists.
- **ContactOut people enrich by email** (Action). Get the ContactOut profile for one email address; personal emails match best. Set include=work_email to also get a work email checked in real time (workEmailStatus Verified or Unverified) (slower). Returns status_code and profile with camelCase keys. Costs 1 email credit if an email is found and 1 phone credit if a phone is found.
- **ContactOut people find linkedin URL** (Action). Get the LinkedIn profile URL for an email address (ContactOut Email to LinkedIn API). Returns status_code and profile with email and linkedin. Costs 1 email credit if a profile is found.
- **ContactOut people search** (Search). Search ContactOut people profiles by title, company, location, skills, education and more. Page with page and page_size (1-25, default 25) in the body. Returns status_code, metadata and profiles keyed by LinkedIn URL. Costs 1 search credit per profile returned, plus email/phone credits when reveal_info=true. Limited to 60 requests per minute.
- **ContactOut people count** (Action). Count ContactOut profiles matching the People Search filters (page, data_types and reveal_info are not accepted). Returns status_code, total_results, estimated_personal_emails, estimated_work_emails and estimated_phones. Does not consume credits. Available to paid users only.
- **ContactOut people search decision makers** (Search). Get decision makers at a company in ContactOut. Send at least one of linkedin_url, domain or name; pass page for later pages (25 per page). Returns status_code, metadata and profiles keyed by LinkedIn URL. Costs 1 search credit per profile returned, plus email/phone credits when reveal_info=true.
- **ContactOut contacts enrich** (Action). Get emails, and phones with include_phone=true, for one LinkedIn profile in ContactOut. email_type picks personal, work, personal,work or none. Returns status_code and profile with url, email, work_email, work_email_status, personal_email, phone and github. Costs 1 email credit if an email is found and 1 phone credit if a phone is found.
- **ContactOut contacts bulk enrich** (Action). Get contact details for up to 100 LinkedIn profiles in one synchronous ContactOut call (V1 bulk). Returns status_code and profiles keyed by the requested URL: an array of emails, or an object with emails and phones when include_phone=true. Costs 1 email credit per profile with an email and 1 phone credit per profile with a phone.
- **ContactOut contacts check personal email** (Action). Check whether ContactOut has a personal email for a LinkedIn profile. Returns status_code and profile.email (true when present). Does not consume credits. Paid users only.
- **ContactOut contacts check work email** (Action). Check whether ContactOut has a work email for a LinkedIn profile. Returns status_code and profile with email (true when present) and email_status (Verified, Unverified or null). Does not consume credits. Paid users only.
- **ContactOut contacts check phone** (Action). Check whether ContactOut has a phone number for a LinkedIn profile. Returns status_code and profile.phone (true when present). Does not consume credits. Paid users only.
- **Create a ContactOut contact enrichment job** (Create). Start an asynchronous ContactOut contact lookup (V2 bulk) for up to 1000 LinkedIn profile URLs. Returns status (e.g. QUEUED) and job_id; fetch results with get using the job_id, or pass callback_url to have ContactOut POST them when done. Costs 1 email credit per profile with an email and 1 phone credit per profile with a phone.
- **Get single ContactOut contact enrichment job by ID** (Get). Get a ContactOut V2 bulk contact lookup job by its job_id. Returns uuid, status and result, where result is keyed by LinkedIn URL with emails, personal_emails, work_emails and phones.
- **ContactOut hashed emails bulk lookup** (Action). Get SHA-256 hashed personal emails for 5 to 100 LinkedIn profile URLs in ContactOut. Returns status_code, matches.emails (hashes), matches_found, unmatched and unmatched_count. Work emails are not included. Costs 1 email credit per profile that returns a hash.
- **ContactOut email verifications verify** (Verify). Verify the deliverability of one email address with ContactOut. Returns status_code and data.status: valid, invalid, accept_all, disposable or unknown. Costs 1 verifier credit when the result is valid, invalid or accept_all.
- **Create a ContactOut email verification job** (Create). Start an asynchronous ContactOut bulk verification of up to 100 email addresses. Returns status (e.g. QUEUED) and job_id; fetch results with get, or pass callback_url to receive them by POST. Costs 1 verifier credit per email whose result is valid, invalid or accept_all.
- **Get single ContactOut email verification job by ID** (Get). Get a ContactOut bulk email verification job by its job_id. Returns uuid, status (DONE when complete) and result, a map of email to valid, invalid, accept_all, disposable or unknown.
- **List all ContactOut campaigns** (List). List ContactOut email campaigns. Returns id, name, status, created_at and updated_at for each campaign. The Campaigns API must be enabled for the API token; otherwise ContactOut returns 403.
- **Get single ContactOut campaign by ID** (Get). Get one ContactOut campaign by id, with its sequence steps. Set include_stats=true to add stats (sends, opens, replies, bounces, open_rate, reply_rate). Returns id, name, status, created_at, updated_at, steps and stats. Needs the Campaigns API enabled for the token.
- **List all ContactOut usage stats** (List). Get ContactOut API usage for a month. Pass period as YYYY-MM (default current month). Returns status_code, period and usage with email, phone and search counts and quotas; postpaid keys also carry remaining and over_quota values. Unpaginated: the list returns this one usage object as a single record; limit and next_cursor do nothing.
- **ContactOut companies enrich** (Action). Get ContactOut company details for up to 30 domains. Returns status_code and companies keyed by domain; a domain with no match maps to an empty object. Costs 1 search credit per company found.
- **ContactOut companies search** (Search). Search ContactOut companies by name, domain, size, location, industry, technologies, revenue and founding year. Pass page in the body for later pages (25 per page). Returns status_code, metadata and a companies array. Costs 1 search credit per company returned.
