Browse documentation
Agent-first documentation · 2026-11-14.1 · Updated 2026-11-14 View as Markdown

Connect ChatGPT, Claude, or another MCP client

Domino exposes the public remote MCP endpoint:

https://letsdomino.io/mcp

The endpoint supports two bearer-token paths:

  • browser-based OAuth for claude.ai and eligible ChatGPT workspaces;
  • static, per-user Agent Access bearer tokens for Claude Code, API clients, and other header-capable MCP clients.

Both paths use the same Domino ability filtering and capability registry. They do not make public documentation private, broaden abilities automatically, or bypass prepared-action confirmation.

Pick the correct access path

Goal or client Authentication What it can do
Let ChatGPT or Claude explain Domino None; read https://letsdomino.io/llms.txt Public product instructions only. No account access.
ChatGPT custom app or claude.ai hosted custom connector Domino OAuth MCP tools selected on the Domino consent screen.
Claude Code or another header-capable MCP client Static Agent Access bearer token MCP tools allowed by that token.
Claude API / programmatic MCP connector Caller-supplied authorization_token MCP tools allowed by the supplied token; the application owns credential storage and refresh.
Capability API or Assistant API Static Agent Access bearer token Typed API operations allowed by that token. Domino's MCP OAuth access tokens are MCP-audience-bound and are rejected by the APIs.

Never put a bearer token in a server URL, prompt, description, normal chat message, source file, screenshot, or log.

claude.ai hosted custom connectors

Domino implements the OAuth discovery and Dynamic Client Registration flow that Anthropic currently documents for custom connectors. Use Connect claude.ai to Domino with OAuth for exact setup, consent, verification, editing, and revocation steps.

The short path is:

  1. Open Customize → Connectors in claude.ai.
  2. Choose Add custom connector.
  3. Add https://letsdomino.io/mcp.
  4. Choose Connect, sign in to Domino, and select the smallest abilities needed.
  5. Enable Domino from the conversation's + → Connectors menu.
  6. Verify authenticated initialize, tools/list, and one harmless read request.

Creating the connector is not proof that it authenticated, discovered tools, or reached the intended Domino account.

Claude Code or another header-capable MCP client

Create a least-privilege token in Domino's Agent Access settings. A current Claude Code-style setup is:

claude mcp add --transport http domino https://letsdomino.io/mcp \
  --header "Authorization: Bearer YOUR_TOKEN" \
  --header "X-Domino-Client: claude-code"

Use the client's current official syntax. Prefer its protected credential store or an environment/secret reference over a literal token in shell history.

Generic header-capable clients often use this shape:

{
  "mcpServers": {
    "domino": {
      "url": "https://letsdomino.io/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TOKEN",
        "X-Domino-Client": "your-client-name"
      }
    }
  }
}

Claude API or another programmatic MCP caller

Anthropic's Messages API MCP connector accepts an authorization_token; the application must obtain, store, rotate, and revoke that credential safely. Domino does not open an interactive browser flow inside an API request.

Use a static Domino Agent Access token with only the required abilities, supply it through the API's protected authorization_token field, and keep it out of request logs. The token remains a Domino credential; it is not an Anthropic API key.

If an application implements Domino's OAuth flow itself, it must follow protected-resource discovery, Dynamic Client Registration, the resource parameter, exact registered redirects, PKCE S256, state validation, refresh rotation, and revocation. Do not copy a claude.ai OAuth access or refresh token into another client.

ChatGPT

Open the plugin directory from Settings → Plugins → Browse directory. The settings page lists the plugins already installed. In the directory, open Add and look for Add custom MCP server. Available options depend on the account or workspace. ChatGPT plugin directory · OpenAI’s private plugin setup

Start with https://letsdomino.io/mcp. In a workspace that permits custom MCP apps, add that URL, select OAuth and use automatic client registration. The management page must show the exact callback https://chatgpt.com/connector_platform_oauth_redirect for Domino's default configuration. If it shows another callback, the deployment operator must first register that exact URI. OpenAI authentication reference

