Use BiOS from ChatGPT
ChatGPT and the OpenAI Codex CLI
ChatGPT connects to BiOS through our hosted connector: turn on developer mode, add one address, and sign in with your BiOS account. Prefer the terminal? The Codex CLI runs the local BiOS server with an API key, and that path is covered below too.
Before you start
You need a BiOS account, and that is it. The connector signs you in from the app, so there is no API key to copy and nothing to install. Create a free account if you do not have one yet.
Only the local Codex CLI path below uses an API key (created under Dashboard, API Keys) and Node.js 18 or newer.
Setup
- 1
Turn on developer mode
In ChatGPT, open Settings, go to Apps & Connectors, open Advanced settings, and enable Developer mode.
Custom connectors are available on the ChatGPT plans that include developer mode. If you do not see the option, check your plan.
- 2
Create the connector
Back in Apps & Connectors, click Create connector. Name it BiOS and paste this address:
texthttps://mcp.usbios.ai/mcpWhen ChatGPT asks how to authenticate, pick OAuth. Do not pick "No authentication"; the connector needs the sign-in step to know which account and workspace to act on.
- 3
Sign in and approve
ChatGPT opens a BiOS sign-in page. Log in, choose the workspace you want to connect, pick a permission level (Read only, Training, or Full access), and approve. You are sent straight back to ChatGPT.
- 4
Use it in a chat
Enable the BiOS connector from the tools menu in the composer, then ask for what you need in plain English.
- 5
Prefer the terminal? Add BiOS to the Codex CLI
The Codex CLI runs the BiOS server locally with an API key instead of the sign-in flow. Add this block to your Codex configuration file and restart Codex:
~/.codex/config.toml[mcp_servers.usfbios] command = "npx" args = ["-y", "@usfbios/mcp-server"] env = { "USFBIOS_API_KEY" = "sk_live_your_api_key" }
Check that it works
- The connector shows as connected under Apps & Connectors in ChatGPT settings.
- Ask "What is my BiOS wallet balance?" in a chat with the connector enabled. ChatGPT should answer with a number.
- In Codex, ask "List my BiOS training jobs". The CLI should call
list_training_jobsand print your jobs.
Try these prompts
“List my BiOS training jobs and summarize how the newest one is doing”
“Start a LoRA fine-tune of Mistral 7B on my support dataset, and estimate the cost first”
“Deploy my finished fine-tune and give me the endpoint URL”
“Show the metrics for my latest training run”
Your assistant has 38 BiOS tools in total. The tool reference documents each one.
Troubleshooting
There is no option to add a connector in ChatGPT settings
Custom connectors live behind developer mode: Settings, then Apps & Connectors, then Advanced settings. If the toggle is missing, your ChatGPT plan may not include it.
The sign-in page says the connection request has expired
Connection requests are short-lived. Go back to ChatGPT and connect again; the fresh request opens a new sign-in page.
The tools work, but on the wrong workspace
Remove the connector under Apps & Connectors, then create it again and choose the workspace you want on the approval page.
Tool calls fail with a permission error
The connection was approved with a lower permission level than the task needs. Reconnect and pick Training or Full access on the approval page.
Codex CLI: the server never starts, or npx is not found
The local server runs on Node.js. Install Node 18 or newer from nodejs.org, then run npx -y @usfbios/mcp-server in a terminal to confirm it starts (it waits for input; press Ctrl+C to exit).
Frequently asked questions
Do I need an API key for the ChatGPT connector?
No. ChatGPT uses your regular BiOS sign-in through OAuth. Only the Codex CLI path uses an API key, because it runs the server on your machine.
Why pick OAuth instead of "No authentication"?
The sign-in step is what links the connection to your BiOS account and workspace. Without it, tool calls have no account to act on and are rejected.
Does the OpenAI Agents SDK work too?
Yes. The Agents SDK runs the local server: point it at npx -y @usfbios/mcp-server with the USFBIOS_API_KEY environment variable and every BiOS tool becomes available to your agent.
Does the Codex CLI setup need an OpenAI key for BiOS?
No. BiOS only needs its own API key from your dashboard. Your OpenAI account is only used by Codex itself.
Use BiOS from other clients
The same server works everywhere MCP does. More setup guides:
Terminal coding agent by Anthropic
Claude app for macOS and Windows
claude.ai in the browser and the mobile apps
AI code editor
AI code editor with Cascade agent
Open-source VS Code agent extension
GitHub Copilot agent mode
High-performance editor with Agent Panel
Autonomous software engineer by Cognition
Google terminal coding agent