Skip to content
← Tools / Skills
Toolravitemer (community)/10 trustMetrics-checked

MCPHub.nvim

MCP client for Neovim — wire MCP servers straight into your editor workflow.

Visit official site →

About

MCPHub.nvim is a Neovim plugin that acts as an MCP client, integrating MCP servers directly into your editing workflow. It is the missing bridge between the MCP ecosystem and Neovim: once configured, MCP servers' tools, resources, and prompts become available inside the editor, and it pairs naturally with AI coding plugins like Avante.nvim and CodeCompanion.nvim.

The plugin handles server lifecycle and discovery, exposes a UI for browsing available servers and their capabilities, and lets you invoke MCP tools without leaving your buffers. It is a small, focused MIT-licensed project (~1,800 stars) maintained by ravitemer, and it has picked up enough traction to be sponsored and referenced by terminal vendors building MCP integrations.

This is plumbing, not a product: Neovim-only, configured in Lua, and most useful as a companion to an AI assistant plugin rather than on its own. If your editor is VS Code or Cursor, their built-in MCP support makes this irrelevant.

What it can do

  • Full MCP client inside Neovim: server management, tool invocation, resource browsing
  • Server browser UI (:MCPHub) for inspecting capabilities and testing tools
  • Companion integration with Avante.nvim and CodeCompanion.nvim
  • Supports stdio and SSE server transports
  • MIT licensed; lightweight Lua implementation

Setup

  1. Install via your Neovim plugin manager (e.g. lazy.nvim: { "ravitemer/mcphub.nvim" }).
  2. Declare your MCP servers in the plugin's setup config (stdio or SSE transports).
  3. Run :MCPHub to browse servers, tools, resources, and prompts.
  4. Pair with an AI plugin (Avante.nvim, CodeCompanion.nvim) to let the assistant call MCP tools.

Prerequisites

Neovim 0.10+; a Lua-based config (lazy.nvim recommended). MCP servers you want to connect (Node.js or Python runtimes for most).

Use cases

codemcpneovimdeveloper-tools

Works with

Trust score — 8/10

/10 trustMetrics-checked

Scored 8/10 (metrics tier, metrics-v1). Evidence: 1,789 GitHub stars (ravitemer/mcphub.nvim); MIT license confirmed via GitHub API; MCP client for Neovim: server lifecycle/discovery, :MCPHub browser UI, stdio+SSE transports; pairs with Avante.nvim and CodeCompanion.nvim — verified against repo README; Sponsored/referenced by terminal vendors (Warp) building MCP integrations — README verified. Manual review: niche plumbing for Neovim users, not a standalone product; Neovim-only scope is the honest limit; thin but consistent evidence. License: MIT.

★ 1,789 GitHub stars

How the trust score is built

Full methodology →
Adoption · stars/downloads, log-scaled vs peers
5.0/10
Maintenance · recency, releases, issue load
8.0/10
Openness · license + docs
10.0/10
Manual review · sanity read + red-flag check
8.0/10
  • · 1,789 GitHub stars (ravitemer/mcphub.nvim); MIT license confirmed via GitHub API
  • · MCP client for Neovim: server lifecycle/discovery, :MCPHub browser UI, stdio+SSE transports; pairs with Avante.nvim and CodeCompanion.nvim — verified against repo README
  • · Sponsored/referenced by terminal vendors (Warp) building MCP integrations — README verified
  • · manual review: niche plumbing for Neovim users, not a standalone product; Neovim-only scope is the honest limit; thin but consistent evidence

Sources

Every fact above was checked against these sources. Where a claim comes from the provider and couldn't be independently verified, the text says so.