neovim-mcp
Related Servers
Alternatives to neovim-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceExposes 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.1,254 npmMIT
- AlicenseAqualityAmaintenanceEnables 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.15MIT
- AlicenseCqualityBmaintenanceEnables 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.38MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents and AI IDEs to pull real-time LSP diagnostics, type/hover/signature information, and code navigation from a running editor, replacing slow tsc and eslint runs. Also supports workspace-wide symbol renaming, reference lookup with usage context, opening files, and listing open editor windows.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to semantically navigate codebases via an AST index, supporting symbol search, usage lookup, module exploration, and dependency analysis.MIT
- AlicenseAqualityAmaintenanceEnables AI clients to interact with Neovim buffers via MCP tools, providing buffer and cursor context.61 npmISC
TDQS
Scored across 14 tools
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.
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.
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.
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.