20 MCP Tools
20 MCP tools. Full terminal control. Your AI agent just got its own command center.
Questions this answers
- How do I let AI agents control my terminal?
- Is there a terminal with a built-in MCP server?
- How can Claude Code create and manage terminal tabs programmatically?
- What MCP tools are available for terminal automation?
- How do I give Cursor or Windsurf access to my terminal?
How it works
Chau7 ships a full MCP server that exposes 20 tools organized around terminal primitives: tab lifecycle (create, close, list, status), command execution (exec, send raw input), output retrieval (scrollback buffer capture), and telemetry (run tracking, session listing, transcripts). Each tool maps to a single, well-defined operation so agents can compose complex workflows from simple building blocks.
The tools are designed for real-world agent patterns. tab_exec runs a command and waits for completion, returning structured output. tab_send_input handles interactive prompts by sending raw keystrokes. tab_output retrieves the last N lines of scrollback, letting agents read command results without parsing terminal escape sequences. Status tools report process state, working directory, and active child processes so agents always know what is happening.
Telemetry tools (run_get, run_list, run_transcript, run_tool_calls) give agents access to their own execution history. An agent can review what it did in previous runs, inspect tool call patterns, and use session data to inform current decisions. This creates a feedback loop where agents learn from their own terminal interactions.
Why it matters
Without Chau7, AI agents are limited to injecting text into a single terminal session and hoping for the best. With 20 purpose-built MCP tools, agents can create tabs, execute commands, read output, inspect processes, track sessions, and manage their own workspace. It is the difference between shouting into a room and having a proper conversation.
Frequently asked questions
Which AI clients work with Chau7's MCP tools?
Any MCP-compatible client works, including Claude Code (Claude CLI), Cursor, Windsurf, and Codex. Chau7 auto-registers its server configuration in each client's config file on launch, so there is no manual setup required.
Do the MCP tools require network access?
No. The MCP server communicates over a local Unix socket with no network exposure. All tool calls stay on your machine, and no authentication is needed because the socket is only accessible to your user account.
Can MCP tools run destructive commands?
Yes, the tools execute whatever commands you send, just like typing in a terminal. Chau7 provides tab limits to prevent runaway tab creation, but command-level safety is the responsibility of the AI agent and its configuration.