All agents
Busabase for ChatGPT

Connect ChatGPT to Busabase

Web chat; add Busabase as a custom MCP server from ChatGPT Plugins (chatgpt.com/plugins), then @-mention it in Chat or Work.

Busabase MCP server

https://busabase.com/api/mcp

Read the ChatGPT documentation
Busabase
MCP connector
A Base of posts in a Busabase workspace, with records, views, and agent prompts

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)
  1. Open ChatGPT on the web and go to Plugins (chatgpt.com/plugins).
  2. Select the plus button, then Add custom MCP server.
  3. Enter a name (for example Busabase), and under Connection enter the Server URL https://busabase.com/api/mcp.
  4. Set authentication to OAuth. Review the risk warning and select I understand and want to continue, then Create as a plugin.
  5. Install the resulting plugin (it appears in your personal plugins), complete the Busabase sign-in in the browser, then start a new conversation, type @, and pick the Busabase plugin.
  6. Ask it to call auth_verify.

Account and workspace policies decide who can add custom MCP servers; write-capable custom connectors may be limited to Business, Enterprise, and Edu workspaces, and on a plan without them the connector is read-only, so the agent can inspect the workspace but cannot open a Change Request. Write tool calls ask for confirmation by default.

Add custom MCP server (OpenAI docs)

Known gotchas

Use ChatGPT on the web to add the server; workspace permissions and security restrictions (including Lockdown) apply. 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. ChatGPT cannot resolve localhost:15419, so Busabase Desktop is not reachable directly; OpenAI documents a Secure MCP Tunnel (tunnel-client plus an OpenAI Platform tunnel_id) for private servers, which is a separate setup.

How it compares

Connection capabilities side by side with other agents already in this directory.

CapabilityChatGPTClaude CodeCursor
TypeWeb chatTerminal agentsAI editors
Recommended pathMCP connectorAgent SkillAgent Skill
How it connectsMCP + OAuthMCP + OAuth · Plugin / SkillMCP + OAuth · Plugin / Skill
TransportStreamable HTTPStreamable HTTPStreamable HTTP
AuthenticationOAuth (dynamic registration)OAuth (dynamic registration)OAuth (dynamic registration)
These stepsFrom official docsLast checked Oct 21, 2026

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.

Where these steps come fromOfficial site

Let your agent do the setup

One instruction, one authorization, and every change it makes afterwards carries a message and a diff you can check or revert.

Browse every agent

Busabase MCP server

https://busabase.com/api/mcp