Busabase for ChatGPTConnect ChatGPT to Busabase
Web chat; add Busabase under Settings → Connectors → Advanced → Developer mode.
Busabase MCP server
https://busabase.com/api/mcp
Busabase
Set it up
Hosted chat has no shell and no file system, so a connector is the way in.
Add the server
Point your chat client at the Busabase MCP endpoint.
Sign in
Complete OAuth in the browser — no client id or secret to create.
Pick the smallest permission
changeRequest lets the agent propose but never merge.
Verify
Ask the agent to call auth_verify before it does any work.
Step by step
This host has no shell, so a connector is the only way in.
At a glance
- Vendor
- OpenAI
- How it connects
- MCP + OAuth
- Transport
- Streamable HTTP
- Authentication
- OAuth (dynamic registration)
Open Settings → Connectors → Advanced → Developer mode, add https://busabase.com/api/mcp as a custom connector, and complete OAuth in the browser. Write-capable custom connectors may be limited to Business, Enterprise, and Edu workspaces; on a plan without them the connector is read-only, so the agent can inspect the workspace but cannot open a Change Request.
Known gotchas
Write-capable custom connectors may be limited to Business, Enterprise, and Edu workspaces; on other plans the connector is read-only, so the agent can inspect the workspace but cannot open a Change Request. It also cannot reach Busabase Desktop (no way to resolve localhost:15419).
Written from this agent's own documentation. We have not re-run every step on a real machine, so check the linked docs if a command has changed.
Let your agent do the setup
One instruction, reviewed access, and every change it makes afterwards arrives as a proposal you approve.
Browse every agentBusabase MCP server
https://busabase.com/api/mcp