A
licenseA
qualityA
maintenanceEnables AI clients to interact with Neovim buffers via MCP tools, providing buffer and cursor context.
6
5 npm
ISC
Neovim MCP Server
by laktek
Related Servers
Alternatives to Neovim MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMake 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.23MIT
- FlicenseNot gradedqualityCmaintenanceBridges Claude Code and Claude.ai by exposing project memory files over MCP for shared context across both interfaces.-
- FlicenseNot gradedqualityDmaintenanceEnables LLM-powered code analysis, generation, debugging, and context management through MCP integration with IDEs like Cursor and Claude Desktop.-
- AlicenseNot gradedqualityCmaintenanceAI context management for codebases – enables Claude Code to read, search, and update project documentation via MCP.MIT
- AlicenseNot gradedqualityBmaintenanceMCP 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
TDQS
A3.7/5.0
Scored across 7 tools
Disambiguation4/5
Most tools have distinct purposes, but there is some overlap between 'reload_buffer' and 'reload_all_buffers' that could cause confusion. The descriptions help clarify that 'reload_buffer' targets a specific buffer while 'reload_all_buffers' handles all buffers, but the similar naming might lead to misselection in some contexts.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern using snake_case, such as 'get_buffer_content', 'list_nvim_buffers', and 'update_buffer'. This predictability makes it easy for agents to understand and use the tools without confusion from mixed conventions.
Tool Count5/5
With 7 tools, the server is well-scoped for managing Neovim buffers and files. Each tool serves a clear purpose, such as retrieving, listing, opening, and updating buffers, which aligns well with the domain of Neovim integration without being overly sparse or bloated.
Completeness4/5
The tool set covers core buffer operations like getting, listing, opening, and updating, with good lifecycle coverage. A minor gap is the lack of a tool for closing or deleting buffers, which might be needed for full buffer management, but agents can likely work around this with existing tools.
Maintenance
ActivityInactive
ResponsivenessNo issues