$ loading_
Let AI navigate, inspect, and edit code through Neovim tooling.
The available materials indicate this MCP tool primarily operates locally with Neovim/LSP/Treesitter, requires no secrets, and declares no remote endpoints, with no clear high-risk red flags. The main cautions are its local code-execution capability and a relatively weak trust profile despite being open source.
The materials explicitly state that no keys or environment variables are required, and there is no evidence of API tokens, account credentials, or other sensitive authentication data being collected or transmitted.
No remote endpoint is declared, and the description does not mention sending code or user data to external services; based on the available materials, no explicit network egress is evident.
The system flags this tool as executes-code, indicating it can execute code locally or invoke local editor-related processes. This is a normal MCP capability but warrants limiting the runtime environment and invocation scope.
The description says it uses Neovim's LSP and Treesitter to navigate code and can read/write the quickfix list, implying access to current project code context and editor state. There is no evidence of overbroad access beyond the stated function, but it still involves local code data access.
The source is a third-party registry, but there is a public GitHub repository available for audit, which is a positive open-source signal. However, the license is unspecified, community adoption is 0 stars, and maintenance status is unknown, so supply-chain trust is only moderate and source review is advisable before use.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "neovim-mcp" yet — see the docs or source repo.
Use neovim-mcp to find the definition of processOrder, all references, and its upstream/downstream call relationships in the current project, then summarize the key call chain.
A summary with the function definition location, reference list, and clear call-chain analysis.
Use neovim-mcp to read TypeScript errors from the quickfix list, fix them file by file, and explain the reason for each change.
Code edits with fixes applied, a list of remaining errors, and explanations for each fix.
Use neovim-mcp and Treesitter to find all code that manipulates SQL strings directly and refactor it to a shared query wrapper function.
Matched code locations, the refactored changes, and an explanation of the shared wrapper approach.
Let AI clients access Neovim buffer and cursor context via MCP.
Lets AI inspect and modify code symbols through Neovim LSP.
Enable AI code navigation and editing across languages through LSP-backed tools.
Control Neovim in tmux so AI can automate editing and development tasks.
Connect VSCode to MCP so AI can inspect code context in real time.
Control a running Emacs via MCP for editing and status checks.