block
Enable Goose to Provide Its Own MCP Interface
Description: Currently, Goose functions as an MCP client—relying on external MCP servers for context and configuration. This proposal requests that Goose expose its own MCP interface. With this enhancement, Goose (or an external tool) could interact with itself via MCP to instantiate and configure a new Goose instance complete with the necessary context tools tailored to a specific project prompt.
Current Behavior: • Goose operates solely as an MCP client, requiring external MCP servers for interactions. • There is no mechanism for Goose to self-configure or dynamically instantiate a context-specific instance.
Proposed Enhancement: • Add a self-managed MCP interface to Goose. • Allow Goose to be both the client and the server, so that it can create and configure a new instance (or be configured by another tool) with the correct contextual tools for any given project. • Preserve existing client functionality while extending capabilities to include self-management.
Benefits: • Autonomy: Goose can manage its own instance setup, and CRUD operations with mcp servers. • Flexibility: External tools can also leverage this MCP interface to configure Goose dynamically for project-specific needs. • Streamlined Integration: Direct self-management via MCP enhances adaptability, allowing for more precise and context-aware deployments.
