@aetherall/mcp-nvim-tmux
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_NVIM_TMUX_CMD | No | AI command template for analysis (default: ollama run $MODEL) | ollama run $MODEL |
| MCP_NVIM_TMUX_MODEL | No | Default model for all AI operations | |
| NVIMRUN_PROMPTS_DIR | No | Directory for prompt templates | |
| MCP_NVIM_TMUX_ANALYZE_MODEL | No | Model for analysis operations | |
| MCP_NVIM_TMUX_SUMMARIZE_MODEL | No | Model for summarization |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| nvim_startC | Start a new Neovim session in tmux |
| nvim_stopC | Stop a Neovim session |
| nvim_keysB | Send keystrokes to Neovim. Use for special keys and navigation. Examples: ['i'] to enter insert mode, ['Escape'] to exit, ['Enter'] for newline, ['Tab'] for tab, ['C-w', 'l'] for window navigation, ['d', 'd'] to delete line |
| nvim_cmdC | Execute a Vim command |
| nvim_source_luaC | Source a Lua file in Neovim using :luafile command |
| nvim_screenC | Capture the current screen content |
| nvim_editC | Open a file at a specific line |
| nvim_typeA | Type literal text without any special key interpretation. Perfect for code, URLs, or text with special characters. All characters including $, !, quotes, etc. are typed exactly as provided. Example: 'echo $HOME' types literally without shell expansion |
| nvim_recordingsC | List available asciinema recordings |
| nvim_playC | Play an asciinema recording |
| nvim_catB | Display asciinema recording in AI-readable format with input/output timeline |
| nvim_analyzeB | Analyze a Neovim recording using AI to explain what happened |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools have clearly distinct purposes: session control, text/keystroke input, Vim commands, screen capture, and recording operations. Some potential overlap exists among recording tools (play/cat/analyze/list) and between nvim_cmd, nvim_edit, and nvim_source_lua, but descriptions help distinguish them.
All tool names use a consistent nvim_ prefix and snake_case. There are minor deviations from a strict verb_noun pattern, since several names are noun/resource-oriented (nvim_screen, nvim_keys, nvim_cmd, nvim_recordings).
The server provides 12 tools, which is within the well-scoped 3-15 range. Each tool appears to cover a distinct facet of Neovim/tmux control and recording workflow without excessive redundancy.
The surface covers core Neovim lifecycle and interaction: start/stop, typing, keystrokes, commands, screen capture, and recording playback/analysis. Minor gaps include no explicit save/quit/buffer-management or tmux pane/window operations, though nvim_cmd can compensate for some of these.