Skip to main content
Glama
santanusinha

neovim-use-mcp

by santanusinha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to neovim-use-mcp

No user-submitted related servers found.

    Related Servers

    • 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

    • lsp-mcp

      afriemann
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that exposes LSP-backed code navigation and editing tools to LLM agents using a single global config file to route file extensions to language servers.
      MIT

    • 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-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

    • Vigentic MCP

      munozu
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that utilizes a headless Neovim instance as an IDE kernel for advanced code editing and navigation. It provides tools for LSP-powered diagnostics, buffer management, and structural edits using Tree-sitter.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools target a distinct operation: reading, editing, LSP queries, diagnostics, formatting, and plugin dispatch are clearly separated. The only mild ambiguity is among nvim_edit_lines, nvim_edit_text, and nvim_insert_lines, though their descriptions explain when to use each.

    Naming Consistency4/5

    All tools share the nvim_ prefix and use snake_case, which makes the set feel cohesive. However, some names are verb_noun (nvim_read_file, nvim_edit_lines) while others are noun-oriented (nvim_diagnostics, nvim_command, nvim_document_symbols), creating a minor style inconsistency.

    Tool Count4/5

    18 tools is slightly above the typical 3-15 range, but the count is justified by the server's broad scope covering file editing, buffer management, LSP navigation, diagnostics, formatting, and plugin access. No tool feels like filler, so the set is reasonable despite being a bit large.

    Completeness4/5

    The tool surface covers core workflows well: reading and editing files, formatting, saving, diagnostics, symbols, references, hover, rename, and code actions are all present. Minor gaps exist, such as no explicit buffer-close or file-create tool and no LSP implementation/type-definition navigation, but agents can work around these via nvim_command or nvim_exec_lua.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources