# Unipile MCP connector

Connect Unipile to Elaichi and Claude, ChatGPT, Cursor and any MCP client can browse Unipile's API endpoints, read their details, and run requests against your messaging accounts as you, with every call logged.

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

## Facts

| | |
| --- | --- |
| Application | Unipile |
| Category | Application Development |
| AI tools | 5 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| Native MCP | Yes. Unipile builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | www.unipile.com/contact-us |
| 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 |

## Why connect Unipile's MCP server through Elaichi

Unipile builds and runs this MCP server. Elaichi sits in front of it, so Unipile's tools follow the same sign-in, access rules and audit log as every other connector your organization uses. Calls an AI client makes to Unipile's server directly, outside Elaichi, get none of this.

- **One address for every AI client.** Claude, ChatGPT and Cursor reach Unipile's tools at https://api.elaichi.ai/mcp, the same address as every other connected app. Nobody adds Unipile's server to each client one by one.
- **Each person signs in as themselves.** Each person signs in to Elaichi as themselves. Members connect with their own Unipile sign-in, and a connection someone shares runs on its owner's account. The credential stays in Elaichi's separate credential service, and the AI client holds only its Elaichi sign-in.
- **Rules checked before a call leaves.** Restrictions on a role or a person, for the whole connector or a single tool, are checked before a call reaches Unipile's server. By default, a tool Unipile does not mark read-only or non-destructive counts as destructive, and over MCP it needs the "Delete data and remove access" consent.
- **One audit log for every app.** Each call that runs is recorded with the person, the tool, the connection and the AI client that made it, in the same audit log as every other app.
- **Tool issues go to Unipile.** Unipile builds and runs these tools, and Elaichi staff do not curate them, so a report about how a tool behaves goes to the Unipile team. Contact: [www.unipile.com/contact-us](https://www.unipile.com/contact-us/).

More: [why run a vendor's MCP server through Elaichi](https://elaichi.ai/blog/vendor-mcp-servers-through-elaichi/)

## What you can ask once Unipile is connected

- Find the Unipile endpoint for listing chats on a LinkedIn account.
- Pull the last ten messages from our sales inbox in Unipile.
- Show me what fields the Unipile send message endpoint needs.

## Connect Unipile in Elaichi

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

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

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

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

## Unipile 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 Unipile 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 Unipile 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 Delete, which reaches into connected apps and cannot be undone.

## What teams do with Unipile through Elaichi

### Find the right Unipile endpoint fast

Engineering. Ask which Unipile endpoint lists chats for a LinkedIn account and get the endpoint, its parameters and an example back in plain language, without opening the reference docs.

### Pull up a conversation before a call

Sales. Ask for the last messages exchanged with a prospect across the LinkedIn and email accounts connected in Unipile, so the rep walks into the call already caught up.

### Check replies across every inbox

Recruiting. Ask which candidates answered this week across the messaging accounts in Unipile and get one list back instead of checking each account by hand.

### Reproduce a customer's failing request

Support. Look up the endpoint a customer is calling, confirm the required fields, and run the same request through Unipile to see what actually comes back.

### Map what Unipile can do before building

Product. Search the Unipile endpoint catalog by keyword, read what each one accepts and returns, and decide what the next feature can rely on.

### Confirm connected accounts and settings

Operations. Ask which messaging accounts are connected in Unipile and what server variables are set for your workspace, then catch anything that has drifted.

## Elaichi vs Zapier MCP vs Composio for Unipile

All three can connect Unipile 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 Unipile tools | Allow or restrict single Unipile 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 Unipile 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 Unipile to Claude?

Two steps. In Elaichi, add Unipile and paste your Unipile API key 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. Sign in to Elaichi when prompted and Unipile is available in Claude.

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

Yes. Once Unipile is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. You connect Unipile once and every client picks it up.

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

An agent can list and search the endpoints in the Unipile API, read what each one needs and returns, check your server variables, and run requests against your connected messaging accounts, for example fetching recent chats or messages. Short concrete asks like "list the chats on our LinkedIn account" work better than long sentences.

### Does connecting Unipile give the AI everything in my messaging accounts?

No. Every request to Unipile runs under the API key and person who signed in, so the agent can only reach the accounts and endpoints that key already covers. Elaichi can narrow that further by restricting which actions are allowed, and it never widens access beyond what Unipile itself permits.

### Can my team share one Unipile connection?

Yes. One person connects Unipile in Elaichi and shares the connection with a team, and nobody else ever handles the Unipile API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every request to Unipile.

### Can I stop an agent from sending messages or changing things in Unipile?

Yes. Restrictions in Elaichi work per action, so you can allow browsing endpoints and reading details while blocking the ability to run requests against Unipile. A restricted action is left out of the AI client's tool list entirely and cannot be called, whatever the prompt says.

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

Offboarding that person in Elaichi ends their access to Unipile at once, across Claude, ChatGPT, Cursor and every other client. A shared Unipile connection keeps working for everyone else on the team. If you want it gone entirely, disconnecting Unipile once in Elaichi removes it from every client.

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

Yes. Unipile 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 Unipile?

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

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

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

## All 5 Unipile tools

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

- **List API Endpoints** (List). Lists all API paths and their HTTP methods with summaries, organized by path. Results can be passed directly into 'get-endpoint'.
- **Get Endpoint Details** (Get). Gets detailed information about a specific API endpoint, including security schemes and servers
- **Search API Endpoints** (Search). Performs a deep search through paths, operations, and parameters to discover relevant API endpoints. Use this tool to find specific API capabilities, required parameters, or data models based on search keywords. Results can be passed directly into 'get-endpoint'.
- **Execute API Request** (Execute). Executes an API request with a given HAR request object.
- **Get Server Variables** (Get). Gets the server variables for each server within a specific OpenAPI spec.