Skip to main content
Dubot offers two MCP servers for different jobs. One reads the public documentation. The other works with an authorized Dubot workspace.

​
Choose the right MCP

The documentation MCP cannot inspect a customer workspace, change Dubot configuration, publish to Production, or run product actions. Use the protected product MCP for workspace administration.

​
Manage a workspace with the product MCP

Dubot provides a protected remote Model Context Protocol (MCP) server for authorized workspace administration. An MCP-capable client can use it to inspect Dubot configuration, prepare changes in Test, review what would be published, and publish approved configuration to Production.
Available now: The Dubot product MCP is live at https://app.dubot.ai/mcp. It requires OAuth authentication and an explicit workspace grant.

​
Connect

1

Add the remote server

In an MCP-capable client, add https://app.dubot.ai/mcp as a remote MCP server.
2

Complete OAuth

Follow the sign-in flow opened by the client. Dubot does not require you to paste an API key into the client.
3

Choose the workspace boundary

Grant access only to the Dubot workspaces the client should be able to inspect or manage.
4

Review before publishing

Keep authoring work in Test, inspect unpublished changes and their dependencies, then approve a separate publish operation when the intended Production change is clear.
The exact labels in the connection flow vary by MCP client. The server URL and Dubot authorization boundary stay the same.

​
What an authorized client can do

Publishing changes or brand configuration affects Production. Review the selected entities, dependencies, and target workspace before approving a publish operation in any MCP client.

​
What the MCP does not provide

The product MCP is Dubot’s authenticated configuration and publishing surface. It does not provide anonymous access, grant access to workspaces outside the OAuth consent, or turn the public marketing website into an action surface. The customer product remains the source of truth for product state and permissions. Product actions still follow the action policies and confirmation model described in Governance and security. Workflow recording in the browser extension is a separate way to discover candidate product actions. Recorded calls still require human review before they are added to the action catalog. See How Dubot learns a product.

​
Authorization and discovery

An unauthenticated connection starts the OAuth discovery flow. The server publishes protected-resource and authorization-server metadata so a compatible client can locate the authorization service, complete user consent, and retry with an access token.
Use the smallest workspace grant that supports the task. Remove the connection from the MCP client when it is no longer needed.

​
Read the docs from an AI client

Connect to https://dubot.mintlify.site/mcp when an AI client needs public product documentation rather than workspace access. This server is useful for questions about Dubot’s product model, integration contract, governance, workflow recording, and pilot process. It does not require a Dubot workspace grant.