🎉 v5.0.0 - ✨ CodeCompanion function tools

[ravitemer]

Breaking Changes

Hi Guys, some exciting news to those that use CodeCompanion with mcphub. CodeCompanion now supports function tools (with main branch) in addition to the xml tools (with has-xml-tools branch). There are many advantages with function tools when the LLM supports them. Mainly they are better in accuracy, speed, tokens etc. Please see the detailed discussion at olimorris/codecompanion.nvim#1306

In view of v15 release of codecompanion we have made some breaking changes to the mcphub.nvim plugin.

• Now mcphub provides @mcp as both an xml tool (when using has-xml-tools branch of codecompanion) as well as a function tool (with main branch of codecompanion) automatically based on the codecompanion branch.

1. 🚨 You need to remove the old mcp tool entry from codecompanion.config.strategies.chat.tools

require("codecompanion").setup({
 -- other codecompanion config
  strategies = {
    chat = {
       tools = {
     -- Remove old mcp tool which will be auto added as a tool group with two individual tools.
      --   ["mcp"] = {
      --     callback = function()
      --       return require("mcphub.extensions.codecompanion")
      --     end,
      --     description = "Call tools and resources from MCP Servers",
      --   },
     },
    },
  },
})

2. codecompanion extension is now more streamlined in one place using the codecompanoin's extensions api.

require("codecompanion").setup({
--other config
extensions = {
  mcphub = {
    callback = "mcphub.extensions.codecompanion",
    opts = {
      make_vars = true,
      make_slash_commands = true,
      show_result_in_chat = true,
    },
  },
 },
})

• The @mcp tool is split into two separate tools use_mcp_tool and access_mcp_resource
• mcphub.config.extensions.codecompanion is deprecated as the options are now declared at codecompanion extension itself.