Please describe the feature you want
The Model Context Protocol (MCP) is a key feature of the Pochi VSCode extension, allowing users to extend the toolset with custom tools from various sources. Currently, this functionality is not available in the Pochi CLI. This issue proposes a roadmap to implement MCP support in the CLI, enabling users to leverage the same powerful extensibility in their terminal-based workflows.
Roadmap:
-
Integrate MCP Hub: The CLI needs a mechanism to manage MCP connections, similar to the McpHub in the VSCode extension. This will involve creating a new module in packages/cli to handle the lifecycle of MCP connections. The existing implementation in packages/vscode/src/integrations/mcp/mcp-hub.ts can be used as a reference.
-
Configuration: The CLI needs a way to configure MCP servers. This could be a new configuration file (e.g., ~/.pochi/mcp.json) or a new section in the existing configuration file. The configuration should be consistent with the format used in the VSCode extension.
-
Tool Execution: The CLI needs to be able to execute tools from MCP servers. This will involve extending the existing tool execution logic in packages/cli/src/task-runner.ts to support MCP tools.
Additional context
This feature will bring the Pochi CLI closer to feature parity with the VSCode extension, providing a more consistent and powerful experience for users who work in both environments.
🤖 Generated with Pochi
Please describe the feature you want
The Model Context Protocol (MCP) is a key feature of the Pochi VSCode extension, allowing users to extend the toolset with custom tools from various sources. Currently, this functionality is not available in the Pochi CLI. This issue proposes a roadmap to implement MCP support in the CLI, enabling users to leverage the same powerful extensibility in their terminal-based workflows.
Roadmap:
Integrate MCP Hub: The CLI needs a mechanism to manage MCP connections, similar to the
McpHubin the VSCode extension. This will involve creating a new module inpackages/clito handle the lifecycle of MCP connections. The existing implementation inpackages/vscode/src/integrations/mcp/mcp-hub.tscan be used as a reference.Configuration: The CLI needs a way to configure MCP servers. This could be a new configuration file (e.g.,
~/.pochi/mcp.json) or a new section in the existing configuration file. The configuration should be consistent with the format used in the VSCode extension.Tool Execution: The CLI needs to be able to execute tools from MCP servers. This will involve extending the existing tool execution logic in
packages/cli/src/task-runner.tsto support MCP tools.Additional context
This feature will bring the Pochi CLI closer to feature parity with the VSCode extension, providing a more consistent and powerful experience for users who work in both environments.
🤖 Generated with Pochi