Fellow MCP connector

Connect Fellow in Elaichi first: pick Fellow from the catalog, click connect, and approve the request on Fellow's own OAuth sign-in screen. 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 as yourself and your Fellow meetings, agendas and action items are available in the conversation.

Yes. Fellow is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. There is nothing to set up again per client, and each person signs in as themselves wherever they use it.

With Fellow connected, an agent can find a meeting, read its summary or full transcript, tell you who attended and list the action items that came out of it. It can also read, write and rename agendas, browse your channels, and find, create, edit or apply agenda templates. Short concrete asks work best, such as the action items from Tuesday's pipeline review rather than a long paragraph of instructions.

No. Access follows the person who signed in, so an agent can only reach the Fellow meetings, channels, transcripts and agendas that person can already open in Fellow. Elaichi can narrow that further, for example to reading summaries only, but it can never widen it beyond what Fellow itself allows that person.

Yes. One person connects Fellow in Elaichi and shares it with a team, and nobody else ever handles a credential or sees a login. Each teammate still signs in to Elaichi as themselves, so every read of a Fellow transcript or edit to an agenda is logged under their own name.

Yes. Restrictions in Elaichi work per action, so you can allow reading Fellow summaries and action items while blocking agenda edits or template deletion. A restricted action is never advertised to Claude, ChatGPT, Cursor or any other client, so no prompt, however worded, can reach it.

Offboarding that person in Elaichi ends their access to Fellow through every client at once. If they shared a Fellow connection with a team, it keeps working for everyone else. Disconnecting Fellow once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client at the same time.

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