Use Dubot with MCP

Connect an AI client for documentation, workspace authoring, or approved actions

Dubot has three MCP use cases. They are intentionally separate.

MCP is optional. You do not need it to install the browser SDK or launch a Resource Center, Wizard, or Guidance experience. Use this page only when an AI client is part of the workflow.

Service	Audience	Access	Server URL	Status
Documentation MCP	Anyone reading these docs	Public, read-only	https://docs.dubot.ai/mcp	Available
Authoring MCP	A Dubot workspace member	OAuth plus workspace grant	https://app.dubot.ai/mcp	Requires a workspace grant; confirm client access with Dubot
Action channel	A customer-product end user	OAuth plus signed product identity and a live tab	https://mcp.dubot.ai/{workspace-slug}	Controlled rollout

Tokens, grants, tools, and consent are not interchangeable across these services.

Documentation MCP

Use the documentation server to search and read public Dubot documentation from an MCP-capable client. It cannot inspect a workspace, change configuration, publish, or run a customer action.

Authoring MCP

The authenticated authoring server lets an AI client work as the connecting Dubot user within explicitly granted workspaces.

1. Add the server

   Add https://app.dubot.ai/mcp to an MCP-capable client.

2. Complete OAuth

   Sign in to Dubot through the authorization flow. Compatible clients register dynamically, so there is no client secret to paste.

3. Grant workspaces

   In your Dubot profile, open MCP connections and select the workspaces that client may access.

4. Author in Test

   Inspect configuration or create and update drafts. Write tools target Test.

5. Publish separately

   Review changes and dependencies before using an explicit Production publish tool. Publishing requires the appropriate admin role.

The authoring tool set covers workspace context plus wizards, actions, capabilities, brand, Test changes, and publishing. Tool calls still enforce the connecting user’s live organization role and current workspace grant.

A successful OAuth login without a workspace grant is intentionally insufficient. Calls fail closed until at least one eligible workspace is selected.

End-user action channel

The action channel exposes selected, published Session API actions to an end user’s AI client. Execution still occurs in that user’s signed-in product tab through the same customer-owned first-party executor used by wizard actions.

It requires:

• the workspace’s action channel to be enabled;
• a configured resume URL;
• selected published Session API actions with MCP enabled;
• a product page running the Dubot SDK;
• userId and a valid identityToken;
• the end user to approve the connecting client;
• a live eligible product tab when a tool is called.

Confirm-gated calls render an in-product Accept or Decline prompt. Completed calls appear in an action toast and remain subject to the published action version, input schema, response mask, and customer-side permissions.

The action channel is a controlled-rollout feature. Confirm workspace enablement, identity enforcement, resume behavior, and supported client before giving the URL to end users.

Do not cross the boundaries

• An authoring token is rejected by the action-channel host.
• An action-channel token is rejected by the authoring host.
• Documentation tools cannot use either authenticated surface.
• Authoring tools change Dubot configuration; action-channel tools run published customer operations.
• Revoking an end-user grant and revoking an authoring connection are different actions in different user interfaces.