"Threads" matching MCP servers:

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.

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

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 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.