Integrations

The terminal your agents drive.

Point any MCP-capable agent — Claude Code, Codex, Gemini CLI, Cursor, Goose — at TermFlow and it can open terminals, run commands, and read output. You bring the agent and your keys; TermFlow is the terminal they steer.

Works with your agents.

Claude Code

MCP client

Anthropic's terminal agent. Add TermFlow as an MCP server and Claude Code can open terminals, run commands, and read their output — a real terminal instead of a piped subshell.

OpenAI Codex CLI

MCP client

OpenAI's open-source coding agent. Point it at TermFlow's MCP server in its config and it drives real terminals with structured output.

Gemini CLI

MCP client

Google's open-source terminal agent — a first-class MCP client. Connect it to TermFlow's MCP server and it can manage panes and commands.

Cursor

MCP client

The AI editor's agent is an MCP client. Give it TermFlow as a terminal it can spawn, drive, and observe.

Goose

MCP client

Block's open-source agent. An MCP client that can use TermFlow's terminal tools to run and inspect commands.

aider

MCP client (via wrapper)

The open-source pair-programmer. Through an MCP wrapper it can run and observe commands in a TermFlow terminal.

Anything that speaks MCP — including your own scripts and orchestrators — can drive TermFlow the same way.

Three ways to connect.

Built-in MCP server

Available

TermFlow ships a first-party MCP server. Add it to any MCP client's config and the agent can drive your terminal — create panes, run commands, read output.

REST / WebSocket API

Available

Prefer HTTP? The same capabilities are a documented REST + WebSocket API on localhost. Build your own orchestrator against it.

Agent Client Protocol (ACP)

Planned

Hosting ACP agents directly inside TermFlow — spawn Gemini CLI, Goose, or Claude Code (via adapter) in a pane — is on the roadmap. Not shipped yet.

What the MCP server exposes.

TermFlow's built-in, first-party MCP server gives an agent a small, honest set of tools to drive a real terminal:

list_terminalsEnumerate the open terminals.
create_terminalOpen a terminal or split a new pane.
execute_commandRun a command — one terminal, or fan out to many.
get_terminal_outputRead a terminal's output.
get_terminal_detailInspect a terminal's state.
get_my_terminalLet an agent identify its own terminal.
close_terminalClose a terminal — including its own.

Common questions.

Does TermFlow ship its own AI?

No — you bring the agent and your own keys. TermFlow is the terminal they drive. We don't sell AI usage at all.

How does an agent connect?

Add TermFlow's built-in MCP server to your agent's MCP config — or call the REST/WebSocket API directly. The agent can then open terminals, run commands, and read output.

Is ACP supported?

Not yet. Hosting ACP agents inside TermFlow is on the roadmap. Today, agents drive TermFlow as an MCP server or over the HTTP API.

Is it free?

Yes — the API and MCP server are free on your machine, Apache-2.0. See pricing.

Get TermFlow See pricing