Anteriad MCP connector

Connect Anteriad in Elaichi first by pasting in your Anteriad API key, which is the only sign-in step Anteriad needs. 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 in https://api.elaichi.ai/mcp. Sign in as yourself and Anteriad intent signals, matches, and audience counts are available in the conversation.

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

With Anteriad connected, an agent can look up the intent signals for a given account, list which intent topics are trending, and pull the account links and matches Anteriad holds for your target accounts. It can also report the contact, mobile ad ID, and cookie counts behind an Xplorer audience so you can size a campaign. Everything this connector does is reading and summarizing, so it answers questions about your Anteriad data rather than changing it.

No. An agent only sees the Anteriad intent data, matches, and audience counts that the person who signed in can already see, because every request runs inside that person's own access. Elaichi can narrow that access further per team, for example limiting a group to intent topics and counts only, but it can never widen what Anteriad itself allows.

Yes. One person connects Anteriad in Elaichi with the API key and shares the connection with a team, and nobody else on the team ever handles that key. Each person still signs in to Elaichi as themselves, so the audit log records exactly who asked for which Anteriad intent signals or audience counts.

The Anteriad connector is read only, so an agent can list and look up intent signals, matches, topics, and counts but cannot change or delete anything in Anteriad. On top of that, Elaichi lets you restrict each action separately, and a restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.

When you offboard someone in Elaichi, their access to Anteriad through every connected client ends at once. If they had shared an Anteriad connection with a team, it keeps working for everyone else. Disconnecting Anteriad once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client at the same time.

Yes. Anteriad 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.

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

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