Creativity · MCP — client

MCP Neovim Client

The MCP Neovim Client is a Lua plugin that adds MCP support to Neovim. It connects to configured servers over stdio or HTTP, routes tool/resource calls through the editor's UI, and integrates with popular LLM frontends like avante.nvim, CodeCompanion, and Cortex. The result: an LLM inside Neovim that can read the repository, search the web, and modify files — all with explicit user approval.

MCP facts

Kind: client
Ecosystem: anthropic-mcp
Language: Lua
Transports: stdio, http

Capabilities

Connects to configured MCP servers and exposes their tools to LLM plugins
Renders tool call approvals inline in Neovim with diff previews for write operations
Plays well with CodeCompanion.nvim and avante.nvim via adapter APIs

Install

{ 'ravitemer/mcphub.nvim', dependencies = { 'nvim-lua/plenary.nvim' } }

Configuration

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "~/projects"]
    },
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": { "GITHUB_TOKEN": "${GITHUB_TOKEN}" }
    }
  }
}

Frequently asked questions

Does it replace Copilot in Neovim?

No — it's a transport layer. Pair it with an LLM plugin like avante.nvim to get Copilot-style completions plus MCP-driven tool calls.

How does approval work?

The plugin renders each tool call as a floating prompt. Write operations show a diff before applying; read operations usually auto-approve based on a per-server policy.

What MCP servers work well with Neovim?

Filesystem, GitHub, Postgres, and the language-specific ones (Python, TypeScript). Anything that helps understand a codebase.

Sources

Model Context Protocol — accessed 2026-04-20
mcphub.nvim — accessed 2026-04-20
avante.nvim — accessed 2026-04-20