nvim-mcp

mcp
Guvenlik Denetimi
Basarisiz
Health Gecti
  • License — License: Apache-2.0
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Community trust — 47 GitHub stars
Code Basarisiz
  • rm -rf — Recursive force deletion command in scripts/run-cov.sh
Permissions Gecti
  • Permissions — No dangerous permissions requested
Purpose
This is a Model Context Protocol (MCP) server that allows AI assistants to interact directly with Neovim instances. It enables AI models to read diagnostic data, manage files, and apply LSP-driven code actions within the editor.

Security Assessment
Overall Risk: Low
The tool inherently accesses local files and editor contents to function properly, meaning your code will be exposed to the connected AI model. It does not request inherently dangerous system permissions. A static code scan caught a `rm -rf` command in the repository, but this is safely isolated inside a developer testing script (`scripts/run-cov.sh`) and poses no threat to end-users. There are no hardcoded secrets, and the Rust codebase minimizes the risk of memory-safety vulnerabilities.

Quality Assessment
The project is in active development, having received updates as recently as today. It is legally clear for integration, distributed under the permissive Apache-2.0 license. While the community is relatively small (around 47 GitHub stars), the repository is professionally maintained. It includes comprehensive documentation, detailed tool references, and automated CI/CD pipelines, signaling a high standard of code quality and reliability.

Verdict
Safe to use.
SUMMARY

A Model Context Protocol (MCP) server that provides seamless integration with Neovim instances, enabling AI assistants to interact with your editor through connections and access diagnostic information via structured resources.

README.md

Neovim MCP Server

codecov
GitHub Actions Workflow Status

A Model Context Protocol (MCP) server that provides seamless integration with
Neovim instances, enabling AI assistants to interact with your editor through
connections and access diagnostic information via structured resources.
Supports both stdio and HTTP server transport modes for different integration
scenarios.

Features

  • Multi-Connection Support: Manage multiple concurrent Neovim instances
  • LSP Integration: Complete LSP workflow with code actions, hover, and diagnostics
  • Universal Document Identifier: Work with files by buffer ID, relative path,
    or absolute path
  • MCP Resources: Structured diagnostic data via connection-aware URI schemes
  • Multi-Transport Support: Both stdio and HTTP server transport modes
  • Dynamic Tool System ⚠️ (Experimental): User-extensible custom tools
  • Plugin Integration: Automatic setup through Neovim plugin

Installation

Use Cargo install from crates.io

cargo install nvim-mcp

Using Nix

nix profile install github:linw1995/nvim-mcp#nvim-mcp

From Source

git clone https://github.com/linw1995/nvim-mcp.git && cd nvim-mcp
cargo install --path .

Usage Cases Collection


  • LSP Hover Translation (From #85)
  • Diagnostic Analysis and Code Fixes (From #10)
  • Smart Context Retrieval (From #86)
  • And more in Discussions

Quick Start

1. Setup Neovim Integration

With a plugin manager like lazy.nvim:

return {
    "linw1995/nvim-mcp",
    build = "cargo install --path .",
    opts = {},
}

2. Configure claude or other MCP clients

# Auto-connect to current project Neovim instances (recommended)
claude mcp add -s local nvim -- nvim-mcp --log-file . \
  --log-level debug --connect auto

# Analyze diagnostics in current Neovim instance
claude "analyze @nvim:nvim-diagnostics://"

Documentation

For detailed information, see:

Development

Basic development setup:

# Enter development shell
nix develop .

# Run tests
cargo test -- --show-output

# Build and run
cargo run -- --connect auto

See Development Guide for complete setup instructions,
testing procedures, and contribution guidelines.

Yorumlar (0)

Sonuc bulunamadi