01
Add OnBuddy to your agent
Open your agent’s remote MCP settings, choose OAuth, and add the server URL shown below. Your agent provider may require an admin to enable custom servers.
OnBuddy Workspace · MCP
Your assistant. Your work. Your permissions.
Bring the AI tools you use into your ongoing work. OnBuddy’s Model Context Protocol server lets compatible agents find context and help with tasks, using the access you choose.
Connect through your own OnBuddy account
Choose your workspace, spaces and permissions. Your agent acts as you. Workspace policy and your current role still apply to every request.
02
Choose what it can access
Sign in to OnBuddy and select a workspace, spaces and permissions. Start with reading tasks; approve write access only when you need the agent to make changes.
03
Check the connection
Ask your agent to identify your OnBuddy workspace and list your authorized spaces. Refresh AI connections in OnBuddy to check whether a tool request succeeded.
Choose your assistant
Connect Claude, ChatGPT, Codex or another compatible assistant
Ask what needs your attention, summarize progress across a space, or turn your conversation into follow-up tasks. OnBuddy uses MCP to connect your assistant to the work you authorize.
https://mcps.onbuddy.ai/onbuddyUse remote Streamable HTTP with OAuth and automatic client registration. No shared workspace key is needed. Your assistant’s account and administrator requirements also apply.
Claude
For a company-managed Claude account, an authorized Claude administrator must first add OnBuddy in Organization settings → Connectors. Each member then connects with their own OnBuddy account.
- Open Customize → Connectors. Add a custom connector named OnBuddy, or select the connector your administrator added.
- Enter the server URL shown here. Choose sign-in with OAuth. If asked how to identify the OAuth client, choose Register automatically; no client secret or API key is needed.
- Connect, sign in to OnBuddy and approve your workspace, spaces and permissions. Return to Claude and enable OnBuddy from the conversation’s connector menu.
ChatGPT web
Your ChatGPT account and workspace must allow custom MCP plugins. If the option is unavailable, ask your ChatGPT workspace administrator. This setup is separate from local Codex configuration.
- Open Plugins → + → Add custom MCP server. Name it OnBuddy and enter the server URL shown here.
- Choose OAuth and automatic client registration (DCR) where offered. Review the connection notice and create the plugin. OnBuddy does not require you to supply a client secret.
- Install the plugin and connect your OnBuddy account. Approve selected access, then start a conversation and select OnBuddy using @.
ChatGPT desktop / Codex app
Use a desktop surface with MCP server settings. Local configuration can be shared with Codex CLI and IDE on the same host; it does not install a plugin in ChatGPT web.
- Open Settings → MCP servers → Add server. Name the server OnBuddy and choose Streamable HTTP.
- Paste the server URL shown here, save, and restart the MCP connection or app as requested.
- Select Authenticate, sign in to OnBuddy and approve selected access. Return to the app and use /mcp where available to check the connection.
Codex CLI / IDE
Install Codex CLI, or use the MCP settings in the Codex IDE extension. Your organization may manage which servers are allowed.
- Run the commands below in your terminal. In the IDE, you can instead add a Streamable HTTP server named OnBuddy in MCP settings.
- Complete the OnBuddy sign-in opened by the login command and choose your workspace, spaces and permissions.
- Return to Codex. Use /mcp in the CLI, or the IDE server list, to check that OnBuddy is connected.
codex mcp add onbuddy --url https://mcps.onbuddy.ai/onbuddy codex mcp login onbuddy
Other compatible assistants
The assistant must support remote Streamable HTTP, OAuth with PKCE and dynamic client registration (DCR). Check its documentation and organization policy before starting.
- Add a remote MCP server named OnBuddy using the URL below.
- Choose OAuth and automatic registration. Start sign-in from the assistant; do not paste credentials into a conversation.
- Approve access in OnBuddy, return to the assistant and enable the connection for your conversation.
Your first useful request
“Use OnBuddy to identify my workspace, list the spaces I authorized, and show my open tasks in a space I choose.”
Refresh AI connections after the reply. Verified means a tool request succeeded; check the answer identifies the workspace you intended.
For members
Your connection stays yours
Connect using your own identity. Choose the spaces your agent can use and review each requested permission. Reduce access directly in Settings → AI connections. Reconnect from your assistant to authorize more access, or revoke the connection at any time. Connections expire after 30 days.
An agent receives the data it reads. Revoking access prevents subsequent requests; it cannot recall data already received by the agent.
For workspace admins
Set the workspace’s boundaries
Member self-service is the default. Owners and admins can restrict connections to admins or pause external agents for everyone. They can also limit all assistants to read-only access. Review the impact before applying policy, see who authorized connections and their recent changes, and revoke individual grants in Workspace AI access.
Restoring policy access resumes unexpired grants. Revoking a grant requires a fresh connection. Admin policy never gives an agent access beyond the member’s own permissions.
Get unstuck
I cannot add a custom server in my agent.
Check that your host supports remote MCP with OAuth, and ask its workspace admin whether custom connections are enabled.
OnBuddy says access is paused or restricted.
Ask an OnBuddy workspace owner or admin to review AI connections. You can still manage and revoke your existing grants.
I authorized, but the connection is not working.
Return to the agent and run the verification prompt. Check the workspace you selected, then refresh OnBuddy’s connection list. An authorization alone does not prove the agent has reached the server.
The agent needs another permission.
Reconnect from the agent and review its new request. Existing grants never gain permissions automatically. Space membership and role restrictions continue to apply.
My connection expired or was revoked.
Open Connection history in OnBuddy for reconnect guidance. Start fresh sign-in from your assistant and review access again. Ended connection details remain for up to 30 days after expiry; old records already removed cannot be recovered.