MCPHub Neovim

Add MCPHub.nvim to your Neovim plugin manager configuration. The example below uses lazy.nvim.

-- In your lazy.nvim plugins table:
{
  "ravitemer/mcphub.nvim",
  dependencies = { "nvim-lua/plenary.nvim" },
  config = function()
    require("mcphub").setup()
  end,
}

MCPHub reads server definitions from a JSON configuration file. Create ~/.config/mcphub/servers.json with your MCP server entries. The plugin supports environment variable expansion using the ${ENV_VAR} syntax and JSON5 (comments and trailing commas allowed).

{
  "mcpServers": {
    "fetch": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-fetch"]
    },
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "${HOME}/projects"]
    }
  }
}

Customize the setup call with the path to your config file, auto-start behavior, and any UI preferences.

require("mcphub").setup({
  config = vim.fn.expand("~/.config/mcphub/servers.json"),
  auto_start = true,
})

Run :MCPHub in Neovim to open the interactive server management interface. From here you can start/stop servers, browse available tools and resources, and run test calls to verify connectivity.

:MCPHub

Configure your chat plugin (e.g., CodeCompanion or Avante) to use MCPHub as the MCP provider. Each plugin has its own setup—refer to the MCPHub documentation at ravitemer.github.io/mcphub.nvim for plugin-specific snippets.

MCPHub automatically detects a .mcphub.json or .vscode/mcp.json file in the project root and merges it with the global config, allowing per-project MCP server customization without modifying the global file.