T3 Code thread MCP
Related Servers
Alternatives to T3 Code thread MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceLets coding agents create and manage threads in a running T3 Code server over MCP.3MIT
- AlicenseAqualityAmaintenanceEnables external agents to list T3 environments and projects, start coding threads, monitor progress, send follow-up instructions, and interrupt running turns via MCP.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables any agent to spawn and manage T3 Code agent threads over HTTP MCP — starting research or coding agents, sending follow-ups, waiting for results, and answering approval prompts. It pairs once as a T3 device, exposes 15 tools, and keeps operations retry-safe.0MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to start, monitor, and control T3 Code / T3 Turbo threads locally via MCP.1MIT
- FlicenseAqualityCmaintenanceMCP 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.19-
- AlicenseNot gradedqualityDmaintenanceEnables MCP clients to spawn and control Codex CLI and Claude Code sessions on the host machine, with session management and filesystem access.4MIT
TDQS
Scored across 7 tools
Each tool maps to a distinct action on the thread resource (create/list/read/send/wait/settle/interrupt). Descriptions clarify boundaries, e.g. create_thread vs send_message_to_thread and set_thread_settled vs interrupt_thread.
All tools use snake_case with a verb-first pattern and 'thread(s)' as the resource noun. send_message_to_thread is slightly longer but still follows the same convention.
7 tools is well-scoped for peer thread management; each tool covers a necessary operation without redundancy.
Core thread lifecycle (create, list, read, message, wait, settle, interrupt) is covered, but there is no explicit archive or delete operation despite archived threads being referenced. This is a minor gap that agents can work around if archiving is handled elsewhere.