34 MCP Tools
34 registered tools for terminal control and recorded context.
Availability
Implemented in the stable source; configuration and compatibility limits are described below.
Reviewed against stable v0.5.1. Rust candidate additions are labeled separately. Release status.
The pain this solves
- MCP clients need a defined interface to query sessions and operate terminal tabs.
- An accurate tool count matters because resources and tools are separate MCP methods.
What ships with it
- The stable registry defines 34 tools for telemetry, tabs, runtime observability, and repository context.
- tab_request_control and tab_release_control express user-granted authority over existing tabs.
- Tool availability does not mean unrestricted access to every user tab.
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
The stable v0.5.1 MCP registry contains 34 tool definitions. They cover stored runs and sessions, tab operations, runtime observability and subscriptions, and repository metadata and events.
The telemetry and session tools are run_get, run_list, run_tool_calls, run_transcript, run_tag, run_latest_for_repo, session_list, and session_current. Tab tools include tab_list, tab_create, tab_request_control, tab_release_control, tab_exec, tab_status, tab_wait_ready, tab_send_input, tab_press_key, tab_submit_prompt, tab_close, tab_output, agent_launch, tab_set_cto, and tab_rename.
Runtime tools are chau7_runtime_info, chau7_mcp_session_info, chau7_runtime_events, chau7_timer_inventory, chau7_state_snapshot, chau7_subscribe, and chau7_unsubscribe. Repository tools are repo_get_metadata, repo_set_metadata, repo_frequent_commands, and repo_get_events. Mutating control is scoped: an existing user tab must be explicitly granted to MCP before it can be driven. The separate Require Approval setting applies to new-tab creation and is off by default; command execution follows the separate MCP command-permission mode.
Why it matters
A registered MCP tool surface lets a compatible client query Chau7’s recorded session data and operate on authorized tabs. Tool count describes the registry; it does not mean every tool gives unrestricted access to every user tab.
Frequently asked questions
How many tools are registered?
The stable v0.5.1 toolDefinitions registry contains 34 tools. MCP resources are listed separately and are not included in that count.
Can a client control any open user tab?
No. An MCP-created tab is controlled by MCP. The Require Approval setting controls whether Chau7 asks before creating a new tab (off by default). A request to control an existing user tab always presents a separate explicit consent prompt through tab_request_control; command execution is governed separately by MCP command-permission mode.
Which clients are configured automatically?
The stable auto-registration path handles Claude Code, Cursor, Windsurf, Gemini CLI, and Codex when their configuration prerequisites exist. Other clients may require compatible manual setup.