Replies: 1 comment
-
|
As context, the ACP implementation does support MCP servers just not via the UI of the chat buffer. They have to be shared with the adapter via the user's config. I think the effort vs complexity matrix for shim'ing CodeCompanion's own tools to a coding agent isn't worthwhile as there's nothing unique that CodeCompanion really offers. Making it easier to share MCP tools with an agent, I totally get. I think CodeCompanion should do more to allow users to bring their own MCP servers without requiring the extension, alas, that's still low priority right now. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Just a random thought that occurred to me. Since mcphub.nvim supports lua MCP servers/tools and ACP allows clients to provide MCP servers to the agent, would it be possible to implement a shim that translates codecompanion tool definitions to MCP tools, so that the agents can make use of them?
I suppose this would make sense for tools like
list_code_usageor my experimental dap extension, which are tightly integrated into the editors and would be difficult to set up with a standalone MCP. @ravitemer, do you think this is a feature that is worth looking into?Beta Was this translation helpful? Give feedback.
All reactions