Skip to main content
Glama
Shooooooooo

nvim-mcp

by Shooooooooo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to nvim-mcp

No user-submitted related servers found.

    Related Servers

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

      santanusinha
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that edits files through a real Neovim instance, giving agents access to LSP diagnostics, formatting, code actions, and plugin commands.
      18
      160 npm
      MIT

    • overseer-nvim-mcp

      impossiblecode
      A
      license
      A
      quality
      A
      maintenance
      MCP server for overseer.nvim — gives any MCP-capable coding agent running inside Neovim (Claude Code, Codex, Gemini CLI, opencode) the same visibility and control over tasks the user has: list, run, tail, restart, stop. Agent-started dev servers land in the user's own task list instead of becoming invisible orphaned processes.
      7
      32 npm
      MIT

    • cursor-mcp-server

      bbarney7
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server wrapping the Cursor CLI agent, enabling Claude Code and other MCP clients to delegate tasks to Cursor's AI agent for file writing, bash commands, and codebase queries.
      -

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

    A3.9/5.0

    Scored across 23 tools

    Disambiguation5/5

    Each tool targets a distinct area: LSP operations, buffer manipulation, terminal control, and general commands. Even overlapping tools like nvim_command and nvim_exec_lua are clearly differentiated by their descriptions (Ex commands vs. Lua expressions). No two tools appear to do the same thing.

    Naming Consistency4/5

    All tools share the nvim_ prefix and use lowercase with underscores, making them predictable. However, there is a mix of verb-first (nvim_read_buffer, nvim_open_file) and noun-first (nvim_terminal_send, nvim_lsp_clients) patterns, which is slightly inconsistent but still readable.

    Tool Count3/5

    At 23 tools, this is on the heavier side but appropriate for the broad scope of controlling a Neovim instance. The tools are not redundant; each covers a distinct capability. The count feels reasonable for the complexity of the domain, though it borders on being overwhelming.

    Completeness4/5

    The surface is quite comprehensive: LSP operations, buffer I/O, terminal management, and general command execution are all covered. Minor gaps exist, such as lack of buffer deletion or window creation tools, but the included nvim_exec_lua tool can fill these gaps, and the core workflows are well covered.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources