Forage
Let your agent discover, install, and adopt new MCP servers on demand instead of you manually curating every integration.
Overview
Forage is a MCP server for the Build phase that enables agents to discover, install, and use additional MCP servers automatically.
What is this MCP server?
- Self-improving MCP discovery oriented to AI agents
- Find, install, and use new MCP servers from within agent sessions
- stdio npm package forage-mcp v0.1.1
- Reduces manual registry hunting as project needs change
- Server version 0.1.1; npm identifier forage-mcp
- Described capability triad: find, install, and use new MCP servers
Community signal: 11 GitHub stars.
What problem does it solve?
Static MCP configs force constant context-switching to registries while your agent already knows what capability it is missing.
Who is it for?
Power users shipping agent-heavy products who expect integration needs to evolve weekly.
Skip if: Teams with locked-down allowlists that forbid dynamic package installs, or beginners who want one fixed toolset.
What do I get? / Deliverables
With forage-mcp registered, your agent can expand its own tool surface by finding and installing MCP servers during the session.
- Bootstrapped forage-mcp stdio server in agent config
- Agent-driven discovery and installation of additional MCP servers
- Faster integration experiments without manual registry browsing
Recommended MCP Servers
Journey fit
First shelf is Build/agent-tooling because expanding the tool graph is how you compose the product during development. Agent-tooling captures self-improving discovery—meta-MCP that extends what your agent can call mid-project.
How it compares
Dynamic MCP registry agent, not a single-domain data connector or journey-wide methodology skill.
Common Questions / FAQ
Who is Forage for?
Solo builders and indie teams running Claude Code or Cursor who want agents to grow their MCP toolset without manual registry chores.
When should I use Forage?
Use it when you are in Build or later phases and repeatedly need new MCP capabilities that you did not list in the initial config.
How do I add Forage to my agent?
Install the npm package forage-mcp, register it as a stdio MCP server, and ensure your agent policy allows it to install additional MCP packages you approve.