> For the complete documentation index, see [llms.txt](https://docs.autommate.com/userguide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autommate.com/userguide/start-here/documentation-scope-and-product-versions.md).

# Documentation scope and product versions

These guides cover Dublin Edition 6.0.0 and AI Agent Composer 1.5.3. Feature access depends on your edition, role, application connections and execution environment. Check the boundaries below before following an edition-specific procedure.

### Documentation scope

| Item                    | Coverage                                               |
| ----------------------- | ------------------------------------------------------ |
| Platform                | Dublin Edition 6.0.0                                   |
| AI Agent Composer       | 1.5.3                                                  |
| Edition-specific guides | Enterprise and MSP; follow the guide for your edition. |
| Access                  | Use the role required by the task.                     |

Enterprise screenshots illustrate Enterprise configuration. Follow the MSP guides for provider and tenant responsibilities. MCP response examples are labelled separately because they come from a connected MCP environment.

### Dublin 6.0.0 limitations

* Service designer: Engage supports one Webhook entry and one Schedule entry per service. Add at least one Execute Work Item before continuing.
* Work Items: select a released version for service use. A Dev version is not a released version.
* Foundation: Approval Policies, Access Policies, and Time & SLA are marked Coming soon. Identity and access policy are outside the service designer in this release.
* AI Agent Composer: configure a provider, model, authorized connections, knowledge, skills and channels for your use case. Test each connected capability before making the agent available to users.
* MCP: Dublin 6.0.0 introduces the server. The documented baseline contains 14 tools for discovery, inspection and existing API/webhook Hyperflow execution; their request declarations were rechecked on 20 October 2026. This baseline does not include dedicated Service Automation or create/edit/deploy Hyperflow operations. Check the active connection's tool list for the installed build rather than applying this count to every release. See [MCP capability scope](/userguide/mcp-and-ai-reference/capabilities-and-version-scope.md).

#### Check compatibility before using a procedure

[Dublin 6.0.0 release notes](https://docs.autommate.com/userguide/release-notes/dublin-edition/dublin-6.0.0) describe Dublin 6.0.0 and the MCP Server. As of 13 October 2026, the Dublin on-premises installer package is not yet available. Contact Autom Mate support before planning an on-premises upgrade.

Check your edition, build, signed-in role and application connection before starting. Use an account authorized for the task.

The MCP connection procedure covers an active cloud autommate.app workspace, using Sign in Using Credentials with Streamable HTTP and OAuth. Microsoft sign-in is not supported by this flow. For a 401 Unauthorized response, check the user’s Autom Mate role and module permissions. An on-premises MCP connection procedure is not included in this guide.

Use the [MCP Server guide](https://docs.autommate.com/userguide/autom-mate-mcp-server) for connection setup and the [MCP reference](/userguide/mcp-and-ai-reference/connect-an-ai-client-with-mcp.md) for exposed request fields and labelled response examples. These references define supported capabilities without relying on informal V1/V2/V3 labels.

For service configuration, use the [Enterprise deployment draft](/userguide/service-automation/create-an-enterprise-service-deployment-draft.md) and the [MSP deployment guide](/userguide/service-automation/deploy-a-service-to-msp-tenants.md) for their edition-specific scope.

Use [Troubleshoot service setup](/userguide/operate-and-troubleshoot/troubleshoot-service-setup.md) when a service prerequisite or entry point needs investigation.

### AI-assisted authoring and examples

[Build with an AI assistant](/userguide/mcp-and-ai-reference/build-with-an-ai-assistant.md) describes the create, test, fix and review lifecycle. Authoring steps require supported operations on the installed environment; they are not added to the 14-tool baseline by this guide. The [Jira-to-Xurrent](/userguide/mcp-and-ai-reference/use-cases-and-examples/jira-to-xurrent.md) and [reusable-tenant-service](/userguide/mcp-and-ai-reference/use-cases-and-examples/reusable-tenant-service.md) recipes define designs and acceptance checks, not completed executions in your environment.