All agents
Busabase for Claude Duet

Connect Claude Duet to Busabase

Anthropic's proactive agent app (iOS, Android and claude.ai), announced 2026-10-21 as a waitlist-only research preview for US Pro and Max subscribers. It works on its own cloud computer, sends a morning brief and asks before sensitive actions.

Busabase MCP server

https://busabase.com/api/mcp

Read the Claude Duet 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
Anthropic
How it connects
MCP + OAuth · MCP + API key
Transport
Streamable HTTP
Authentication
OAuth (dynamic registration)

Claude Duet uses your Claude account's connectors, so you add Busabase once in the Claude app. Anthropic says Duet "carries over your memory, skills, and connected apps from your Claude account" and can use "all the apps and services you've chosen to connect to Claude".

  1. In the Claude app on the web, open Customize → Connectors, click + Add, then Add custom connector.
  2. Enter a name and the remote MCP server URL https://busabase.com/api/mcp, then Continue.
  3. Review the authentication settings Claude detected (Authentication: Sign in now; OAuth client: keep the recommended Use Claude's published identity, or Register automatically), then Continue and Add.
  4. Complete OAuth in the browser.
  5. Open Claude Duet and ask it to call auth_verify on Busabase.

As an alternative to OAuth, the Request headers section accepts a fixed Authorization: Bearer <key> (create the key in Busabase Settings → API Keys).

Not yet confirmed by Anthropic: its Duet pages do not say whether a custom connector you add this way appears in Duet, and we have not been able to try Duet (waitlist). If step 5 fails, tell Duet which connectors it can see and use the Claude page to check the connector itself.

Get started with custom connectors using remote MCP

Known gotchas

Research preview on a waitlist for Claude Pro and Max in the US; Team and Enterprise are not included. Anthropic does not say whether a custom connector (such as a remote MCP server) you add in Claude carries over to Duet; it only says Duet can use the apps and services you connect to Claude. Not tried by us yet. It runs as a standalone iOS and Android app and on claude.ai, on Anthropic's cloud computer, so it cannot reach Busabase Desktop on localhost. Background checks count toward your Claude plan's usage limits.

How it compares

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

CapabilityClaude DuetClaude CodeCursor
TypeAgent platformsTerminal agentsAI editors
Recommended pathMCP connectorAgent SkillAgent Skill
How it connectsMCP + OAuth · MCP + API keyMCP + 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 24, 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