overseer-nvim-mcp
Related Servers
Alternatives to overseer-nvim-mcp
- AlicenseAqualityBmaintenanceEnables AI assistants to control running Neovim sessions via RPC socket, supporting command execution, state inspection, and LSP actions. Automatically discovers Neovim instances and supports multi-instance management on Linux and macOS.1823 PyPI68MIT
- AlicenseAqualityDmaintenanceMake Neovim feel like Cursor. This MCP server gives an agent full control over the Neovim session it is running inside, including buffers, windows, diagnostics, LSP language intelligence, and terminals.23MIT
Related Servers
- AlicenseBqualityDmaintenanceAn MCP server that enables AI agents to control Neovim instances running in tmux sessions.12MIT
- AlicenseAqualityFmaintenanceMCP server for running external coding agents as background tasks inside Claude Code. Supports multiple backends including Codex, Grok, GLM, DeepSeek, and more.7MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that bridges CLI coding agents like Claude Code, Codex, opencode, and Antigravity into any MCP client, enabling synchronous and asynchronous task execution, follow-up input, and a structured code review tool.24 npm3MIT
- AlicenseAqualityDmaintenanceAn MCP server that lets AI agents see, act on, and verify the rendered Neovim UI, like a Playwright for Neovim. It provides tools to launch/attach to Neovim, observe the screen, send input, and wait for conditions.8MIT
- AlicenseAqualityDmaintenanceMCP server that launches and supervises coding-CLI subagents (claude, opencode) in detached tmux windows, collapsing the ceremony of starting a TUI coding assistant into a single tool call.5MIT
- AlicenseNot gradedqualityAmaintenanceA standalone MCP server that lets AI agents such as Claude Code, Gemini CLI, Codex, and Kimi CLI read, type into, and send messages to each other's terminal panes, enabling coordinated multi-agent workflows without manual copy-pasting. It talks directly to tmux, so no external dependencies or framework rewrites are needed.49 npmMIT
TDQS
Scored across 7 tools
Each tool maps to a distinct lifecycle action or listing operation, and the descriptions go out of their way to spell out the differences (dispose vs stop vs restart, with the force/ownership rules repeated). The only real overlap is the stop/dispose/restart trio, which an agent could still confuse at a glance, but the descriptions resolve it.
All tools share a consistent `overseer_` prefix with lowercase snake_case verbs, and the two listing tools follow a clean `list_<noun>` pattern. Single-object tools use bare verbs (run, stop, tail, dispose) rather than verb_noun, a minor deviation but still readable and predictable.
Seven tools is tightly scoped to the domain: start, observe, and control long-running tasks plus discover templates. Every tool earns its place with no redundant or throwaway entries.
The surface covers the full task lifecycle (run, list, tail, wait-for-output, restart, stop, dispose) plus template discovery, with tail's status line removing the need for a separate status tool. The notable gap is sending input to an interactive task's stdin, and there is no way to create or persist a template, though the latter is deliberately delegated to on-disk config.