Neovim MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_nvim_buffersB | List all open buffers in Neovim instances running in the current directory |
| get_current_bufferB | Get the currently active buffer in Neovim |
| get_buffer_contentB | Get the content of a specific buffer by path |
| update_bufferB | Update the content of a buffer in Neovim. Changes appear immediately in the editor. |
| reload_bufferA | Reload a buffer from disk. Use this after editing a file externally to refresh the buffer in Neovim. |
| reload_all_buffersA | Check all open buffers and reload any that have changed on disk. Use this after editing files externally. |
| open_fileA | Open a file in Neovim. Use this to open newly created files or existing files for editing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Current Neovim Buffer | The currently active buffer in Neovim |
| Open Neovim Buffers | List of all open buffers in Neovim instances running in current directory |
TDQS
Scored across 7 tools
Most tools have distinct purposes, but there is some overlap between 'reload_buffer' and 'reload_all_buffers' that could cause confusion. The descriptions help clarify that 'reload_buffer' targets a specific buffer while 'reload_all_buffers' handles all buffers, but the similar naming might lead to misselection in some contexts.
All tool names follow a consistent verb_noun pattern using snake_case, such as 'get_buffer_content', 'list_nvim_buffers', and 'update_buffer'. This predictability makes it easy for agents to understand and use the tools without confusion from mixed conventions.
With 7 tools, the server is well-scoped for managing Neovim buffers and files. Each tool serves a clear purpose, such as retrieving, listing, opening, and updating buffers, which aligns well with the domain of Neovim integration without being overly sparse or bloated.
The tool set covers core buffer operations like getting, listing, opening, and updating, with good lifecycle coverage. A minor gap is the lack of a tool for closing or deleting buffers, which might be needed for full buffer management, but agents can likely work around this with existing tools.