F
licenseA
qualityC
maintenanceMCP 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
-
t3code-mcp
by emmsixx
Related Servers
Alternatives to t3code-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables external AI supervisors to oversee and steer native Codex through MCP, including thread and turn management, observation, interruption, approval responses, runtime status, and checkpointing.MIT
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to start, monitor, and control T3 Code / T3 Turbo threads locally via MCP.MIT
- AlicenseNot gradedqualityAmaintenanceEnables external MCP clients to drive DeepSeek Harness agents for real coding tasks, providing tools for task execution and queueing, session management, sandboxed file access, preset switching, and usage statistics.357 npm2GPL 3.0
- AlicenseNot gradedqualityAmaintenanceEnables controlling an autonomous multi-agent engineering swarm from MCP clients, including starting and managing tasks, spawning agents, triggering PR reviews, and checking swarm status.5 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables external clients to spawn, control, observe, and terminate isolated AI coding agent sessions over MCP via stdio or Streamable HTTP, with scoped chip datasheet knowledge-base retrieval.-
TDQS
A4.1/5.0
Scored across 7 tools
Disambiguation4/5
Most tools are clearly distinct: list_threads/get_thread for reading, start_thread/send_message for creating and continuing threads, interrupt_thread for control, and list_environments/list_projects for discovery. The only mild overlap is between list_threads and get_thread, but their descriptions make the list-vs-detail relationship clear.
Naming Consistency4/5
Tool names follow a consistent verb_noun pattern: list_threads, get_thread, interrupt_thread, list_environments, list_projects, send_message, start_thread. The pattern is predictable, though 'send_message' and 'start_thread' are slightly less uniform than the list/get/interrupt group.
Tool Count5/5
Seven tools is well-scoped for a T3 coding-agent MCP server. Each tool covers a distinct operation: discovery, reading, starting, sending, and interrupting threads, plus environment and project listing. No tool feels redundant or unnecessary.
Completeness4/5
The surface covers the core thread lifecycle: list, get, start, send, and interrupt. Minor gaps exist, such as no explicit archive/unarchive or delete/cancel thread operation, and worktree creation is noted as unsupported, but agents can accomplish the main workflows.
Maintenance
ActivityMaintained
ResponsivenessNo issues