MCP Tuikit MCP Server

A [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) server that enables AI agents (Claude Code, Cursor, Windsurf, OpenCode) to launch

Local serverstdio

What is the MCP Tuikit MCP server?

If you already use MCP Tuikit, the mcp tuikit mcp server is the piece that lets your assistant work with it directly. A Model Context Protocol (MCP) server that enables AI agents (Claude Code, Cursor, Windsurf, OpenCode) to launch, interact with, and observe any terminal application in isolated sessions. mcp-tuikit.

What the server does

  • Isolated Sessions: — Each session runs in an isolated tmux environment. AI interactions do not leak into or disrupt your host terminal
  • Headless & Visual: — Capture accurate textual screen state and visual PNG screenshots of running TUI applications, even in headless CI environments like Xvfb, Sway, or kwin
  • Flow Execution Engine: — Execute pre-defined flows (YAML) against terminal instances. Great for integration testing or guiding autonomous agent tasks
  • Cross-Platform: — Built to support macOS, Linux, and Windows natively. Works with standard terminals (Terminal.app, iTerm2, Gnome Terminal, Windows Terminal) and modern GPU-accelerated emulators (Alacritty, WezTerm, Ghostty, Kitty)

Installation

@dragoscirjan/mcp-tuikit on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • terminal — //session/{id}/screen.txt?maxLines={limit}: Read the raw plaintext buffer of the active terminal session
  • create_session — command, cols?, rows?
  • close_session — session_id
  • create_snapshot — session_id, format (txt/png/both), intent?
  • send_keys — session_id, keys, submit? (bool)
  • wait_for_text — session_id, pattern, timeout_ms?
  • run_flow — yaml_path?, yaml_string?, cols?, rows?
  • list_sessions(none)
  • check_system_dependencies(none)

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch MCP Tuikit.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP Tuikit's toolset — terminal, create_session, close_session and 6 more — is a fair guide to whether it matches your workflow. It is maintained by dragoscirjan; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Available tools

ToolWhat it does
terminal//session/{id}/screen.txt?maxLines={limit}: Read the raw plaintext buffer of the active terminal session.
create_sessioncommand, cols?, rows?
close_sessionsession_id
create_snapshotsession_id, format (txt/png/both), intent?
send_keyssession_id, keys, submit? (bool)
wait_for_textsession_id, pattern, timeout_ms?
run_flowyaml_path?, yaml_string?, cols?, rows?
list_sessions_(none)_
check_system_dependencies_(none)_

How to install the MCP Tuikit MCP server

{
  "mcpServers": {
    "mcp-tuikit": {
      "command": "npx",
      "args": ["-y", "@dragoscirjan/mcp-tuikit"]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use MCP Tuikit to terminal.
  • Use MCP Tuikit to create session.
  • Use MCP Tuikit to close session.

Frequently asked questions

It connects MCP Tuikit to MCP-compatible AI assistants such as Claude and Cursor, exposing 9 tools (terminal, create_session, close_session, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with MCP Tuikit directly.