"Threads" matching MCP servers:

Enables external agents to list T3 environments and projects, start coding threads, monitor progress, send follow-up instructions, and interrupt running turns via MCP.

MCP server for interacting with a running T3 Code instance. Enables viewing agent threads, sending messages, and approving permission requests from Claude Code or voice-controlled models.

Enables hands-free, voice-driven management of T3 Code projects, threads, agent runs, and pending actions via GPTVoice tool calls.

Enables MCP clients to start new Codex conversations and continue existing threads, exposing codex and codex-reply tools over stdio via the Codex app-server protocol.

Bridges MCP clients with local Codex CLI to execute autonomous coding tasks, manage threads, and inspect history via SQLite state.

Lets an agent delegate coding tasks and reviews to Claude Code, Codex or Grok Build CLIs running locally in isolated git worktrees, then poll an inbox for the status, question or final answer. Each caller sees only its own threads.

Lets coding agents create and manage threads in a running T3 Code server over MCP.

Enables ChatGPT to supervise and control local Codex runtime sessions through a secure MCP interface, managing threads, turns, approvals, events, and recovery without exposing direct file, shell, Git, SSH, or model loop access.

A personal MCP bridge that lets ChatGPT drive a local Codex CLI, translating instructions into Codex app-server threads and returning compact summaries of what Codex did.

An MCP server that allows Pebble Index to capture notes, enqueue tasks, create follow-ups, and launch visible Codex threads on a Windows PC. It uses a remote server with token-based access and a local runner that executes only explicit execution requests.

Enables coding agents to start, monitor, and control T3 Code / T3 Turbo threads locally via MCP.

Lets MCP clients connect to T3Code for voice conversations, browsing threads, reading updates, answering questions, reviewing approvals, and starting coding turns over Streamable HTTP.

Enables MCP-compatible hosts such as OpenCode to drive the Codex CLI through codex app-server over stdio, exposing tools to run prompts, inspect status, list threads, and interrupt running turns.