🚀 CodeCompanion + MCP Servers

[ravitemer]

🚀 CodeCompanion + MCP Servers

Hey folks! I wanted to share a Neovim plugin I've been working on called mcphub.nvim. It's designed to make working with Model Context Protocol (MCP) servers super smooth in Neovim.

Here's a quick demo of how it looks in action:

Using Codecompanion Chat plugin

chatdemo.mp4

The main idea was to make it really easy to manage and use MCP servers right from Neovim. You just need one command :MCPHub to get started, and it gives you this nice UI where you can test out all your tools and resources.

CodeCompanion.nvim integration! 🤖

I've also added support for CodeCompanion.nvim, which means you can use all your MCP tools right in your chat interface.

To use it with CodeCompanion, just add the MCP tool to your config like this:

tools = {
  ["mcp"] = {
    callback = require("mcphub.extensions.codecompanion"),
    description = "Call tools and resources from the MCP Servers",
    opts = {
      user_approval = true,
    },
  },
}

Setting it up is pretty straightforward

If you're using lazy.nvim, you can install it like this:

{
    "ravitemer/mcphub.nvim",
    dependencies = {
        "nvim-lua/plenary.nvim",
    },
    build = "npm install -g mcp-hub@latest",
    config = function()
        require("mcphub").setup({
            port = 3000,
            config = vim.fn.expand("~/mcpservers.json"),
        })
    end
}

Some cool features you might like:

• 🎯 Single command (:MCPHub)
• 🔄 Super smart about managing server lifecycles
• ⚡️ Works with both sync and async operations
• 🧹 Clean automatic server cleanup
• 📋 Nice API for programmatic access

@olimorris @GitMurf
Would love for you all to try it out and let me know what you think! Check for more info at: https://github.com/ravitemer/mcphub.nvim

[olimorris]

Take a bow @ravitemer. This looks amazing. Also, you've added process flowcharts so you immediately get a star 😉. Thanks for making CodeCompanion a first class extension.

Do you have some example MCP servers that I could setup and use to test this out?

Tools are going to be a big focus of my work for the next month. I've got a big PR which will add queuing and much more robust process flows to the tooling implementation. And then I plan to move to function calling/tool use that is supported by most LLMs.

[ravitemer]

❤️ Thanks a lot @olimorris. I use codecompanion regularly and am in love with it. Thanks for the amazing work. I got this idea while creating tools for my workflow which are already available as mcp servers. Managing mcp servers using lua seemed difficult. So I went with creating a server on top of mcp servers config file so that any kind of chat client can just make CRUD requests to get access to all of them. This is my first ever plugin, hope you like it and love your feedback. Below is a minimal config with fetch, filesystem and everything enabled. You can test each tool in the ui if you want. everything is a dummy mcp server for testing to test tools, resources and resource templates. Please see mcphub.extensions.codecompanion to see mcp tool implementation. Any suggestions are greatly appreciated.

NOTE:
Currently the UI will only show text response when a tool is called. Without the return_text=true we can get the whole response with all kinds of data which we can use with call_tool api once the chat supports sending images.

Looking forward to the PR. Thanks a lot for my first star 😃 .

Relevant links:
https://github.com/modelcontextprotocol/servers.git
https://github.com/punkpeye/awesome-mcp-servers.git
https://glama.ai/mcp/servers
https://github.com/wong2/mcp-cli.git

{
  "mcpServers": {
    "fetch": {
      "command": "uvx",
      "disabled": false,
      "args": [
        "mcp-server-fetch"
      ]
    },
    "everything": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-everything"
      ]
    },
    "git": {
      "command": "uvx",
      "disabled" : true,
      "args": [
        "mcp-server-git",
        "--repository",
        "/path/to/any-local-git-repo"
      ]
    },
    "filesystem": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-filesystem",
        "/path/to/anyfolder"
      ]
    },
    "puppeteer": {
      "command": "docker",
      "disabled" : true,
      "args": [
        "run",
        "-i",
        "--rm",
        "--init",
        "-e",
        "DOCKER_CONTAINER=true",
        "mcp/puppeteer"
      ]
    }
  }
}

[nshen]

Looks amazing, with mcp we don't need builtin tools anymore ? like @files ?

[ravitemer]

It's upto you, see what fits you best. I guess @files can be replaced by filesystem mcp server with only the tools you need enabled dynamically in the new v2.0.0 to save tokens. I think @editor tool is awesome as we can see the changes happen. Same goes for @code_runner.

[ZohnyZeyad]

Great work @ravitemer !
I can't help but notice the simple yet beautiful UI config you got in the demo there, can you please share your dotfiles for inspiration?

[ravitemer]

Thanks. There is no particular custom settings I configured myself. I am using awesome LunarVim which is more or less zero config IDE for neovim. It doesn't conflict with your existing nvim config, so feel free to give it a try

[blankenshipz]

This is super cool! I'm very new to MCP can you give a little background on why MCP servers are better than interacting with something like the cmd runner? I'm guessing because they support more diverse use cases?

[ravitemer]

Yeah! Exactly. The inbuilt @editor and @cmd_runner are awesome. For most of the coding, they’re enough. MCP servers take it to another level. They let you hook up to your own personal data— databases and anything that has an api you’re working with—and they’re super easy to extend. Building one that fits exactly what you need is a super simple and you get to tap into cool ideas from the community too. Stuff like Puppeteer, browserbase, lets the LLM mess around and design things step-by-step. You don’t have wait for a feature you need. Just add an MCP server into your config, turn on the tools you want, and you’re good to go. There are so many cool mcp servers already available.

mcphub.nvim is a sort of mcp server playground where you can test these servers, make crud calls to your data, and hook a chat plugin like codecompanion with the interface to give llm super powers 😄