Vendor: fellow.ai · entry id 03-fellow · source 03-conversation-intel.md line 411
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)
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.
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.
Install, as the source shows it:
pip install fellowquoted from https://pypi.org/project/fellow/ on 2026-09-27, via pypi, a third party source
Packages seen, with the version on 2026-09-27:
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.
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)
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.
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.
github.com/fellowapp tied to the vendor by rule 3, account website https://fellow.ai has the vendor's domain, confidence strong
The five most recently pushed, on 2026-09-08:
| Repository | Kind | Description | Stars | Pushed | Latest release |
|---|---|---|---|---|---|
| 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 | SDK | Python port of fasiha/mudderjs | 6 | 2026-07-25 | v0.3.1 |
| prosemirror-py | SDK | Python implementation of core ProseMirror modules | 62 | 2026-07-20 | v0.6.1 |
| traefik-cluster-ratelimit | plugin or integration | Traefik Plugin for Rate Limiting Middleware | 1 | 2026-07-08 | |
| 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.
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.
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
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.