ape-context vs .FAF Context
ape-context is a plugin bundle for AI coding tools published by suuus. Marketplaces we read that list it: 1 (Community GitHub marketplaces). .FAF Context is an MCP server published by Wolfe-Jam. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-21. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  ape-context |   .FAF Context |
|---|---|---|
| Community marketplace azure/git-ape | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed, marked deprecated Version: 2.1.3 Downloads/month (npm): 1 610 Downloads/week (npm): 569 Forks (GitHub): 3 Stars (GitHub): 7 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 4.0.1 Downloads/month (npm): 1 610 Downloads/week (npm): 569 Forks (GitHub): 3 Stars (GitHub): 7 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | ape-context | .FAF Context |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 2 (worse) | 7 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 3 (better) |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (faf-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 6, secrets among them: 2 | Not published |
| Parts of the bundle (differs) | 19 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/suuus/ape-context | github.com/wolfe-jam/faf-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
ape-context
Extension for git-ape that provides enhanced context management, allowing platform teams to set up a baseline for Engineering context, tools use & intent
.FAF Context
Dedicated IDE Edition. Persistent project context for Cursor, Windsurf, Cline, VS Code.
How to run each
ape-context
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
.FAF Context As a local MCP server: npm package
claude mcp add --transport stdio faf-mcp -- npx -y faf-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of .FAF Context publish no settings it asks for, so we do not compare settings.
What it can do: ape-context · What it can do: .FAF Context · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.