Open Domino's consent screen in the browser. Sign in to the intended account and enter any SMS sign-in code there. Start with Read for an account check. Return to the app, enable Domino and ask “Is my Domino calendar connected?” Review the result before granting any additional permission.

Refresh an existing ChatGPT connection

If ChatGPT reports errors for Domino tools after an update, open the installed Domino plugin you used in that chat. Choose Settings → Manage app → Refresh tools. When the refresh finishes, choose View details → Try in chat. This opens a fresh chat with that same plugin selected. Ask “Using Domino, what needs my attention? Give me at most three current actions and a link to My Dominos.” Follow the link to check the answer against your plans. ChatGPT plugin directory

Dots in Codex

Use the ChatGPT account associated with your Dot. Check Installed in the plugin directory. If Domino is absent, use the private setup above when your account offers it. After installation, check that the plugin is enabled for your Dot. Open a Dot conversation and ask “Using Domino, is my calendar connected?” A Domino answer that reports a disconnected calendar still verifies that the Dot can read the account. A reply that the plugin is unavailable leaves the connection unverified. Dot computers and apps

Muse

Ask Muse to set up a private custom connector for Domino using https://letsdomino.io/mcp. If it offers secure bearer authentication, create a Read credential in Agent Access and enter it in the connector’s credential field. Return to the chat and ask “Using Domino, what needs my attention?” If Muse reports a timeout, check the credential’s last use in Domino. A timeout without an HTTP response leaves the cause unresolved. Domino Agent Access · Muse custom connectors

Grok Bot for Mac

Open Connect apps → Add a custom connector, choose Remote HTTPS and enter https://letsdomino.io/mcp. Grok Bot provides an HTTP headers field. For a scoped Agent Access token, enter the Authorization header in the connector settings. Return to the bot and ask for calendar connection status to check the account. Grok Bot connector instructions

Verify every connection

  1. Authenticate the connection.
  2. Complete MCP initialize.
  3. Run authenticated tools/list.
  4. Confirm read, draft, RSVP, and commit tools match the granted abilities.
  5. Make a harmless read call, such as checking calendar connection status or listing Ideas Lists.
  6. Inspect the typed structuredContent and confirm it belongs to the intended Domino account.

Do not start with an invitation send, connection request, RSVP, delete, cancellation, booking, purchase, or payment.

Common failures

401

The bearer token is missing, malformed, expired, rotated, revoked, or not being sent. The response advertises Domino's RFC 9728 resource_metadata location so OAuth clients can discover authorization. Do not expose a token while debugging.

403 or a missing tool

The connection lacks the required ability, or the requested feature is disabled for this account or surface. Authenticated tool discovery is ability-filtered. Do not broaden abilities automatically.

The connector exists but tools are unavailable

Connector creation, OAuth completion, token issuance, MCP initialization, tool discovery, tool enabling, and task execution are different states. Verify them in that order.

Tool calls work but sends do not

Sending invitations requires Send. Review the recipients and delivery method, obtain later approval for that exact action, and use the confirmation operation on the original MCP connection. Domino checks the permission required for each action when it executes.

Tool refresh and schema changes

Domino's MCP tools are generated from its capability registry. If a current tool is absent or has changed arguments:

  1. fetch https://letsdomino.io/docs/mcp-tools.json;
  2. compare it with authenticated tools/list;
  3. refresh or rescan the client's tools;
  4. recreate the connector only when that client requires it;
  5. never guess fields from an old scan.

LLM answering guidance

  • Distinguish public docs access, claude.ai OAuth, static MCP headers, and programmatic API token use.
  • Distinguish connector configuration, authentication, tool discovery, a harmless account read, and task completion.
  • Link to current client documentation for menus that can change.
  • Never solve an authentication mismatch by requesting a secret in chat.