> 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/release-notes/dublin-edition/dublin-6.0.0.md). # Dublin 6.0.0 Dublin 6.0.0 expands Autom Mate from workflow execution into outcome-oriented service delivery. The release introduces **Service Automation**, adds secure access through the [**Autom Mate MCP Server**](/userguide/mcp-and-ai-reference/connect-an-ai-client-with-mcp.md), and includes a focused set of security, permission, reliability, and usability fixes. ## Release overview | Item | Details | | ------------ | ------------------------------------------------------------------------------------------ | | Edition | Dublin | | Version | 6.0.0 | | Release date | 12.10.2026 | | Status | GA | | Availability | Autom Mate Cloud. The Dublin on-premises installer is not yet available (13 October 2026). | | Main areas | Service Automation, MCP Server, security, permissions, reliability, and usability | ## Highlights ### Service Automation: from request to verified outcome Service Automation introduces a dedicated **Execute** workspace for designing, deploying, operating, and measuring services. Each request becomes a traceable Service Case and follows the **Engage → Govern → Execute → Prove (E–G–X–P)** lifecycle. ### Reusable work items for E–G–X–P Use **Build > Work Items** to create reusable Hyperflows for the Govern, Execute, and Prove phases. These work items can then be connected to versioned service blueprints and reused across deployments. ### Versioned services and tenant deployments Service blueprints define the outcome contract and lifecycle of a service. Publish controlled versions, deploy them to tenant environments, and bind environment-specific variables, credentials, inputs, and resources without changing the blueprint. ### Operational visibility from Service Cases and Pulse Service Cases provide a complete journey, context, and log history for every service request. Pulse summarizes running, waiting, and overdue cases together with outcomes, outcome rate, and verified value. ### Secure AI access through MCP The new Autom Mate MCP Server connects Claude, ChatGPT, and other compatible clients to Autom Mate through OAuth. It exposes 14 tools and checks the authenticated user's permissions again for every call. ## New & improved ### Service Automation The **Execute** workspace adds the following areas: | Area | What it provides | | ------------- | -------------------------------------------------------------------------------------------------------------------------- | | Pulse | Operational metrics for running, waiting, overdue, started, and completed service cases, plus outcome and value reporting. | | Service Cases | End-to-end visibility into the Journey, Context, and Log History of each request. | | Services | Versioned, publishable service blueprints built around the E–G–X–P lifecycle. | | Deployments | Tenant-specific service copies with Development and Production stages and explicit version control. | | Foundation | Shared service capabilities, beginning with Global Variables. | ![Service Automation Pulse dashboard](https://4222414448-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMAf5diEa8kgXDA6h47Cu%2Fuploads%2F5S3rMgT3eJDqFxZE86SC%2Fservice-automation-pulse.png?alt=media) *Pulse provides operational and outcome visibility across service cases.* #### E–G–X–P lifecycle | Phase | Purpose | | ------- | ----------------------------------------------------------- | | Engage | Accept and normalize the incoming request. | | Govern | Check eligibility, rules, policy, and routing requirements. | | Execute | Deliver the requested service outcome. | | Prove | Independently verify the result and record evidence. | Each trigger creates a uniquely tracked Service Case. Govern, Execute, and Prove work items are created under **Build > Work Items**, then selected while designing the service flow. #### Service versions and deployments * Build the service definition and connect its E–G–X–P work items. * Review and publish a versioned blueprint. * Deploy the service to the appropriate tenant and stage. * Bind Global Variables, Engage body/query/header inputs, literal values, previous outputs, App or Vault credentials, and MateDrive resources during deployment. * Promote a tested deployment without silently changing existing tenant versions. #### Foundation Foundation provides shared capabilities that services bind to at deployment time. Dublin 6.0.0 includes **Global Variables**, including masking for sensitive values. ![Service Automation Foundation](https://4222414448-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMAf5diEa8kgXDA6h47Cu%2Fuploads%2FR7ugBis4dqA3TlWaQ0kO%2Fservice-automation-foundation.png?alt=media) *Foundation centralizes reusable values and prepares the platform for shared policy and SLA capabilities.* ### [Autom Mate MCP Server](/userguide/mcp-and-ai-reference/connect-an-ai-client-with-mcp.md) The Autom Mate MCP Server is available at: {% code collapsedlinecount="10" %} ``` https://mcp.autommate.app/mcp ``` {% endcode %} The connection uses OAuth on the Autom Mate side. The user enters the short Autom Mate workspace name, signs in with username and password, reviews the Autom Mate approval screen, and is redirected to the originating AI client after approval. The server currently exposes 14 tools. Every tool call enforces the authenticated user's current Autom Mate permissions. If a tool is visible but the user lacks the required permission, the operation is rejected—for example with **401 Unauthorized** for an unavailable read operation. See [Autom Mate MCP Server](/userguide/mcp-and-ai-reference/connect-an-ai-client-with-mcp.md) for configuration, screenshots, the complete tool list, permissions, security controls, limitations, and troubleshooting. ## Integration updates | Integration | Update | Authentication and permission impact | | ------------------------ | -------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | | Autom Mate MCP Server | New remote MCP endpoint with 14 tools for supported Autom Mate operations. | OAuth with PKCE; username/password sign-in only for this release; every call rechecks the user's Autom Mate permissions. | | Active Directory service | Updated the Go cryptography dependency to version 0.52.0 or later. | No configuration change expected. | | Excel service | Updated Excelize to version 2.11.0 or later. | No input or output contract change expected. | {% hint style="info" %} For library actions, use the action reference and check the inputs in your installed version before upgrading an integration. {% endhint %} ## Fixes * Search text no longer carries over when users navigate from one page to another in the left navigation. New pages open without an unrelated previous-page filter. * Agent metric timestamps are now handled consistently as UTC, preventing timezone offsets from delaying or distorting agent health states and MCP `agents_get_health` results. * The Active Directory service now uses `golang.org/x/crypto` 0.52.0 or later, addressing the reported critical dependency vulnerabilities. * The Excel service now uses Excelize 2.11.0 or later, addressing CVE-2026-54063 and reducing the risk of memory exhaustion from crafted XLSX files. * Updating an MSP technician's assigned role now persists the selected permissions instead of leaving the technician with full tenant access. * Users without Vault access can no longer view, create, or use Vault credentials from the Hyperflow builder. * Hyperflows with an existing App Credential no longer show a false “required field missing” error to users who cannot edit Vault credentials. * Disabling an action's error-handling flow now removes the inactive configuration correctly, preventing stale exported data and a blank screen after import. * Xurrent actions now process configured JSON body parameters correctly, preventing JSON format errors while preserving existing configurations. Input Preview may still display `bodyParams` as a string, but this does not affect execution. ## Known issues | Area | Known limitation | Workaround or guidance | | ---------------------------- | ------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | | MCP authentication | Microsoft sign-in is not supported for MCP connections. | Select **Sign in Using Credentials** and use an Autom Mate username and password. | | MCP tool discovery | An AI client may display a tool the connected user cannot execute. | The call is rejected when permission is missing. Ask an administrator to review the user's role and module permissions. | | Service Automation templates | Prebuilt service templates are not included in this release. | Create the service blueprint and phase work items manually. | | Foundation | Approval Policies, Access Policies, and Time & SLA are not yet available. | Use the controls available in the connected work items and deployment configuration. | | Human work | Dedicated human-task work items are not yet available. | Use Pause for Resume where a service must wait for a person. | | Skills binding | Skills cannot yet be bound as a deployment resource. | Use the currently supported variables, inputs, credentials, outputs, and MateDrive resources. | | Pulse | Some advanced analytics blocks may not yet be available. | Use the available case, outcome, and value metrics and inspect individual Service Cases for detail. | ## Compatibility & upgrade | Component or behavior | Dublin 6.0.0 guidance | | ------------------------- | -------------------------------------------------------------------------------------------------------------- | | Autom Center | Compatible with version 6.0.0 | | Mate Agent | Compatible with version 6.0.0 | | AI Agent | Compatible with version 1.5.3 | | Recommended upgrade order | Confirm the supported order in the release package compatibility information before production rollout. | | Service blueprint changes | Published versions are immutable; create and publish a new version. | | Existing deployments | Remain pinned and are not automatically upgraded to a new blueprint version. | | Rollback | Retain the previous deployment package and confirm environment-specific rollback constraints before promotion. | | MCP clients | Requires a client that supports remote MCP servers, Streamable HTTP, and OAuth. |