Git vs Forage
A side-by-side look at the Git and Forage MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Git for other tools and integrations work as a local process; choose Forage for aggregators as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Git when
- You need dedicated capabilities in the Other Tools and Integrations domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
create_entities, create_relations, add_observations.
Choose Forage when
- You need dedicated capabilities in the Aggregators domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
forage_search, forage_evaluate, forage_install.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Other Tools and Integrations | Aggregators |
| Quality signal | 89/100 · Excellent | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,289 | 19 |
| Directory activity | 39 views 0 installs 0 upvotes | 7 views 0 installs 0 upvotes |
| Tools | 9 | 6 |
| Full listing | View Git | View Forage |
Tools & capabilities
Git tools 9
create_entitiesCreate multiple new entities in the knowledge graphcreate_relationsCreate multiple new relations between entities in the knowledge graph. Relations should be in active voiceadd_observationsAdd new observations to existing entities in the knowledge graphdelete_entitiesDelete multiple entities and their associated relations from the knowledge graphdelete_observationsDelete specific observations from entities in the knowledge graphdelete_relationsDelete multiple relations from the knowledge graphread_graphRead the entire knowledge graphsearch_nodesSearch for nodes in the knowledge graph based on a queryopen_nodesOpen specific nodes in the knowledge graph by their names
Forage tools 6
forage_searchSearch for MCP servers and tools across registries (Official MCP Registry, Smithery, npm). Describe what capability you need and get ranked results.forage_evaluateGet detailed information about a specific package — version, downloads, README summary, install command. Use this before installing to verify quality.forage_installInstall an MCP server and start it as a proxied subprocess. The server's tools become available immediately via Forage — no restart needed. IMPORTANT: Set confirm=true to proceed with installation (user will be prompted to approve the tool call).forage_learnWrite usage instructions for an installed tool to agent rule files (CLAUDE.md, AGENTS.md, .cursor/rules/). This persists knowledge across sessions so the agent remembers how to use the tool next time.forage_statusList all tools that Forage has installed and is currently proxying. Shows which servers are running, what tools they provide, and their install status.forage_uninstallRemove a previously installed tool. Stops the server, removes from manifest, and cleans up agent rules. Set confirm=true to proceed.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Git
{
"mcpServers": {
"git": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-memory"
]
}
}
}
Forage
{
"mcpServers": {
"isaac-levine-forage": {
"command": "npx",
"args": [
"-y",
"forage-mcp"
]
}
}
}
Frequently asked questions
Git is categorized under Other Tools and Integrations and uses a local stdio subprocess. Forage belongs to Aggregators and uses a local stdio subprocess. Pick Git for other tools and integrations work and Forage for aggregators.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Git is listed as free. Auth: no auth required. Forage is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add git and isaac-levine-forage as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Git has a quality signal of 89/100 (Excellent) with 39 views, 0 installs and 91,289 GitHub stars. Forage has 59/100 (Good) with 7 views, 0 installs and 19 GitHub stars.
