Skip to main content
Glama
paulburgess1357

nvim-mcp

by paulburgess1357
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to nvim-mcp

Related Servers

  • nvim-editor-mcp

    gierdo
    A
    license
    Not graded
    quality
    B
    maintenance
    MCP server bridging tool calls to Neovim editor actions via RPC. Enables AI agents to open files, run Lua, manage quickfix lists, fetch diagnostics, and send notifications.
    GPL 2.0

  • nvim-mcp

    Shooooooooo
    A
    license
    A
    quality
    D
    maintenance
    Make Neovim feel like Cursor. This MCP server gives an agent full control over the Neovim session it is running inside, including buffers, windows, diagnostics, LSP language intelligence, and terminals.
    23
    MIT

  • nvim-ui-mcp

    kjoonha
    A
    license
    A
    quality
    B
    maintenance
    An MCP server that lets AI agents see, act on, and verify the rendered Neovim UI, like a Playwright for Neovim. It provides tools to launch/attach to Neovim, observe the screen, send input, and wait for conditions.
    8
    MIT

  • neovim-mcp

    Simonoob
    F
    license
    A
    quality
    D
    maintenance
    Enables AI agents to navigate code using Neovim's LSP and Treesitter features, and read/write the quickfix list.
    14
    -
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A4.6/5.0

Scored across 18 tools

Disambiguation5/5

Each tool targets a distinct resource+action, and descriptions explicitly cross-reference siblings (get_state vs get_state_brief, read_buf_range vs read_full_buf, send_command vs send_keys vs send_to_terminal). The singular/plural annotation pairs (highlight_range/highlight_ranges, add_virtual_text/add_virtual_texts) are clearly differentiated by scope. No meaningful overlap remains.

Naming Consistency5/5

Consistent snake_case verb_noun (or verb_noun_qualifier) pattern throughout: get_state_brief, read_buf_range, send_command, find_and_replace_buf, clear_virtual_texts. The lone bare 'connect' is a natural exception that breaks no pattern. No mixing of conventions.

Tool Count4/5

18 tools is slightly heavy but each earns its place by covering a genuinely broad editor surface (state, reads, edits, commands, terminals, diagnostics, annotations). The sing/plural annotation variants could arguably be collapsed, but the scoping is reasonable for a full Neovim integration.

Completeness4/5

Strong coverage of state inspection, buffer reads/writes, ex/keystroke/terminal input, diagnostics, and annotation workflows with cleanup tools. Minor gaps exist (no undo/redo, search/navigate, or buffer-close tools), but agents can reach these via send_command.

Maintenance

ActivityMaintained
ResponsivenessSlow

Resources