Neovim MCP Server
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
Using Nix
From Source
&&
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
2. Configure claude or other MCP clients
# Auto-connect to current project Neovim instances (recommended)
# Analyze diagnostics in current Neovim instance
Documentation
For detailed information, see:
- Usage Guide: Detailed usage workflows, CLI options, and transport modes
- Tools Reference: Complete reference for all 26 MCP tools
- Resources: MCP resources and URI schemes
- Development: Development setup, testing, and contributing
Development
Basic development setup:
# Enter development shell
# Run tests
# Build and run
See Development Guide for complete setup instructions, testing procedures, and contribution guidelines.