# MoltSets MCP connector Connect MoltSets to Elaichi and Claude, ChatGPT, Cursor, and the Elaichi Agent can look up people, companies, LinkedIn profiles, business emails, and mobile numbers from your MoltSets account, with every lookup signed in as you and logged. Source: https://elaichi.ai/connectors/moltsets/ ## Facts | | | | --- | --- | | Application | MoltSets | | Category | Sales Intelligence | | AI tools | 20 | | 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 MoltSets is connected - Find the VP of Sales at Acme and her business email - Which company is behind the IP address 203.0.113.42? - Pull LinkedIn profiles for heads of marketing at fintech startups in Austin ## Connect MoltSets in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick MoltSets. 2. Optionally set Share with, then press Connect. 3. Paste a MoltSets API key. One person generates a token in MoltSets 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 MoltSets tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## MoltSets 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. ## MoltSets 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`. ## MoltSets 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. ## MoltSets 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 MoltSets 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 MoltSets 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 MoltSets through Elaichi ### Find the right person before you call Sales. Search MoltSets for the decision maker at a target company, then pull their LinkedIn profile and business email in one ask. ### Turn a LinkedIn URL into a contact Sales Development. Paste a prospect's LinkedIn profile and get their best business email and mobile number from MoltSets, ready for outreach. ### Build an ad audience from a contact list Marketing. Look up the mobile advertising IDs and hashed emails MoltSets holds for a list of contacts, so a matched audience is ready for the ad platform. ### Enrich the record after a form fill Revenue Operations. Give the AI an email address from an inbound form and MoltSets returns the person's business profile, title and company. ### See which company is visiting the site Growth. Hand over an IP address from web analytics and MoltSets names the company behind it, so anonymous traffic becomes an account to pursue. ### Check MoltSets usage before the invoice Finance. Ask how many MoltSets lookups the team has used this month and what the billing shows, without logging into the admin console. ## Elaichi vs Zapier MCP vs Composio for MoltSets All three can connect MoltSets 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 MoltSets tools | Allow or restrict single MoltSets 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 MoltSets 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 MoltSets to Claude? Connect MoltSets in Elaichi by pasting the API key from your MoltSets account when asked. 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 https://api.elaichi.ai/mcp. Claude signs you in through Elaichi and MoltSets people, company and email lookups are available in your chat. ### Does MoltSets work with ChatGPT and Cursor as well as Claude? Yes. Once MoltSets 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 MoltSets once and every client you use picks it up. ### What can an AI agent actually do with my MoltSets data? It can search MoltSets for people and companies, pull a LinkedIn profile from an email address, and find the business email, personal email or mobile number behind a LinkedIn profile. It can also look up the company behind an IP address, fetch advertising IDs and hashed emails for an ad audience, and show your MoltSets account, billing and usage. Short concrete asks work best, such as a name and a company, or a single LinkedIn URL. ### Does connecting MoltSets give the AI everything in my account? The AI can only run the MoltSets lookups that the connected MoltSets account is entitled to, and each person signs in to Elaichi as themselves. Elaichi can narrow that further, for example keeping mobile phone lookups or billing away from a team, but it can never widen what MoltSets allows. ### Can my team share one MoltSets connection? Yes. One person connects MoltSets in Elaichi and shares the connection with a team, and nobody else ever handles the MoltSets API key. Each teammate still signs in to Elaichi as themselves, so every MoltSets lookup in the audit log carries the name of the person who ran it. ### Can I stop an agent from running certain MoltSets lookups, such as mobile phones or billing? Yes. MoltSets lookups through Elaichi only search and read, nothing is deleted or changed, but you can still restrict individual actions such as mobile phone lookups, personal email lookups or billing. A restricted MoltSets action is left out of the AI client's tool list entirely and cannot be called, whatever the prompt says. ### What happens to a MoltSets connection when someone leaves? Offboarding a person in Elaichi ends their access to MoltSets at once, in every client they used. A MoltSets connection shared with a team keeps working for everyone else. If you want MoltSets gone completely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client. ### Does the MoltSets MCP connector work with Gemini, Codex, Claude Code or other MCP clients? Yes. MoltSets 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 MoltSets? Yes. Both let Claude, ChatGPT or Cursor use MoltSets. 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 MoltSets call. ### How is Elaichi different from Composio for MoltSets? 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 MoltSets: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call. ## All 20 MoltSets tools Every tool below is callable through https://api.elaichi.ai/mcp once MoltSets is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all MoltSets search people** (List). Search the MoltSets people database by name, title, employer, seniority, department, industry, company size or location. Returns ranked profiles with business email and company. Needs at least one positive filter. Max 25 per page. 1 search record per row returned. - **List all MoltSets search companies** (List). Search the MoltSets company database by name, domain, industry, headcount, revenue, NAICS code or location. Returns ranked company profiles. Needs at least one positive filter. Max 25 per page. 1 search record per row returned. - **MoltSets linkedin profiles search** (Search). Find LinkedIn profiles that match a person's name and company domain. Set `count_only` to true to get only the match count, free, before spending a token. Costs 1 token when data is found; a `not_found` miss is free. - **MoltSets linkedin profiles lookup by email** (Action). Find the best-matching LinkedIn profile URL for an email address. Costs 1 token when data is found; a `not_found` miss is free. - **MoltSets business emails search** (Search). Find a person's verified work email from their name and company domain, with the matched LinkedIn URL and a send-safety `risk_score`. Costs 1 token when data is found; a `not_found` miss is free. - **MoltSets business profiles search** (Search). Find a person's business profile (job title, employer, firmographics) from their name and company domain. Costs 1 token when data is found; a `not_found` miss is free. - **MoltSets business profiles lookup by email** (Action). Get the business profile behind an email address: name, title, seniority, employer, LinkedIn URL, firmographics and other emails on file. Costs 1 token when data is found; a `not_found` miss is free. - **MoltSets business profiles lookup by linkedin** (Action). Get the most complete profile for a LinkedIn URL: name, title, location, employer firmographics, and business and personal emails with risk scores. Costs 1 token when data is found; a `not_found` miss is free. - **MoltSets emails lookup best by linkedin** (Action). Get the best email for a LinkedIn profile: a business email when one exists, else a personal one (`type` says which). Pass `linkedin_url`, or `linkedin_urls` for up to 100 profiles. Costs 1 token per profile found. - **MoltSets emails lookup business by linkedin** (Action). Get the verified work email for a LinkedIn profile (business addresses only). Pass `linkedin_url`, or `linkedin_urls` for up to 100 profiles. Costs 1 token per profile found. - **MoltSets emails lookup personal usa by linkedin** (Action). Get a verified personal email (Gmail, iCloud and similar) for a LinkedIn profile. US records only, and not on every plan: check `personal_email_available` in the account details first (otherwise 403 `plan_restricted`). Pass `linkedin_url`, or `linkedin_urls` for up to 100 profiles. Costs 1 token per profile found. - **MoltSets emails lookup best personal usa by linkedin** (Action). Get the single highest-confidence personal email for a LinkedIn profile, with its last validation date. US records only, and not on every plan: check `personal_email_available` in the account details first (otherwise 403 `plan_restricted`). Pass `linkedin_url`, or `linkedin_urls` for up to 100 profiles. Costs 1 token per profile found. - **MoltSets mobile phones lookup by linkedin** (Action). Get a carrier-verified mobile number for a LinkedIn profile (mobiles only; not screened against Do Not Call lists). Pass `linkedin_url`, or `linkedin_urls` for up to 100 profiles. Spends 1 phone token per number returned, from a separate paid phone-token subscription; misses are free. - **MoltSets ad audiences lookup maid by email** (Action). Get a mobile advertising ID (AAID or IDFA) for an email address, for mobile ad retargeting. Not available on the $397 and $997 plans (403 `plan_restricted`). Costs 1 token when data is found; a `not_found` miss is free. - **MoltSets ad audiences lookup sha 256 by business email** (Action). Get the SHA256 hash of the personal email linked to a business email, for ad-platform customer match. Not available on the $397 and $997 plans (403 `plan_restricted`). Costs 1 token when data is found; a `not_found` miss is free. - **MoltSets ad audiences lookup hashes by linkedin** (Action). Get SHA256 and MD5 hashes of the business and personal emails for a LinkedIn profile, for ad-platform customer match. Hashes with no data are left out. Not available on the $397 and $997 plans (403 `plan_restricted`). Costs 1 token when data is found; a `not_found` miss is free. - **MoltSets companies lookup by IP** (Action). Identify the company domain(s) behind an IPv4 address, for B2B website-visitor identification. Consumer ISP addresses usually return nothing. Costs 1 token when data is found; a `not_found` miss is free. - **List all MoltSets account** (List). Get your MoltSets account: plan, status, token and phone-token balances, live fair-use headroom, and whether personal-email lookups are on your plan. Free. - **List all MoltSets billing** (List). Get your MoltSets billing details: plan, subscription status, token balance, billing period dates, and the token cost of each tool. Free. - **List all MoltSets usage** (List). Get day-by-day MoltSets usage (calls, tokens, hits, misses, failures) with totals for today, the past week, the past month or the billing cycle. Free.