Claude Desktop

Tier 2: configuration verified on 2026-10-21 against the Claude custom connectors guide. Claude Desktop was not installed on the verification machine. The connector flow, the authentication choices, the plan limits and the network behavior below are quoted from the current guide; the broker endpoints were checked live.

Before you start

• Claude Desktop, or claude.ai, signed in to the account that should own the agents. Custom connectors are available on Free, Pro, Max, Team and Enterprise plans; a Free account can add one custom connector.
• A GitHub account for the human owner. The OAuth sign-in is a separate browser round trip from the Claude session.
• A verified human account with the master delegation agreement signed. See the agent quickstart.
• The server URL has no trailing slash: https://agentregistrar.dev/mcp.

Add the server

For an individual Pro or Max account:

1. Open Customize > Connectors.
2. Choose + Add, then Add custom connector.
3. Enter a name, for example Agent Registrar.
4. Enter the server URL: https://agentregistrar.dev/mcp.
5. Review the authentication settings Claude detects, then choose Sign in when needed so the connector can be enabled without an immediate sign-in.
6. Under OAuth client, choose Use Claude's published identity (Recommended). The broker advertises client_id_metadata_document_supported: true, so a Client ID Metadata Document is accepted. If that option is unavailable, choose Register automatically as the fallback: the broker also supports dynamic client registration, so no client ID or secret is needed.
7. Finish with Add.

For a Team or Enterprise organization, an Owner or Primary Owner adds the connector once under Organization settings > Connectors with the same URL and authentication choices. Members then connect their own account from Customize > Connectors.

Do not choose Use your own OAuth client unless you have a client registered with the broker, which the portal does not offer. Do not add a fixed bearer token under Request headers; this server uses OAuth.

Authorize

In Customize > Connectors, find the connector and choose Connect. Claude opens a browser for the GitHub account that should own the agents. Approve the request. The connector then shows as connected for that account.

If the sign-in is deferred, the first tool call triggers the same browser flow. Complete it before retrying the call.

Verify the connection

Enable the connector for a conversation with the + button, then Connectors. The connector appears with a toggle. Open the tools menu (Search and tools) and confirm the broker's nine tools are listed: identity_register, identity_whoami, identity_signup, identity_prove, identity_record_signup, inbox_list, inbox_read, inbox_wait_for_email and inbox_send.

A connector that is connected but exposes no tools did not finish initialization. Remove and re-add it before assuming the broker is at fault.

First call

Use the Agent Registrar connector. Call identity_register with {"name": "claude-desktop-agent", "harness": "claude-desktop"}, then call identity_whoami with no arguments and show the result.

identity_register creates the agent and binds it to this OAuth session; identity_whoami then returns the same agent. Register first, because a bare identity_whoami auto-provisions the broker defaults, opencode-agent with harness: "opencode-v2", for every client. Registration is idempotent: the agent bound to the token is returned whatever name you pass later, so a different name needs a new OAuth session.

The shape below is illustrative, with synthetic ids and address. It is the identity_whoami result; identity_register returns the same core profile plus created_at. The nested agent mirror, signup_state and docs are omitted for length.

{
  "id": "agt_01JAB2C3D4E5F6G7H8J9K0D1E2",
  "name": "claude-desktop-agent",
  "slug": "claude-desktop-agent-k0d1e2",
  "harness": "claude-desktop",
  "email_address": "claude-desktop-agent-k0d1e2@agents.agentregistrar.dev",
  "status": "active",
  "scopes": ["tos:accept", "signup:free_tier", "inbox:read", "inbox:send"],
  "human_owner": { "...": "..." }
}

Continue

The full signup is in the agent quickstart. Tool inputs and error codes are in the reference.

Troubleshooting

Removing a connector removes its stored credential. There is no separate logout for a custom connector.

Remove and reset

Open Customize > Connectors, find the connector, and choose Remove from its menu. To change the URL or the OAuth settings, remove the connector and add it again; the guide states that editing requires a re-add. On Team and Enterprise plans an Owner can remove it for the organization.

Verification record

Tier 1 needs a recorded transcript from a real connector session, including the client surface and a brokered signup. That transcript does not exist yet.