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

    • squiggles

      carldaws
      A
      license
      A
      quality
      A
      maintenance
      MCP server that lets your coding agent see the squiggles — LSP diagnostics, navigation, refactoring, and each server's custom superpowers
      21
      48 npm
      6
      MIT
    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.2/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct responsibility: LSP lookups (hover, definition, references), mutations (rename, edit, format, code actions), file I/O (read, open), and an escape hatch (exec lua). Even the similar-looking open vs read tools differ clearly in purpose: one returns buffer metadata, the other returns file content.

    Naming Consistency4/5

    All tools share the consistent nvim_ prefix and most use a verb_noun pattern like nvim_read_file and nvim_rename_symbol. Minor deviations like nvim_references and nvim_code_actions being noun phrases, plus bare-verb tools like nvim_format and nvim_hover, keep this from being a perfect 5.

    Tool Count5/5

    10 tools is a well-scoped set for a Neovim-powered editing and LSP server. Each tool covers a meaningful operation, and there is no obvious redundancy or bloat.

    Completeness4/5

    The core workflows are well covered: read, open, edit, format, rename, reference lookup, definition lookup, hover info, and code actions. Minor gaps exist around secondary LSP features like a dedicated diagnostics-only tool, document symbols, or explicit file create/delete operations, but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources