Plain MCP connector

Connect Plain in Elaichi first: pick Plain from the catalog and sign in with your Plain account over OAuth, with 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. Claude signs you into Elaichi, and from then on it can work with your Plain threads, customers, tenants, and help center articles.

Yes. Once Plain 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 Plain once and every client you use picks it up.

It can search your Plain threads, draft and send replies, assign threads to teammates, and add or remove labels. It can look up a customer or tenant to see who is asking and what else is open for them, and it can create and update help center articles. Short, concrete asks work best, such as asking it to assign every unassigned billing thread to Priya rather than writing a long paragraph.

No. The AI works inside the Plain access of the person who signed in, so it sees the threads, customers, tenants, and articles that person can already see in Plain. Elaichi can narrow that further with restrictions, and it never widens it beyond what Plain itself allows.

Yes. One person connects Plain in Elaichi and shares it with a team, and nobody else ever handles a credential. Each teammate still signs into Elaichi as themselves, so the audit log records who replied to a thread or changed an article, not just that the shared Plain connection did.

Yes. Restrictions in Elaichi apply per action, so you can allow searching and reading Plain threads while blocking replies, assignments, or edits to help center articles. A restricted action is never shown to the AI client at all, so no prompt, however it is worded, can reach it.

Offboarding the person in Elaichi ends their access to Plain through every client at once. If they had shared their Plain connection with a team, it keeps working for everyone else. If you want it gone entirely, disconnecting Plain once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client together.

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

Yes. Both let Claude, ChatGPT or Cursor use Plain. 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 Plain 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 Plain: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.