Skip to main content
Glama
Aetherall

@aetherall/mcp-nvim-tmux

by Aetherall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

Related Servers

Alternatives to @aetherall/mcp-nvim-tmux

No user-submitted related servers found.

    Related Servers

    • nvim-mcp

      Shooooooooo
      A
      license
      A
      quality
      B
      maintenance
      Make 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.
      23
      MIT

    • nvim-ui-mcp

      kjoonha
      A
      license
      A
      quality
      B
      maintenance
      An 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.
      8
      MIT

    • mcp-tmux

      laszlopere
      A
      license
      B
      quality
      C
      maintenance
      A comprehensive MCP server for driving tmux sessions, windows, panes, sending keystrokes, and reading pane output locally or over SSH, enabling real-time collaborative pairing with AI.
      71
      4
      MIT

    • tmux-mcp

      fr1sk
      A
      license
      A
      quality
      D
      maintenance
      MCP server that gives AI assistants full visibility into your tmux sessions — browse sessions, windows, and panes, read terminal output, and send commands.
      14
      51 npm
      1
      MIT

    • neovim-use-mcp

      santanusinha
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that edits files through a real Neovim instance, giving agents access to LSP diagnostics, formatting, code actions, and plugin commands.
      18
      160 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 12 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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).

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources