# Captain Data MCP connector The Captain Data connector brings your people searches, company enrichments, employee lists and quota usage into Claude, ChatGPT, Cursor and the Elaichi Agent through one governed endpoint, where each person sees only what their own Captain Data access allows. Source: https://elaichi.ai/connectors/captaindata/ ## Facts | | | | --- | --- | | Application | Captain Data | | Category | Sales Intelligence | | AI tools | 12 | | 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 Captain Data is connected - Summarize this week's people finds and which ones came back enriched. - List the employees found at Acme and group them by department. - How much of our Captain Data quota is left this month? ## Connect Captain Data in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Captain Data. 2. Optionally set Share with, then press Connect. 3. Paste a Captain Data API key. One person generates a token in Captain Data 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 Captain Data tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Captain Data 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. ## Captain Data 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. ## Captain Data 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 Captain Data 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 Only Read is granted by default, which is not enough to call a Captain Data tool. 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. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Captain Data through Elaichi ### Brief yourself on a prospect before the call Sales. Pull up the enriched profile of a buyer, their work history, skills and certifications, and get a short brief without opening Captain Data. ### Review this week's people finds in one place Sales development. Ask which people your searches surfaced this week, which ones came back enriched, and which lists are still thin. ### Check company enrichments for a campaign segment Marketing. Look over the companies you enriched for a segment, compare size and industry, and spot the ones that do not fit before the campaign goes out. ### Scan candidate skills and certifications quickly Recruiting. Read through the skills, certifications and past roles Captain Data found for a shortlist and get a summary you can share with the hiring manager. ### Watch quota and workspace consumption Revenue operations. Ask how much of your Captain Data quota is left, which workspaces are using the most, and whether you will run out before month end. ### Map the people at a target company Partnerships. List the employees Captain Data found at a company you want to partner with, grouped by department and seniority, so you know who to approach. ## Elaichi vs Zapier MCP vs Composio for Captain Data All three can connect Captain Data 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 Captain Data tools | Allow or restrict single Captain Data 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 Captain Data 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 Captain Data to Claude? In Elaichi, choose Captain Data and paste the API key from your Captain Data account, which takes a minute and needs no client ID or secret. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Captain Data is ready in Claude. ### Does Captain Data work with ChatGPT and Cursor as well as Claude? Yes. Captain Data connects once in Elaichi and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You do not set it up again for each one. ### What can an AI agent actually do with my Captain Data data? An agent can read the results of your Captain Data searches and enrichments: the people and companies found, their work experience, skills and certifications, the employees listed at a company, plus your quota and workspace consumption. You can ask for a brief on a prospect, a summary of this week's finds, or how much quota is left. Short, concrete asks such as "list the companies enriched this month" work better than long paragraphs. ### Does connecting Captain Data give the AI everything in my workspace? No. Every request to Captain Data runs as the person who signed in, so an agent sees only the searches, enrichments and workspaces that person can already see. Elaichi can narrow that further by team or by action, and it can never widen it. ### Can my team share one Captain Data connection? Yes. One person connects Captain Data 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 in to Elaichi as themselves, so the audit log names the person behind every request. ### Can I stop an agent from deleting or changing things in Captain Data? This Captain Data connector only reads results, so an agent cannot edit or delete searches or enrichments through it. On top of that, Elaichi restrictions work per action, and a restricted action is never shown to Claude, ChatGPT or Cursor, so no prompt can reach it. ### What happens to a Captain Data connection when someone leaves? Offboarding that person in Elaichi ends their Captain Data access in every client at once. A connection they shared keeps working for everyone else on the team. If you want Captain Data gone entirely, disconnecting it once in Elaichi removes it from every client. ### Does the Captain Data MCP connector work with Gemini, Codex, Claude Code or other MCP clients? Yes. Captain Data 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 Captain Data? Yes. Both let Claude, ChatGPT or Cursor use Captain Data. 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 Captain Data call. ### How is Elaichi different from Composio for Captain Data? 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 Captain Data: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call. ## All 12 Captain Data tools Every tool below is callable through https://api.elaichi.ai/mcp once Captain Data is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Captain Data people finds** (List). Find a person in Captain Data by their full name. Returns the matched person's uid, the Captain Data person UID accepted as people_uid by the other people endpoints. Required: full_name. - **List all Captain Data search peoples** (List). Search people in captaindata using a LinkedIn Sales Navigator people search query. Returns an array of matching people records, each identified by its Captain Data uid, with the remaining profile fields defined by the upstream search output schema. Required: query. Page size is fixed at 25. - **List all Captain Data people enriches** (List). Get enriched people profile data from Captain Data. Returns the enriched profile data as a single JSON object (the source docs do not enumerate its fields). Required: li_profile_url — a LinkedIn profile URL starting with 'https://www.linkedin.com/in/', '/pub/', '/sales/people/' or '/sales/lead/'. - **List all Captain Data people experiences** (List). List a person's work experiences in Captain Data. Returns an array of experience records whose fields are defined by Captain Data's upstream experience output schema. Provide either li_profile_url (a LinkedIn `/in/`, `/pub/`, or Sales Navigator URL) or people_uid (the `uid` from Find, Search, or Enrich People); one of the two is required, and people_uid is preferred when you already have it. - **List all Captain Data people skills** (List). List a person's skills in Captain Data. Returns an array of the person's skill entries. Required: either li_profile_url (LinkedIn `/in/`, `/pub/`, or Sales Navigator URL) or people_uid (Captain Data uid from Find, Search, or Enrich People). - **List all Captain Data people certifications** (List). List a person's licenses & certifications in Captain Data. Returns an array of certification records, each with its id. Identify the person with either li_profile_url or people_uid (people_uid preferred when a uid is already available). Page size is fixed at 20. - **List all Captain Data search companies** (List). Search companies in Captain Data using a Sales Navigator Company search compliant query. Returns a list of company records, each with its id and content-specific company attributes. Required: query. Fixed page size of 25. - **List all Captain Data companies enriches** (List). Enrich a company in Captain Data from its LinkedIn company URL. Returns the enriched company record: id plus an attributes object holding the enrichment fields defined by the upstream companies/enrich output schema. Required: li_company_url — a LinkedIn URL on a company, sales/company, showcase, or school path. - **List all Captain Data companies finds** (List). Find a company in Captaindata by company name or website domain. Returns the matched company record with its id plus its company attribute fields (the full field set is defined upstream). Provide either company_name or domain — not both; domain is preferred when available. - **List all Captain Data workspaces consumptions** (List). Get the current workspace's credit consumption stats in Captain Data. Returns: credits_left, credits_used, credits_max, current_month_start, current_month_end, consumptions. - **List all Captain Data quotas** (List). Get the current workspace quota and billing information in Captain Data. Returns: uid, name, credits_left, credits_max, credits_used, plan_name, current_month_start, current_month_end. - **List all Captain Data company employees** (List). List the employees of a company in Captain Data by its company uid. Returns employee records with an id and Captain Data-defined employee attributes. Required: company_uid. Page size is fixed at 25.