ConfigsMay 12, 2026·2 min read

mcphub.nvim — Neovim MCP Client & UI

Neovim MCP client that runs servers via mcp-hub and exposes an interactive `:MCPHub` UI so chat plugins can browse, test, and call tools.

MCP Hub
MCP Hub · Community
Agent ready

Safe staging for this asset

This asset is staged first. The copied prompt tells the agent to inspect the staged files and ask before activating scripts, MCP config, or global config.

Stage only · 17/100Policy: stage
Agent surface
Any MCP/CLI agent
Kind
CLI Tool
Install
Stage only
Trust
Trust: Established
Entrypoint
Asset
Safe staging command
npx -y tokrepo@latest install ea3df664-b9f6-4b3d-b879-ed4f2b7db0ec --target codex

Stages files first; activation requires review of the staged README and plan.

Intro

Neovim MCP client that runs servers via mcp-hub and exposes an interactive :MCPHub UI so chat plugins can browse, test, and call tools.

  • Best for: Neovim users who want MCP servers inside the editor, with a UI to test tools and wire them into chat plugins
  • Works with: Neovim, Node.js, mcp-hub; integrates with popular Neovim chat plugins
  • Setup time: 15–30 minutes

Practical Notes

  • Quant: baseline your setup with 1 server and 3 tool calls; aim for <2 minutes from :MCPHub open to first successful tool run.
  • Quant: keep versions explicit: Neovim >= 0.8 and Node.js >= 18 are hard requirements—record them in your dotfiles.

How to make MCP in-editor feel “native”

A practical pattern is to keep three layers separate:

  1. Server definition (what runs, with what env)
  2. UI discovery/testing (:MCPHub as a tool console)
  3. Chat integration (only wire the few tools you actually use)

Debugging checklist

  • Confirm Node.js and Neovim versions first.
  • Ensure mcp-hub is installed and on PATH (the Lazy build step can do this).
  • Start with one small server/tool, then expand.

Team workflow tip

Store your MCP server config in version control and treat it like infra: reviews, changelog notes, and rollback steps.

FAQ

Q: Do I need to install mcp-hub separately? A: The recommended Lazy.nvim setup installs mcp-hub via the build step.

Q: Should I expose every tool to my chat plugin? A: No. Start with 1–3 tools you actually use and expand deliberately.

Q: What breaks most often? A: Version drift (Neovim/Node) and PATH issues for the mcp-hub binary.

🙏

Source & Thanks

Source: https://github.com/ravitemer/mcphub.nvim > License: MIT > GitHub stars: 1,766 · forks: 83

Discussion

Sign in to join the discussion.
No comments yet. Be the first to share your thoughts.

Related Assets

nvim-dap — Debug Adapter Protocol Client for Neovim

DAP client implementation enabling debugging directly in Neovim with breakpoints, stepping, variable inspection

Configs
AI Open Source

nvim-lspconfig — Quickstart Configurations for Neovim LSP

Provides default configurations for dozens of language servers so you can set up Neovim's built-in LSP client with minimal boilerplate — just install the server and call setup().

Configs
AI Open Source

mason.nvim — Portable Package Manager for Neovim LSP, DAP & Linters

A Neovim plugin that installs and manages LSP servers, DAP adapters, linters, and formatters from a unified registry, with a built-in UI and automatic PATH management.

Configs
AI Open Source

MCPHub — Centralized MCP Server Management Hub

Manage multiple MCP servers from one dashboard. Smart routing, hot-swap config, OAuth 2.0 auth. Deploy via Docker in one command. Apache-2.0, 2,000+ stars.

MCP Configs
MCP Hub
◈Home🔍Search👤Me