Skip to content
forktty_
MCP

A local MCP bridge for visible terminal automation.

ForkTTY's MCP server maps agent tools to the same owner-only socket API used by the CLI. Agents can inspect context, panes, teams, workflows, and bounded terminal tails without leaving the local desktop boundary.

Quick start

Register the local stdio bridge, confirm the running socket capabilities, then take a compact snapshot before using mutating tools.

Preview MCP registration
forktty mcp setup --dry-run
List socket and provider capabilities
forktty capabilities --json
Read compact workspace context
forktty context-snapshot --tail-lines 0 --json

One automation surface

The CLI, MCP bridge, and GTK app share the same socket behavior. That keeps workspaces, surfaces, status, notifications, worktrees, workflows, and teams consistent across human and agent interactions.

Compact context first

Agents can start with cheap reads such as identify and context snapshots before taking action. Snapshot defaults are compact: team details, workflow details, feed traces, and full message bodies are opt-in.

  • Terminal text reads are bounded and marked untrusted.
  • Worktree mutations require a repository visibly represented in ForkTTY.
  • Team worker cleanup only closes current-runtime launch-owned disposable panes.

Designed for local trust

ForkTTY uses a local Unix socket and stdio MCP bridge rather than a network service. The security model assumes same-user local automation and avoids hidden remote control planes.

Questions

What can ForkTTY MCP tools inspect?
They can inspect workspaces, surfaces, bounded terminal text, agent health, team summaries, workflow loop state, notifications, remotes, and git worktree state.
Can MCP tools send terminal input?
Yes, but the pane is visible and the same socket validation applies. Worker prompts should use the team mailbox and provider-aware dispatch path.
Is ForkTTY MCP network-exposed?
No. The MCP server is local stdio, backed by an owner-only local socket.

Get the alpha build

AppImage and .deb packages are published on GitHub Releases for Linux x86_64.

View releases