NeoVimMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NVIM_BUFFER_PORT | No | Port for the HTTP bridge (default 4389) | 4389 |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_cursor_contextA | Returns current file, filetype, cursor position, and nearby lines. |
| get_linesA | Returns lines from start to end (0-indexed, end-exclusive). |
| get_selectionA | Returns last visual selection based on '< and '> marks. |
| get_yankA | Returns unnamed register text and register type. |
| get_full_fileA | Returns full current buffer content. |
| get_pathB | Returns the absolute and relative path of the current file. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool retrieves a distinct piece of information: cursor context, line range, selection, yank register, full file, and file path. There is no overlap in purpose.
All tools follow a consistent 'get_' prefix followed by a clear noun describing the fetched data (e.g., get_cursor_context, get_lines). No mixing of styles.
With 6 tools covering essential read operations, the count is reasonable for a focused inspection server, though slightly on the lower side.
The server provides only read operations, lacking any mutation tools like edit, execute commands, or buffer management. This leaves significant gaps for a NeoVim integration.