Aggregators and gateways · MCP server
Forage: MCP server, setup and security
Forage is an open-source MCP server that lets an AI agent discover and install MCP servers while retaining tool knowledge across sessions. Its repository has 19 stars and its last commit is from February 21, 2026 and it is licensed under MIT.
What Forage does
According to its repository: “Self-improving tool discovery: searches registries, installs MCP servers as subprocesses without restarts, and persists tool knowledge across sessions.”
An MCP server gives an AI agent extra tools it calls during the conversation: the agent reads their description, decides to use them and gets the result back. Forage is listed under Aggregators and gateways, a category of 141 servers in the directory, where it ranks #103 by stars.
Topics declared by the repository: tool-discovery, ai-agent, claude, llm-tools.
Installing and connecting Forage
Distribution modes declared in the official MCP registry:
- npm package (Node.js, usually started with
npx)
Like any MCP server, you declare it in your client's configuration (Claude Desktop, Claude Code, Cursor, VS Code, Codex…): a name, the command that starts it or its URL, and any environment variables. The client then starts it and lists its tools. Project language: TypeScript. Listed systems: macOS, Windows, Linux.
Security: what to check
An MCP server runs code with the rights you give it, and the model reads its tool descriptions: a malicious or compromised server can hijack the agent. Read the code, or pick a maintained and widely used server, before connecting it.
None of the risk signals we track (system access, secrets, missing licence, abandonment) applies to Forage. That does not replace reading the code.
Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.
Project activity and maintenance
Created on February 17, 2026, the isaac-levine/forage repository has 19 stars and 4 forks, with 0 open issues. It has more stars than 37% of the servers in the directory. Last change 8 months ago. Version published in the registry: 0.1.1 (February 17, 2026).
Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.
Verdict
Forage is still a modest project: read its code and compare it with the alternatives before using it.
Strengths
- Listed in the official MCP registry
- Permissive licence (MIT)
Limitations
- No commit for 8 months
Alternatives
- GitDiagram18.4K ★
- Mockserver monorepo5K ★
- Paperclip106.8K ★
- Basebalance.cloud — x402 RPC & MCP gateway7.5K ★
- AIHOT8.5K ★
- OpenWork MCP Gateway24.2K ★
Learn more
Frequently asked questions
How do I install Forage?
Forage is distributed as npm package (Node.js, usually started with npx). Add it to your client's MCP configuration (Claude Desktop, Cursor, VS Code…) following the README of isaac-levine/forage.
Is Forage free?
The code is published under the MIT licence and can be used free of charge.
Is Forage safe?
No risk signal found (system access, secrets, licence, abandonment). As with any MCP server, keep rights minimal and read the code before sensitive use.
Is it an official server?
Nothing says so: it is a project published by isaac-levine on GitHub. Check who maintains it before giving it access.
What are the alternatives to Forage?
In the same category: GitDiagram, Mockserver monorepo, Paperclip, and Basebalance.cloud — x402 RPC & MCP gateway. GitDiagram and Mockserver monorepo score higher on our grid.
Related articles
- Build your own MCP server in 30 minutesOctober 24, 2026
- Automate your inbox with an AI agentOctober 18, 2026
- MCP, A2A, and tool calling: agent protocols explainedOctober 17, 2026
- Build an AI agent with n8n, without codingOctober 16, 2026
Neutrality. No affiliate links. No vendor pays to be reviewed, rated or ranked. Reviews are directed by François Chollet, neutral and factual, and every data point is dated and sourced. How we score