t3-mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@t3-mcp What T3 environments do I have?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
t3-mcp
Host-independent MCP connector for directly pairing T3 Code environments. It does not require T3 Connect, a host-specific bot setup, or a local turn CLI.
Install
Node.js 20 or newer is required.
npm install -g t3-mcp
t3-mcpThe process speaks MCP over stdio. A generic host configuration is:
{
"mcpServers": {
"t3-mcp": {
"command": "t3-mcp",
"args": [],
"env": {
"T3_MCP_STATE_DIR": "/absolute/path/to/t3-mcp-state"
}
}
}
}T3_MCP_STATE_DIR is optional. Omit it to use the platform state directory outside the repository.
A host that does not use globally installed commands can use "command": "npx" with
"args": ["--yes", "t3-mcp"].
The package contains exactly one skill, t3-run-turn, at skills/t3-run-turn/SKILL.md. It is
host-neutral and uses MCP tools rather than shell commands.
Related MCP server: t3code-mcp
Workflow
Pair directly with an environment using
add_environmentand either apairingUrlor anendpointplusgrant. A pairing URL may carry its grant in a?token=...query or#token=...fragment. T3 Connect is not required.Call
list_environments, select an explicit environmentid, then calllist_projectswith that id. Project and thread identifiers are scoped to the selected environment.Use
start_turnwithenvironmentId,projectId, andpromptfor a new thread. Usecontinue_turnwithenvironmentId,threadId, andpromptfor a new turn in an existing thread. A continuation never forks or silently queues work.Observe with
get_thread. History is bounded to 20 turns by default and 100 at most. Whenhistory.hasMoreorhistory.truncatedis true, passhistory.nextCursorasbeforeCursorto retrieve an older page instead of requesting unbounded history.If a thread reports
approval_requiredorinput_required, resolve it in T3 Code and callget_threadagain. This connector does not approve work or submit input on the user's behalf.If
start_turnorcontinue_turnreturnsunknown, do not retry immediately. Inspect the referenced thread withget_threadfirst; only then decide whether a retry is safe. Mutation requests are never automatically replayed.
After adoption, normal turns use these MCP tools. A local turn CLI, if one is available in a host,
is an optional debugging utility; this package never invokes t3-turn. Optional Connect support is
not part of this release chain.
Tools
add_environment:pairingUrl?,endpoint?,grant?,label?,environmentId?.list_environments: no arguments.list_projects:environmentId.start_turn:environmentId,projectId,prompt, and optionalmodelSelection.continue_turn:environmentId,threadId,prompt.get_thread:environmentId,threadId, and optional boundedturnLimit/beforeCursor.
Pairing URLs use the upstream ?token=... or #token=... form. The response never includes the
grant, access token, authenticated URL, or raw upstream error body.
Mutation acknowledgements are not replayed. A partial result keeps the created thread reference,
and an ambiguous transport result is unknown so the caller can inspect the thread before retrying.
Security
HTTPS is required except for loopback endpoints.
URL credentials and arbitrary query parameters are rejected. A pairing URL query may contain only
token, and the connector removes it before making requests. Endpoint URLs with an explicit grant remain query-free.Redirects are rejected, so credentials are never forwarded to another origin.
The registration file is outside the repository, owner-only, and atomically replaced.
A failed re-pair leaves the existing registration unchanged.
Supported contract
See docs/compatibility.md for the upstream version and the exact
descriptor, token exchange, scopes, and session checks used by this package.
Automated compatibility coverage runs an MCP client against the connector process and controlled HTTP environments implementing the supported direct-pairing contract. No live direct-pairing smoke check was run for this release because this workspace has no operator-provided environment endpoint or grant; the controlled checks must not be read as a claim that a live T3 deployment was exercised.
Available Tools
6 toolsadd_environmentC
Pair a T3 Code environment directly and save its scoped session for future MCP requests.
Inputs: grant, label, endpoint, pairingUrl, +1 more. Returns: error, environment
continue_turnB
Submit a new turn to an explicitly selected existing thread.
Inputs: prompt (required), threadId (required), environmentId (required). Returns: error, continuation
get_threadARead-onlyIdempotent
Read one thread from an explicitly selected environment with bounded, paginated history.
Inputs: threadId (required), environmentId (required), turnLimit, beforeCursor. Returns: error, thread
list_environmentsARead-onlyIdempotent
List saved T3 Code environments without returning credentials.
Inputs: no named parameters. Returns: error, environments
list_projectsARead-onlyIdempotent
List projects from one explicitly selected T3 Code environment.
Inputs: environmentId (required). Returns: error, projects, environmentId
start_turnA
Create a thread and submit its first turn in an explicitly selected environment and project.
Inputs: prompt (required), projectId (required), environmentId (required), modelSelection. Returns: error, start
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool targets a distinct resource and action: projects vs environments vs threads, and actions are clearly separated (list, add, start, continue, get). No ambiguity in purpose.
All tool names follow a consistent verb_noun pattern (list_projects, add_environment, start_turn, etc.), making the API predictable and easy to navigate.
Six tools is well-scoped for managing environments and thread interactions; each tool has a clear role and the count feels neither bloated nor sparse.
The core workflows of environment setup and thread lifecycle (start, continue, read) are covered, but operations like deleting environments or listing threads are missing, which agents may occasionally need.
Maintenance
Related MCP Connectors
Connect ChatGPT and Claude to your Mac, Windows or Linux with secure MCP remote access.
Shared memory MCP server for Claude Code, Codex, Gemini CLI and Cursor. Cited, editable.
Termalin's hosted MCP server. Claude, ChatGPT or any MCP client runs commands, moves files over SFTP, queries databases and reads server metrics and monitoring alerts on your servers, keylessly through Termalin Connectors: no SSH key is handed over and no inbound port is opened. Per-host command policy and an audit log. Needs a termal.in Pro or Team account (new accounts start with a 14-day Pro trial).
Real-time chat for AI agents. Claude Code, Cursor, Cline and Codex join channels over MCP.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceEnables 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.-
- AlicenseAqualityBmaintenanceEnables external agents to list T3 environments and projects, start coding threads, monitor progress, send follow-up instructions, and interrupt running turns via MCP.73MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to interact with real terminal sessions across local and remote hosts, driving multi-turn interactive programs like TUIs, REPLs, and SSH prompts through MCP.72MIT
- AlicenseNot gradedqualityBmaintenanceConnects ChatGPT and MCP clients to authorized local development environments, enabling secure file access, shell execution, persistent tasks, browser/desktop control, and remote management of projects.21MIT