# Fellow: MCP server status, API access gate and what it does

> A meeting assistant that records, transcribes and summarises calls, then turns them into action items and... Official MCP, Paid, self-serve. Checked 2026-08-25.

*Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).*

*Maintained by Andrew McGuire (https://andrewcmcguire.com), who also publishes https://gtmsignals.co and https://justsaid.ai.*

---
[Directory](../index.md) /
[Conversation Intel](../categories/conversation-intel.md) /
Fellow

# Fellow

[Official MCP](../mcp/official.md)
[Paid, self-serve](../gates/paid.md)
[Conversation Intel](../categories/conversation-intel.md)
RESEARCHED
Checked 2026-08-25
CLI: fellow (community)

> **RESEARCHED** Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 1.

Vendor: [fellow.ai](https://fellow.ai) · entry id 03-fellow · source 03-conversation-intel.md line 411

**What it does**
A meeting assistant that records, transcribes and summarises calls, then turns them into action items and decisions tied to the calendar event they came from.

**AI features, separated from automation with an AI label on it**
AI-generated meeting summaries, action-item extraction and talking points. The transcription and calendar sync are automation.

**RevOps role**
Meeting record and follow-up source that an agent can query directly instead of scraping the CRM activity log.

**MCP server**

- **Status bucket**: Official MCP

- **Auth**: OAuth, with OAuth 2.0 dynamic discovery supported.

- **Parsed URLs**: 2 found in the mcp_url field

- **Endpoint probe**: answered, asking for a key
- **Endpoint URL**: [https://fellow.app/mcp](https://fellow.app/mcp)
- **Probed**: 2026-09-04, HTTP 401

The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established by hand on 2026-08-25. On 2026-09-04 the recorded URL answered an MCP initialize as a server, which is liveness and nothing more: nobody has run its tools.

mcp_status, verbatim from the file:

official

mcp_url, verbatim from the file:

https://fellow.app/mcp (docs: https://developers.fellow.ai/reference/mcp-server)

- [https://fellow.app/mcp](https://fellow.app/mcp)
- [https://developers.fellow.ai/reference/mcp-server](https://developers.fellow.ai/reference/mcp-server)

**What this server exposes**

Not harvested yet. Unmeasured, not empty: nobody has read this server's tool list, so this page says nothing about what it exposes.

141 of the 741 entries that record an official or community MCP server carry a harvested tool list. The other 600 are unmeasured, which is not the same as empty. Harvest last run 2026-09-27. The full roll up is on the [tools index](../tools-index.md).

**Command line**

This is a third party's CLI. It was published by somebody other than the vendor, so it is that author's surface for the vendor's API and not the vendor's published surface. The two must not be read as the same thing.

- **Binary**: fellow
- **Status**: community CLI, third party
- **Strongest evidence**: pypi
- **Harvested**: 2026-09-27

Install, as the source shows it:

```
pip install fellow
```

quoted from [https://pypi.org/project/fellow/](https://pypi.org/project/fellow/) on 2026-09-27, via pypi, a third party source

Packages seen, with the version on 2026-09-27:

- [pypi: fellow 0.1.0, third party](https://pypi.org/project/fellow/)

A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it. Harvest date 2026-09-27.

**Access gate**

- **Gate bucket**: Paid, self-serve

- **Can a solo operator reach it**: Yes, by paying, no sales call

api_gate, verbatim from the file:

paid (API access is listed on Team at $7/user/mo annual and every tier above; the Free plan does not include it)

**API documentation**

[https://developers.fellow.ai/reference/mcp-server](https://developers.fellow.ai/reference/mcp-server)

No documentation text is reproduced anywhere on this site. Read the vendor page for the prose. The structured docs digest specced in SPEC section 3 has not been built or crawled: docs_digest is null on every entry in this build.

**GitHub health**

Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build.

The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale.

**On GitHub**

[github.com/fellowapp](https://github.com/fellowapp) tied to the vendor by rule 3, account website https://fellow.ai has the vendor's domain, confidence strong

- **Public repositories**: 18, forks excluded, as read on 2026-09-08
- **Mention MCP**: 0 of them
- **Look like CLIs**: 0 of them
- **Latest push**: 2026-08-22

The five most recently pushed, on 2026-09-08:

| Repository | Kind | Description | Stars | Pushed | Latest release |
|---|---|---|---|---|---|
| [nix-support](https://github.com/fellowapp/nix-support) | infrastructure | A Nix flake providing easy access to useful packages that might not be available or up-to-date in the main nixpkgs... | 2 | 2026-08-22 | |
| [mudder-py](https://github.com/fellowapp/mudder-py) | SDK | Python port of fasiha/mudderjs | 6 | 2026-07-25 | v0.3.1 |
| [prosemirror-py](https://github.com/fellowapp/prosemirror-py) | SDK | Python implementation of core ProseMirror modules | 62 | 2026-07-20 | v0.6.1 |
| [traefik-cluster-ratelimit](https://github.com/fellowapp/traefik-cluster-ratelimit) | plugin or integration | Traefik Plugin for Rate Limiting Middleware | 1 | 2026-07-08 | |
| [n8n-nodes-fellow](https://github.com/fellowapp/n8n-nodes-fellow) | plugin or integration | The Official Fellow n8n Node | 1 | 2026-06-08 | v1.0.3 |

Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08.

**Jobs it can do**

- [Fetch a call transcript](../jobs/fetch-call-transcript.md)
- [Summarize a meeting](../jobs/summarize-meeting.md)

A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records.

Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total.

**Sources**

- [https://developers.fellow.ai/reference/mcp-server](https://developers.fellow.ai/reference/mcp-server)
- [https://help.fellow.ai/en/articles/12622641-fellow-s-mcp-server](https://help.fellow.ai/en/articles/12622641-fellow-s-mcp-server)
- [https://fellow.ai/blog/fellow-mcp-server/](https://fellow.ai/blog/fellow-mcp-server/)
- [https://fellow.ai/pricing](https://fellow.ai/pricing)

4 source URLs. Raw sources field, verbatim:

https://developers.fellow.ai/reference/mcp-server, https://help.fellow.ai/en/articles/12622641-fellow-s-mcp-server, https://fellow.ai/blog/fellow-mcp-server/, https://fellow.ai/pricing

**Notes, verbatim from the file**
Added 2026-08-25 in the coverage sweep. ADMIN-GATED, which is a distinct gate from the usual pricing gate and worth naming: a workspace admin must enable "Allow users to create MCP connections" under Settings, Security before any individual user can connect at all. Access then inherits the connecting user's existing Fellow permissions. The vendor does not state which pricing plan is required, so api_gate is recorded as unknown rather than guessed. [api_gate 2026-08-25] Reclassified unknown -> paid from the vendor's own page (https://fellow.ai/pricing): API access is listed on Team at $7/user/mo annual and every tier above; the Free plan does not include it.

**Provenance**

- **Entry id**: 03-fellow

- **Source file**: 03-conversation-intel.md

- **Source line**: 411

- **Tier**: RESEARCHED

- **last_checked**: 2026-08-25

- **Data baked**: 2026-09-27

Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the [methodology page](../methodology.md).
