Yes. Chau7 provides an approval gate for MCP actions, tab limits, enable/disable toggle, and MCP-created tab indicators. You control what agents can do.

Local MCP Server

A clean way to
automate your terminal.

Q: Which AI tools work with Chau7's MCP?

Claude Code, Cursor, Windsurf, and Codex all auto-discover Chau7's MCP server on launch. Any MCP-compatible client can connect via the Unix socket.

Q: Do I need to configure anything?

No. Chau7 auto-registers its MCP server in Claude Code, Cursor, Windsurf, and Codex configuration files on every launch. Zero manual setup.

Chau7 ships a local MCP server over Unix socket. 20 tools for tabs, commands, output, and telemetry. Your AI agents use it. Your scripts use it. Nothing leaves your machine.

The plumbing

Local Unix socket. Standard MCP protocol. No network, no cloud, no API keys.

Auto-registration

On every launch, Chau7 writes its socket path into the MCP config of Claude Code, Cursor, Windsurf, and Codex. Your tools find it without you touching a file.

Local Unix socket

The server listens on a filesystem socket. No TCP, no port, no network. Only processes on your Mac can reach it.

Full terminal automation

20 tools give your AI agents, or your own scripts, a clean way to drive Chau7. Open tabs, run commands, read output, query telemetry. A proper API instead of screen scraping.

20 tools. Everything accessible.

Tabs, commands, output, sessions, and telemetry. All available through the standard MCP protocol. All local.

Tab Management (8 tools)

tab_listList all tabs across windows with status, git branch, CTO state

tab_createOpen new tabs with directory & window targeting

tab_execExecute commands with prompt-state checking

tab_statusProcess tree, telemetry run, git branch, CTO state

tab_send_inputRaw input for interactive prompts (no newline appended)

tab_closeClose with optional force flag for running processes

tab_outputLast N lines of scrollback (max 5000, 512KB cap)

tab_set_ctoPer-tab Context Token Optimization override

Telemetry & Analytics (8 tools)

run_getFull telemetry run by UUID

run_listFilter by session, repo, provider, date range, tags

run_tool_callsEvery tool call an AI agent made in a run

run_transcriptComplete conversation turns for replay

run_tagTag runs for organization and filtering

run_latest_for_repoMost recent run per repository path

session_listSessions with run counts, filterable by repo

session_currentCurrently active AI sessions across all tabs

MCP Resources (4 endpoints)

tab://listAll open tabs with metadata

session://listActive AI sessions

run://latestMost recent telemetry run

config://mcpCurrent MCP server configuration

tab_status response

{
  "tab_id": "C1C4AB49-DA22-46F6-831B-FF7CFC2BDDC3",
  "active_app": "Claude",
  "status": "running",
  "git_branch": "main",
  "cto_active": true,
  "is_mcp_controlled": false,
  "processes": [
    { "name": "claude", "pid": 48291, "cpu_percent": 12.3 }
  ],
  "active_run": {
    "provider": "claude",
    "duration_so_far_ms": 184200
  }
}

run_tool_calls response

{
  "run_id": "a3f8c2e1-9b4d-4f6a-8e7c-5d2b1a0f3e9d",
  "tool_calls": [
    {
      "tool": "Read",
      "input": { "file_path": "/src/main.swift" },
      "duration_ms": 45
    },
    {
      "tool": "Edit",
      "input": { "file_path": "/src/main.swift" },
      "duration_ms": 120
    }
  ]
}

Zero-config auto-registration

On every launch, Chau7 registers itself in your AI tools' MCP config files. No manual setup.

Claude Code~/.claude.json

Cursor~/.cursor/mcp.json

Windsurf~/.codeium/windsurf/mcp_config.json

Codex~/.codex/config.toml

You control what agents can do.

The MCP server is local, but that does not mean unguarded. You decide what runs.

If you're wondering why these guardrails exist, imagine what happened before we added them. Actually, don't. We're still recovering.

Approval Gate

MCP tool calls can require explicit user approval before executing. Enable per-tool or globally.

Tab Limits

Set maximum number of MCP-created tabs to prevent runaway agents from spawning unlimited sessions.

Enable / Disable Toggle

Turn MCP server on or off entirely from Settings. When off, the Unix socket is not created.

MCP Tab Indicator

Tabs created by MCP are visually tagged so you always know which tabs an AI agent opened.

Frequently asked questions

What is MCP?

MCP (Model Context Protocol) is an open standard that lets AI agents interact with external tools and data sources. Chau7 implements a local MCP server that makes terminal automation available as 20 tools over a Unix socket. No cloud, no API keys. Learn more about MCP.

Which AI tools work with Chau7's MCP?

Claude Code, Cursor, Windsurf, and Codex auto-discover Chau7's MCP server on launch. Any MCP-compatible client can connect via the Unix socket at the path specified in the config files.

Is MCP access safe?

Yes. Chau7 provides an approval gate for MCP actions, configurable tab limits, a global enable/disable toggle, and visual indicators for MCP-created tabs. You always know what an agent is doing, and you control what it can do.

Does MCP data leave my machine?

No. The MCP server runs on a local Unix socket. Only processes on your Mac can connect to it. There is no network listener, no port, no cloud relay. Tool calls, responses, and telemetry all stay on your filesystem.

Can I use MCP from my own scripts?

Yes. Any MCP-compatible client can connect to the Unix socket. You can also use the JSON-RPC API directly from any language that can talk to a Unix socket. Chau7's MCP is not limited to AI agents: it's a general-purpose terminal automation interface.

Do I need to configure anything?

No. Chau7 auto-registers its MCP server in Claude Code (~/.claude.json), Cursor (~/.cursor/mcp.json), Windsurf (~/.codeium/windsurf/mcp_config.json), and Codex (~/.codex/config.toml) on every launch. Zero manual setup required.

A clean way toautomate your terminal.