Skip to main content
Glama
Simonoob

neovim-mcp

by Simonoob
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to neovim-mcp

No user-submitted related servers found.

    Related Servers

    • lsp-mcp-server

      garretpremo
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes type-aware code navigation and fast file search to AI agents via language servers, enabling definitions, references, symbols, and file lookup without reading entire codebases.
      3,050 npm
      MIT

    • tree-lens

      zhaoxingxing06
      A
      license
      A
      quality
      A
      maintenance
      Enables LLM agents to navigate source code structurally via tree-sitter over MCP, offering outline-based reading, AST pattern search, workspace-scale symbol indexing, call graph analysis, and built-in security audit queries.
      15
      MIT

    • CodeAtlas

      5hihan
      A
      license
      C
      quality
      B
      maintenance
      Enables coding agents to navigate large codebases through a tree-sitter symbol graph, retrieve compact path:line-annotated context, and run a SNIPE fix loop with live dashboard updates on every save.
      38
      MIT

    • nvim-mcp

      paulburgess1357
      A
      license
      A
      quality
      A
      maintenance
      Enables AI assistants to control running Neovim sessions via RPC socket, supporting command execution, state inspection, and LSP actions. Automatically discovers Neovim instances and supports multi-instance management on Linux and macOS.
      18
      42 PyPI
      63
      MIT
    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.6/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool targets a distinct action: LSP diagnostics, symbols, references, definitions, implementations, hover info, and workspace symbols are all clearly separate. AST context, quickfix management, LSP client control, and health check are also unique, so no overlap.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern in snake_case (e.g., get_diagnostics, goto_definition). However, 'workspace_symbols' lacks a verb prefix unlike its counterpart 'get_document_symbols', and 'vim_health' could be more descriptive. Overall, the naming is mostly consistent.

    Tool Count5/5

    14 tools is well-scoped for a Neovim MCP server covering LSP interactions, AST queries, quickfix operations, and server health. Each tool serves a clear purpose without unnecessary bloat or deficiency.

    Completeness4/5

    The toolset thoroughly covers code navigation and LSP features (symbols, references, definitions, diagnostics, hover). Missing features like code actions or formatting, but these are likely out of scope for a read-only assistant. Minor gap: no way to get buffer content or edit files.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources