mcphub.nvim

mcphub.nvim is an MCP client for Neovim designed to seamlessly integrate MCP servers into your editing workflow. It provides a unified interface to manage, test, and interact with MCP servers directly from Neovim, enabling smooth communication with tools and chat plugins. The hub exposes capabilities such as Tools, Resources, Resource Templates, Prompts, and real-time change notifications for lists and templates, all accessible through familiar Neovim workflows. When connected to compatible MCP servers via Streamable-HTTP or SSE transports, you can browse server capabilities, invoke tools, fetch resources, and manage prompts without leaving your editing environment. The plugin also supports integration with popular chat tooling like Avante.nvim, CodeCompanion.nvim, and CopilotChat.nvim, so you can leverage these integrations to run commands, fetch images or templates, and get prompt-based assistance alongside your code edits.

Prerequisites:

• Neovim 0.9 or newer
• Lua support in Neovim (built-in LuaJIT)
• A compatible MCP server configuration or access to a running MCP server

Installation (example using packer.nvim):

use {
  "ravitemer/mcphub.nvim",
  requires = {
    { "nvim-lua/plenary.nvim" },
    { "nvim-lua/popup.nvim" }
  },
  config = function()
    require("mcphub").setup()
  end
}

Basic setup (Neovim config):

require("mcphub").setup({
  -- optional: customize connections, transports, and UI
  servers = {
    mcphub = {
      transport = "streamable-http", -- or: sse, stdio depending on your setup
      endpoint = "https://example-mcp-server.org/api"
    }
  }
})

Usage tips:

• Ensure your MCP server is reachable from your machine.
• If using a local server, ensure stdio transport is enabled if required by your setup.
• Use the built-in documentation and help views to discover available tools, resources, and prompts.

Tips and notes:

• This MCP client focuses on Neovim integration; if you run into transport errors, verify the server supports Streamable-HTTP or SSE as configured.
• Environment variables like MC_HOST or API keys may be required by certain servers. Use placeholders in the mcp_config or set them in your environment where the MCP client runs.
• If you upgrade Neovim or the plugin, re-run your plugin manager to ensure all dependencies (like plenary or lua-json5) are up to date.
• For best results, enable real-time updates (Tool/Resource/Prompt list changes) to keep your local view in sync with the remote MCP server.