Repository navigation
docs: connect Claude Code, Codex, ChatGPT and bots over MCP #16741
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,94 @@ | ||
| # Outside agents | ||
|
|
||
| Agents that T3 Code did not start can work with an environment through its MCP | ||
| server. They can read projects and threads, start and message threads, and | ||
| check which providers and models are available. This covers Claude Code or | ||
| Codex in your own terminal, ChatGPT, and bots that support MCP. Each agent signs | ||
| in once, and you choose what it may do. | ||
|
|
||
| ## Get the MCP URL | ||
|
|
||
| In **Settings → Connections**, open a saved environment's menu and choose | ||
| **Copy MCP URL**. The URL is the environment's address followed by `/mcp`, for | ||
| example: | ||
|
|
||
| ```text | ||
| https://<environment-address>/mcp | ||
| ``` | ||
|
|
||
| The address must use HTTPS, or `localhost` when the agent runs on the host | ||
| itself. Agents refuse to sign in over a plain `http://` LAN or tailnet address. | ||
|
|
||
| - **An agent on your own computers** can use T3 Connect, Tailscale HTTPS, or | ||
| `localhost` on the host. See [remote access](./remote-access.md). | ||
| - **A hosted agent**, such as ChatGPT or a bot running in the cloud, must reach | ||
| the environment from the internet. Use the T3 Connect address. A Tailscale | ||
| address only works from your own tailnet. | ||
|
|
||
| ## Approve a sign-in | ||
|
|
||
| The first time an agent connects, it opens a sign-in page on the environment. | ||
| The page names the agent and where its access goes: | ||
|
|
||
| - For an agent on your computer, approval returns to a `localhost` address on | ||
| the computer that opened the page. | ||
| - For a hosted agent, approval goes to that service, such as `chatgpt.com`. | ||
| Anyone who runs that service gets the access. | ||
|
|
||
| Only approve a sign-in you just started. To approve, enter a pairing code from | ||
| **Settings → Connections** or from `t3 auth pairing create` on the host. A | ||
| browser already signed in to the environment as an administrator can approve | ||
| without a code. | ||
|
|
||
| Then choose what the agent may do: | ||
|
|
||
| - **Read only** is the default. The agent can read projects and threads and see | ||
| the available providers and models. It cannot change anything. | ||
| - **Supervised** through **Full access** also let it start, message and stop | ||
| threads in every project. A thread it starts or steers cannot run with more | ||
| permissions than the mode you chose. | ||
|
|
||
| ## Claude Code | ||
|
|
||
| ```sh | ||
| claude mcp add --transport http t3 https://<environment-address>/mcp | ||
| claude mcp login t3 | ||
| ``` | ||
|
|
||
| `claude mcp login` opens the sign-in page in your browser. On a machine | ||
| without a browser, add `--no-browser`, open the printed URL elsewhere, and | ||
| paste the final URL back when asked. `claude mcp list` shows `t3` as connected | ||
| once you approve. | ||
|
|
||
| ## Codex | ||
|
|
||
| ```sh | ||
| codex mcp add t3 --url https://<environment-address>/mcp | ||
| codex mcp login t3 | ||
| ``` | ||
|
|
||
| `codex mcp login --no-browser` prints the sign-in URL instead of opening it. | ||
| `codex mcp list` shows `t3` with OAuth once you approve. | ||
|
|
||
| ## ChatGPT | ||
|
|
||
| Add the environment as a custom MCP app in ChatGPT's apps settings: | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win State ChatGPT plan and admin prerequisites. OpenAI’s current documentation limits full MCP, including write actions, to Business, Enterprise, and Edu plans on the web. Pro supports read/fetch access only, and workspace administrators must enable developer mode. Add these prerequisites so users know whether they can create the app and use thread-changing tools. (help.openai.com) 🤖 Prompt for AI Agents |
||
|
|
||
| 1. Create a new app or plugin with a custom MCP server. | ||
| 2. Set the server URL to `https://<environment-address>/mcp`, using the T3 | ||
| Connect address. | ||
| 3. Choose **OAuth** for authentication. ChatGPT discovers the rest; you do not | ||
| need a client ID or secret. | ||
| 4. Create the app, then approve the sign-in page that opens. | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win Move OAuth approval before app creation. OpenAI’s current setup flow completes OAuth during tool scanning, before the user creates the app. This step tells users to create the app first and approve afterward. Move the approval step to the OAuth configuration and tool-scan stage. (help.openai.com) 🤖 Prompt for AI Agents |
||
|
|
||
| ## Other agents and bots | ||
|
|
||
| Any agent that supports remote MCP servers over HTTP with OAuth can connect. Give | ||
| it the MCP URL and choose OAuth, and the agent finds the sign-in settings itself. | ||
| Agents without OAuth support cannot connect. | ||
|
|
||
| ## Remove an agent | ||
|
|
||
| Approved agents appear under **Settings → Connections** like other clients. | ||
| Revoke one there to cut off its access immediately. A sign-in lasts 30 days; | ||
| after that the agent asks you to approve it again. | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔒 Security & Privacy | 🟡 Minor | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: pingdotgg/t3code
Length of output: 45662
🏁 Script executed:
Repository: pingdotgg/t3code
Length of output: 42704
🏁 Script executed:
Repository: pingdotgg/t3code
Length of output: 18552
Clarify the principal for hosted-agent grants.
T3 sends the authorization result to the hosted service's registered redirect host. T3 does not bind this grant to the approving account or workspace. State that the hosted service controls which of its users can use the selected access.
🐛 Suggested fix
🤖 Prompt for AI Agents