# PersistIQ MCP connector

The PersistIQ connector brings your leads, campaigns and do-not-contact domains into Claude, ChatGPT, Cursor and Microsoft Copilot through one governed endpoint, so each person works inside their own PersistIQ access with every call logged.

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

## Facts

| | |
| --- | --- |
| Application | PersistIQ |
| Category | CRM |
| AI tools | 13 |
| 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 PersistIQ is connected

- Add Dana Ruiz at Acme to the Q3 outbound campaign
- Which leads replied this week and who owns them?
- Add acme.com to the do-not-contact list

## Connect PersistIQ in Elaichi

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

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

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

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

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

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

## PersistIQ 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 PersistIQ 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 PersistIQ 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 PersistIQ through Elaichi

### Add a new lead to a campaign

Sales development. After a prospecting session, give the agent a name, email and company. It creates the lead in PersistIQ and enrolls it in the campaign you name.

### Catch a lead up after a call

Sales. Describe what changed, a new title, a new status, a note on timing, and the PersistIQ lead is updated without opening the record.

### Keep the do-not-contact list current

Compliance. When a company asks not to be emailed, add its domain to the PersistIQ do-not-contact list in one ask. Review the full list before a new campaign goes out.

### See which campaigns are running

Marketing. Pull every PersistIQ campaign with its owner and status so the team knows what is live before launching another sequence.

### Clean up lead fields and statuses

Revenue operations. List the lead fields and statuses PersistIQ uses, find leads with missing or outdated values, and fix them from a chat.

### Review the week's outreach activity

Sales management. Ask for recent PersistIQ events, grouped by rep and campaign, and get a short summary of what went out and who responded.

## Elaichi vs Zapier MCP vs Composio for PersistIQ

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

Two steps. In Elaichi, add the PersistIQ connector and paste in an API key from your PersistIQ settings; there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in as yourself and PersistIQ is ready in your next chat.

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

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

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

It can look up a PersistIQ lead, create one, update one, or add it to a campaign. It can list your campaigns, lead fields, lead statuses, users and recent events, and it can add a domain to the do-not-contact list. Short, concrete asks like "update Dana's status to replied" work better than long paragraphs.

### Does connecting PersistIQ give the AI access to every lead and campaign?

No. Every call runs as the person who signed in, so the agent sees only the PersistIQ leads, campaigns and events that person can already see. Elaichi can narrow that access further with roles and restrictions, and it never widens it beyond what PersistIQ itself allows.

### Can my team share one PersistIQ connection?

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

### Can I stop an agent from deleting or changing things in PersistIQ?

Yes. Restrictions in Elaichi apply per action, so you can allow reading PersistIQ leads while restricting deleting a campaign lead or editing the do-not-contact list, on a role or on one person. A restricted 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 PersistIQ connection when someone leaves?

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

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

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

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

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

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

## All 13 PersistIQ tools

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

- **Create a PersistIQ campaign lead** (Create). Add up to 100 leads to a campaign (more than 100 returns 400). Leads already in the campaign come back under errors ("Lead has already been taken"); the others are added. Required: campaign_id, and leads or lead_id.
- **Delete a PersistIQ campaign lead by ID** (Delete). Remove a lead from a campaign. The id is the lead ID (l_...). Required: campaign_id, id.
- **List all PersistIQ campaigns** (List). List campaigns with their send statistics, optionally only those a lead belongs to, owned by a user, or with a given name. Paged lists return up to 100 records per page (events: 500); the connector follows next_page while has_more is true.
- **List all PersistIQ dnc domains** (List). List Do Not Contact domains: emails to addresses at these domains are not sent without manual approval. Paged lists return up to 100 records per page (events: 500); the connector follows next_page while has_more is true.
- **Create a PersistIQ dnc domain** (Create). Add a Do Not Contact domain, so emails to addresses at that domain need manual approval. Required: name.
- **List all PersistIQ events** (List). List account activity events (lead created/updated, campaign changes, messages sent, replies, opens, clicks, bounces), optionally filtered by group, campaign, lead, user and time range. message_received means the lead replied. Paged lists return up to 100 records per page (events: 500); the connector follows next_page while has_more is true.
- **List all PersistIQ lead fields** (List). List all lead fields (built-in and custom) of the company. Their name is the key in a lead's data.
- **List all PersistIQ lead statuses** (List). List all lead statuses of the company (e.g. engaged, working, unresponsive).
- **List all PersistIQ leads** (List). List leads, 100 per page, optionally filtered by status name or update time. Paged lists return up to 100 records per page (events: 500); the connector follows next_page while has_more is true.
- **Get single PersistIQ lead by ID** (Get). Get a single lead by ID (e.g. l_1abc). Required: id.
- **Create a PersistIQ lead** (Create). Create up to 10 leads per call. A lead whose email already exists is skipped (dup = skip, the default) or updated (dup = update). The response lists the created leads and, with status = error, the leads that failed (e.g. blank email); the others are still created. Required: leads (each with email).
- **Update a PersistIQ lead by ID** (Update). Update a single lead: change its status (by name or status_id), mark it bounced or opted out, or set built-in and custom attributes in data. Required: id.
- **List all PersistIQ users** (List). List all non-archived users of the company. Use a user's id as creator_id on leads.create, and default_mailbox_id as mailbox_id on campaign_leads.create.
