# Fellow MCP connector

The Fellow connector brings meeting summaries, transcripts, action items and agendas to Claude, ChatGPT, Cursor and the Elaichi Agent, so once connected each person can ask about their own Fellow meetings and prepare agendas inside their own access.

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

## Facts

| | |
| --- | --- |
| Application | Fellow |
| Category | Conversational Intelligence |
| AI tools | 18 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | No |
| Native MCP | Yes. Fellow builds and runs this MCP server. Elaichi adds sign-in, access controls and an audit log on top |
| Support for its tools | help.fellow.ai/en |
| 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 |

## What you can ask once Fellow is connected

- Summarize yesterday's customer calls and list every open action item.
- Draft an agenda for Thursday's pipeline review from last week's notes.
- Which action items from the Acme kickoff are still unassigned?

## Connect Fellow in Elaichi

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

1. Open Connections, choose Add connection, and pick Fellow.
2. Optionally set Share with, then press Connect.
3. Approve it in Fellow. Fellow's own window opens. Whoever approves it decides what this connection can reach.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Fellow tools are exposed, rename them, or freeze arguments before anyone points a client at it.

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

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

## Fellow 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 Fellow 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

Only Read is granted by default, which is not enough to call a Fellow tool. 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. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Fellow through Elaichi

### Catch up on a customer call you missed

Sales. Ask for the Fellow summary, who was on the call and which action items came out of it, then get the follow-up written before the prospect forgets you.

### Prepare for a renewal in five minutes

Customer success. Search the last three meetings with the account in Fellow, pull the open action items and draft the agenda for the renewal call from what was actually promised.

### Turn a planning meeting into tracked work

Product. Read the transcript of the planning session, list every commitment that was made and check which action items in Fellow are still unassigned.

### Draft a one-on-one agenda from last time

People. Pull the previous one-on-one from Fellow, carry forward the unfinished items and write this week's agenda before the meeting starts.

### Find the decision buried in weeks of meetings

Leadership. Search Fellow transcripts for when a budget or hiring decision was made, who was in the room and what the summary recorded.

### Keep every team on the same meeting template

Operations. Create an agenda template in Fellow, set it as the default for a channel and apply it to upcoming meetings so notes land in the same shape everywhere.

## Elaichi vs Zapier MCP vs Composio for Fellow

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

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.

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

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.

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

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.

### Does connecting Fellow give the AI access to every meeting in my workspace?

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.

### Can my team share one Fellow connection?

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.

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

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.

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

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.

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

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.

### Is Elaichi an alternative to Zapier MCP for Fellow?

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.

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

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.

## All 18 Fellow tools

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

- **Get action items** (Get). Get action items.
- **Get meeting participants** (Get). Get meeting participants.
- **Get meeting summary** (Get). Get meeting summary.
- **Get meeting transcript** (Get). Get meeting transcript.
- **Search meetings** (Search). Search meetings.
- **List channels** (List). List channels.
- **Get channel details** (Get). Get channel details.
- **Read agenda** (Action). Read a note’s current contents.
- **Write agenda** (Action). Create an agenda for a meeting, or replace an existing agenda’s contents.
- **Edit agenda** (Action). Make a targeted change, such as adding a talking point or an action item, without rewriting the whole note.
- **Rename agenda** (Action). Change a note’s title without changing its contents.
- **Search agenda templates** (Search). Find saved templates by title, or list the most recently updated ones.
- **Get agenda template** (Get). Read one template's contents, or read the template a meeting series starts each of its notes from.
- **Create agenda template** (Create). Save a new template. New templates are personal unless you ask for a workspace-wide one.
- **Edit agenda template** (Action). Change a template's contents, title, or description.
- **Delete agenda template** (Delete). Permanently delete a saved template.
- **Apply agenda template** (Action). Put a template's contents into one meeting's agenda.
- **Set default agenda template** (Set). Make a template the default for a whole series, so every future note in that series starts from it.