Practical overview
When it fits
Use it when your Neovim workflow needs MCP server management or server capabilities integrated with a supported chat plugin.
Who it is for
- Neovim users integrating MCP servers into editor-based chat workflows.
- Developers managing or testing local and remote MCP servers from Neovim.
Documented uses
- Manage and test MCP servers within Neovim.
- Connect server tools, resources, resource templates and prompts to supported chat plugins.
- Configure local and remote servers, including remote authentication.
Requirements & limits
The public repository displays an MIT license. The plugin is implemented in Lua.
- Supported transports are STDIO for local servers and Streamable HTTP or SSE for remote servers.
- Remote authentication options include OAuth with PKCE and headers for API keys or tokens.
- Supported MCP capabilities include tools, resources, resource templates and prompts; roots and sampling are marked unsupported.
- Chat integrations expose different capabilities; the documented support varies by plugin.
- Configuration features include JSON5, VS Code-style server settings, environment and input variables, and project-local configuration merging.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install MCPHub.nvim with Lazy.nvim and a global mcp-hub binary
Configure MCPHub.nvim to start with Neovim using Lazy.nvim and install its required mcp-hub binary globally.
Before you start
- Neovim 0.8.0 or later built with LuaJIT
- Node.js 18.0.0 or later
- plenary.nvim
- Lazy.nvim
- A Node package manager such as npm, yarn, or bun
Steps
Add ravitemer/mcphub.nvim to your Lazy.nvim plugin configuration.
Declare nvim-lua/plenary.nvim as a dependency.
Set the build command to npm install -g mcp-hub@latest.
Call require("mcphub").setup() in the plugin configuration.
Expected outcome
Lazy.nvim is configured to install the global mcp-hub binary when the plugin is updated and call MCPHub setup.
Guide limitations
- jq is optional and is described as improving servers.json formatting.
- The guide points to the configuration guide for additional plugin configuration.
Configure MCP servers and open the MCPHub interface
Define MCP servers in the default configuration file and access their management interface in Neovim.
Before you start
- MCPHub installed and set up in Neovim
- A server configuration file at ~/.config/mcphub/servers.json
Steps
Create or edit ~/.config/mcphub/servers.json and define servers under the mcpServers key.
Use supported server entries for local stdio or remote streamable-HTTP or SSE servers.
Run :MCPHub in Neovim to open the interface.
Use the interface to add, edit, or delete servers, install from the Marketplace, toggle servers, tools, or resources, and test tools or resources.
Expected outcome
MCPHub provides a Neovim interface for managing configured MCP servers and testing tools and resources.
Guide limitations
- The documented default configuration path is ~/.config/mcphub/servers.json; project-local configuration files are also detected and can create separate workspace hub instances.
- MCP roots and sampling are listed as unsupported.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 11 October 2026
- Original website title
- ravitemer/mcphub.nvim · Official homepage title · retained in its source language