Browse documentation
Agent-first documentation · 2026-08-11.3 · Updated 2026-08-11 View as Markdown

Connect ChatGPT, Claude, or another MCP client

Domino exposes a remote MCP endpoint at:

https://letsdomino.io/mcp/v2

The endpoint currently authenticates with a Domino Agent Access bearer token in the HTTP Authorization header. The client must be able to store and send that header securely.

First decide: explain or act

Let ChatGPT or Claude explain Domino

No connector or token is required. Use a prompt such as:

Read https://letsdomino.io/llms.txt and the most relevant linked pages.
Tell me how to create an Ideas List in the Domino website. Do not perform it.

Let an assistant access the Domino account

The assistant needs a compatible MCP or API connection plus a least-privilege Agent Access token. Reading documentation alone never grants account access.

Authentication compatibility check

Before entering the endpoint, confirm that the client supports all of the following:

  • a remote HTTP MCP server;
  • a custom Authorization: Bearer ... header or a protected bearer-token field;
  • JSON-RPC initialize, tools/list, and tools/call;
  • custom write tools if the user expects mutations;
  • review or confirmation behavior for consequential actions.

If the hosted connector UI only accepts OAuth and does not offer a secure static bearer-token field, it is not directly compatible with Domino's current MCP authentication. Do not paste the token into the server URL, app description, tool prompt, or chat to work around that limitation.

Use a header-capable MCP client or the Capability API instead.

Generic header-capable configuration

Clients that accept a remote server plus static headers generally use this shape:

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

Use the actual configuration schema required by the client. Store YOUR_TOKEN through a protected secret mechanism when supported.

ChatGPT

ChatGPT custom MCP apps and developer mode are controlled by plan, workspace, administrator, and current product availability. OpenAI's current flow uses Settings or Workspace settings → Apps → Create, then asks the user to provide the remote MCP endpoint, choose an available authentication mechanism, and scan tools.

Before attempting the connection:

  1. Confirm the ChatGPT plan and workspace allow custom MCP apps.
  2. Confirm the user is allowed to enable developer mode or create an app.
  3. Inspect the authentication choices shown by ChatGPT.
  4. Continue only if ChatGPT offers a secure method that can send Domino's bearer header.
  5. Enter the Domino endpoint.
  6. Choose Scan Tools.
  7. Verify the scanned tools match the Domino token abilities.
  8. Create or enable the draft app for a test conversation.

If the authentication choices do not support the Domino bearer token, stop. Domino does not currently expose the OAuth authorization-server flow expected by OAuth-only remote connector setups.

ChatGPT's availability and menus can change. Check OpenAI's current developer mode and MCP apps documentation before giving exact workspace-menu instructions.

Claude web and hosted custom connectors

Claude's hosted custom-connector flow asks for a public remote MCP URL and typically uses the authentication mechanism supported by that connector flow. Team and Enterprise owners can need to register the connector for the organization; individual plan users can use Customize → Connectors → Add custom connector when available.

Because Domino currently uses a static bearer header rather than an MCP OAuth flow:

  1. Inspect the connector's authentication fields before adding it.
  2. Use the hosted connector only if it securely supports the Domino bearer token.
  3. Do not place the token in the URL or ordinary chat.
  4. If only OAuth configuration is available, use Claude Code, another header-capable client, or the Capability API instead.

See Anthropic's current remote MCP custom connector instructions for plan and organization setup.

Claude Code or another CLI client

A CLI that supports remote HTTP MCP headers can connect directly. For example, a current Claude Code-style command is:

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

Prefer a protected environment or credential store over a literal token in shell history. Use the client's current official syntax rather than copying an old command blindly.

Verify the connection

  1. Initialize the MCP session.
  2. Run tool discovery.
  3. Confirm read-only versus write/RSVP/commit tools match the token.
  4. Ask a harmless question such as “Is my Domino calendar connected?” or “List my Ideas Lists.”
  5. Verify the answer is grounded in structuredContent and the current Domino account.

Do not begin with an invitation send, connection request, RSVP, delete, or cancellation.

Tool refresh and schema changes

Domino's MCP tools are generated from its current capability registry. Some hosted clients cache or freeze scanned tool definitions. If a known current tool is missing or its arguments changed:

  1. fetch https://letsdomino.io/docs/mcp-tools.json;
  2. compare it with the client's discovered catalog;
  3. refresh or rescan the app tools;
  4. recreate the draft connector when that client requires it;
  5. do not guess fields from an older scan.

Common failures

401

The token is missing, malformed, revoked, or not being sent by the client. Check the secure header configuration without exposing the token in logs.

403

The token lacks the required ability or the Domino account is not eligible for that access. Do not broaden abilities automatically.

Tool scan returns too few tools

Compare the granted abilities with the authenticated tools/list response. Discovery is authorization-filtered.

Tool calls work but sends do not

External effects require Send ability plus a valid prepared action, later explicit user approval, and actions.commit from the same MCP principal. A ChatGPT or Claude confirmation dialog does not replace Domino's prepared-action contract.

LLM answering guidance

  • Never promise direct ChatGPT or Claude compatibility without checking the current authentication field.
  • Distinguish documentation retrieval, connector creation, authentication, tool scan, read test, and write authority.
  • Link to current client documentation for menus that can change.
  • Never solve an authentication mismatch by asking the user to paste the bearer token into chat.