Lets AI inspect and modify code symbols through Neovim LSP.
Based on the provided materials, this MCP tool appears to operate mainly locally through Neovim/LSP for code analysis and symbol-level modifications, with no declared secrets or remote endpoints, so overall risk is relatively low. Attention is still warranted because it can execute locally and modify code/files, and while it is open source and auditable, community adoption is minimal and maintenance status is unknown.
The materials explicitly state that no keys or environment variables are required, and there is no indication of API keys, tokens, or other sensitive credentials; based on the available information, credential exposure or abuse risk appears low.
No remote endpoint is declared, and the description only states that it provides symbol tools through Neovim's built-in LSP locally; there is no factual indication that user data is exfiltrated to third-party services.
The system flags this tool as having executes-code capability, and its stated functions include code analysis, renaming, and body replacement via Neovim/LSP; this means it can trigger local developer tooling/processes and affect code, which is a normal but noteworthy capability for this class of tool.
Its declared capabilities include symbol lookup, renaming, and body replacement, which implies access to and modification of code within the current Neovim project; based on the materials, this is local code/file access consistent with the stated functionality, with no evidence of excessive permissions.
The project is an Apache 2.0 open-source repository, so the source is in principle auditable, which is a clear risk-reducing factor; however, it comes from a third-party registry, has only 0 stars, and an unknown maintenance status, so its maturity and ongoing maintenance warrant caution.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "nvim-mcp-server" yet — see the docs or source repo.
Use nvim-mcp-server to locate the definition of `processOrder`, list all references in the project, and summarize its inputs, outputs, and call chain.
Provides the function definition, a list of references, and a brief analysis of its role and call relationships.
Using nvim-mcp-server, rename the symbol `usrCfg` to `userConfig` and review all affected files to ensure there are no obvious naming conflicts after the change.
Returns the rename changes, affected files, and any potential conflicts or follow-up checks.
Use nvim-mcp-server to find the `validateInput` function and replace its body with a clearer parameter validation implementation while keeping the original function signature unchanged.
Generates the updated function implementation and explains the replacement and possible behavioral impact.
Enable AI code navigation and editing across languages through LSP-backed tools.
Connect VSCode to MCP so AI can inspect code context in real time.
Quickly search large codebases, find symbols, list files, and read code.
Connect to Jupyter via MCP to run code and explore data interactively.
Build, debug, and manage software tasks with natural language across LLMs.
Index local repositories for semantic search and structured code understanding.