MCP Neovim Server MCP Server

An MCP server for neovim

Local serverstdio

What is the MCP Neovim Server MCP server?

Most developer tooling work still happens through a UI a human drives. MCP Neovim Server MCP server moves it into the conversation instead. An MCP server for neovim.

The short version

Connect Claude Desktop (or any Model Context Protocol client) to Neovim using MCP and the official neovim/node-client JavaScript library. This server leverages Vim's native text editing commands and workflows, which Claude already understands, to create a lightweight code or general purpose AI text assistance layer.

  • Connects to your nvim instance if you expose a socket file, for example --listen /tmp/nvim, when starting nvim
  • Views your current buffers and manages buffer switching
  • Gets cursor location, mode, file name, marks, registers, and visual selections
  • Runs vim commands and optionally shell commands through vim
  • Can make edits using insert, replace, or replaceAll modes
  • Search and replace functionality with regex support

The tools it exposes

The server publishes 14 tools. What each one is for:

  • vim_buffer — Get buffer contents with line numbers (supports filename parameter)
  • vim_command — Send a command to VIM for navigation, spot editing, and line deletion
  • vim_status — Get comprehensive Neovim status
  • vim_edit — Edit lines using insert, replace, or replaceAll modes
  • insert — insert lines at startLine
  • replace — replace lines starting at startLine
  • replaceAll — replace entire buffer contents
  • vim_window — Manipulate Neovim windows (split, vsplit, close, navigate)
  • vim_mark — Set named marks at specific positions
  • vim_register — Set content of registers
  • vim_visual — Create visual mode selections
  • vim_macro — Record, stop, and play Vim macros

What it needs from you

Configuration is passed through the environment: ALLOW_SHELL_COMMANDS, NVIM_SOCKET_PATH. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Neovim Server's toolset — vim_buffer, vim_command, vim_status and 11 more — is a fair guide to whether it matches your workflow. It is maintained by bigcodegen; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP Neovim Server.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
vim_bufferGet buffer contents with line numbers (supports filename parameter)
vim_commandSend a command to VIM for navigation, spot editing, and line deletion
vim_statusGet comprehensive Neovim status
vim_editEdit lines using insert, replace, or replaceAll modes
insertinsert lines at startLine
replacereplace lines starting at startLine
replaceAllreplace entire buffer contents
vim_windowManipulate Neovim windows (split, vsplit, close, navigate)
vim_markSet named marks at specific positions
vim_registerSet content of registers
vim_visualCreate visual mode selections
vim_macroRecord, stop, and play Vim macros
vim_tabComplete tab management
vim_foldCode folding operations

How to install the MCP Neovim Server MCP server

{
  "mcpServers": {
    "MCP Neovim Server": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-neovim-server"
      ],
      "env": {
        "ALLOW_SHELL_COMMANDS": "true",
        "NVIM_SOCKET_PATH": "/tmp/nvim"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
ALLOW_SHELL_COMMANDSConfiguration value read at startup.Optional
NVIM_SOCKET_PATHFilesystem location the server is allowed to use.Optional

Example prompts to try

  • Use MCP Neovim Server to vim buffer.
  • Use MCP Neovim Server to vim command.
  • Use MCP Neovim Server to vim status.

Frequently asked questions

It connects MCP Neovim Server to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (vim_buffer, vim_command, vim_status, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Neovim Server directly.