mcphub.nvim
mcphub.nvim is a Neovim plugin that integrates the Model Context Protocol (MCP) into your editor, allowing you to connect and manage MCP servers directly from Neovim. It works with popular chat plugins like Avante and CodeCompanion, enabling seamless access to external tools and resources within your editing workflow.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | ravitemer/mcphub.nvim |
| Owner | ravitemer |
| Primary language | Lua |
| License | MIT — OSI-approved |
| Stars | 1.8k |
| Forks | 87 |
| Open issues | 26 |
| Latest release | v6.2.0 (2025-07-31) |
| Last updated | 2026-01-18 |
| Source | https://github.com/ravitemer/mcphub.nvim |
What mcphub.nvim is
A Lua-based Neovim client implementing MCP specification support for tools, resources, prompts, and resource templates via Streamable-HTTP, SSE, and STDIO transports. Features OAuth and header-based authentication, real-time capability tracking, multi-instance synchronization, and native Lua MCP server authoring.
Get the mcphub.nvim source
Clone the repository and explore it locally.
git clone https://github.com/ravitemer/mcphub.nvim.gitcd mcphub.nvim# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Requires Neovim (version not specified in data); verify compatibility before rollout.
- OAuth flow support (PKCE) requires proper redirect URI configuration; plan authentication setup early.
- Project-local `.nvim/mcp.json5` auto-detection can cause config conflicts if not clearly documented to teams.
- Multi-instance sync relies on file-watching; verify behavior on network filesystems or CI environments.
- Lua native MCP servers require Lua expertise; evaluate team capability if custom servers planned.
When to avoid it — and what to weigh
- Neovim Not Your Primary Editor — mcphub.nvim is Neovim-only. If your team uses VS Code, JetBrains IDEs, or other editors, consider alternatives with broader IDE support.
- Roots or Sampling Capabilities Required — The plugin explicitly does not support MCP Roots or Sampling. If your workflow depends on these advanced MCP features, this is not suitable.
- Offline or Air-Gapped Environments — Server discovery and marketplace require network access. Heavily restricted environments will need manual server configuration.
- Production LLM Inference at Scale — This is an editor integration layer, not a production MCP server runtime. Evaluate dedicated MCP server infrastructure for large-scale deployments.
License & commercial use
MIT License: permissive OSI-approved license allowing commercial use, modification, and distribution with attribution.
MIT is a permissive license permitting commercial use without royalty or licensing restrictions. Suitable for proprietary tooling and commercial products. No copyleft obligations. Review MIT text to confirm attribution requirements align with your commercial deployment model.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
MCP servers act as execution contexts; evaluate trust and input validation for each connected server. OAuth PKCE flow is standard but requires secure redirect URI handling. Environment variable and command execution syntax (`${}`) can be misused if user-controlled; sanitize or document restrictions. Credentials stored in config files; advise on encryption or secret management tooling. No formal security audit data provided.
Alternatives to consider
Anthropic MCP (native SDK or Claude desktop integration)
Direct MCP support in Claude desktop and Anthropic SDKs; broader ecosystem support but lacks Neovim-specific editor integration.
VS Code MCP Extensions (e.g., built-in or third-party)
Native VS Code MCP support for broader IDE adoption and first-class LLM editor integration, but excludes Neovim users.
Custom Neovim Lua Scripting (manual API calls)
Full control and no external dependencies, but requires significant Lua expertise and lacks standardized MCP protocol compliance.
Build on mcphub.nvim with DEV.co software developers
Visit the mcphub.nvim documentation to get started, or join the Discord community for support and best practices.
Talk to DEV.coRelated open-source tools
Surfaced by semantic similarity across the DEV.co open-source index.
Related on DEV.co
Explore the category and the services that help you build with it.
mcphub.nvim FAQ
Does mcphub.nvim support local and remote MCP servers?
Can I use mcphub.nvim with Avante, CodeCompanion, or CopilotChat?
What MCP features are not supported?
Can I write custom MCP servers in Lua?
Work with a software development agency
Adopting mcphub.nvim is usually one piece of a larger software development effort. As a software development agency, DEV.co provides software development services and web development expertise — pairing senior software developers and web developers with your team to design, build, and operate mcp servers software in production.
Integrate MCP into Neovim Today
Visit the mcphub.nvim documentation to get started, or join the Discord community for support and best practices.