Neovim MCP Server

Created By
bigcodegena year ago
Control Neovim using Model Context Protocol (MCP) and the official neovim/node-client JavaScript library
Overview

What is Neovim MCP Server?

Neovim MCP Server is a proof of concept integration that allows users to control Neovim using the Model Context Protocol (MCP) and the official neovim/node-client JavaScript library. It creates a lightweight code assistance layer leveraging Vim's native text editing commands.

How to use Neovim MCP Server?

To use the Neovim MCP Server, you need to expose your Neovim instance with the --listen /tmp/nvim option when starting Neovim. Then, configure your claude_desktop_config.json to include the MCP server command.

Key features of Neovim MCP Server?

  • Connects to your Neovim instance for real-time interaction.
  • Views the current buffer and gets cursor location, mode, and file name.
  • Runs Vim commands and makes edits using insert or replacement modes.
  • Provides various API resources for managing Neovim sessions and buffers.

Use cases of Neovim MCP Server?

  1. Assisting in code editing and navigation within Neovim.
  2. Automating repetitive tasks in the Neovim environment.
  3. Enhancing coding efficiency with real-time code assistance.

FAQ from Neovim MCP Server?

  • Is this server stable for production use?

No, this is a quick proof of concept and may not interact well with custom Neovim configurations.

  • What are the limitations?

Error handling could be better, and sometimes commands may not be interpreted correctly by Claude.

  • Is there a license for this project?

Yes, it is licensed under the MIT License, allowing free use, modification, and distribution.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
bigcodegen
Star
124
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago