t3-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| T3_MCP_STATE_DIR | No | Optional directory path for storing state. If omitted, the platform state directory outside the repository is used. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_environmentC | Pair a T3 Code environment directly and save its scoped session for future MCP requests. |
| list_environmentsA | List saved T3 Code environments without returning credentials. |
| list_projectsA | List projects from one explicitly selected T3 Code environment. |
| start_turnA | Create a thread and submit its first turn in an explicitly selected environment and project. |
| continue_turnB | Submit a new turn to an explicitly selected existing thread. |
| get_threadA | Read one thread from an explicitly selected environment with bounded, paginated history. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.