Release R26-1 #
Available from 20th January 2026
Highlights #
MCP Servers – new feature to enable agentic usage of Cyclr Connectors
We have introduced a new product to Cyclr: MCP PaaS. With MCP PaaS, you can create MCP Servers for agentic use of your company’s native Cyclr Connectors, with controls for Method exposure, data minimization, connection security, and transaction auditability.
Learn more in our Documentation, or at mcppaas.com. If you’d like to discuss adding MCP PaaS to your existing Cyclr subscription, please get in touch with your Cyclr representative.
Cyclr API – new POST /v1.0/account/connectors/{accountConnectorId}/getSetupLink endpoint
We’ve added a new endpoint to the Cyclr API which performs the same function as the interface’s Generate Setup Token feature. This enables you to generate details from Cyclr to pass on to someone externally so they can authenticate an existing Account Connector. Avoids them needing access to Cyclr or to share their credentials directly with you. With this endpoint, you could now automate obtaining these details within your own application.
Webhook Steps – can be secured using OAuth 2.0
Alongside Cyclr’s new MCP Servers feature comes Account-level OAuth Client Credentials. This allows certain Webhook Steps to be secured using the OAuth 2.0 Client Credentials flow, and Cyclr will ensure that a provided access token is valid before accepting a request.
See Securing Cyclr Webhooks for more information.
Improvements #
Accounts > Connectors > Generate Setup Token – restored restricted access
Resolved a new situation where it was possible for someone given access to authenticate a Connector through the Generate Setup Token option to go beyond that after authenticating where they could see other Connectors.
Connectors > Authentication – installed Connectors could become unusable if authentication wasn’t completed
If a Connector’s Authentication has multiple pages to complete, stopping partway through could previously result in that instance of the Connector becoming unusable, requiring it to be deleted and reinstalled.
Connectors > Custom Object Method Categories – improved icons
The icons shown within Cyclr’s interface around Custom Object Method Categories and their Methods have been updated, along with a small change in where they are positioned.
Console > Data Retention – minor interface improvements
When viewing the Console level Data Retention settings, the error messages have been improved when setting a “0” retention period for either Successful or Errored Transactions. When re-enabling either options, a default of 31 Days is also now used.
Console > GitHub Integration – import Templates over 1 MB in size from GitHub
Can now import Cyclr Templates that are over 1 MB in size from GitHub repositories back into a Cyclr Console using the GitHub Integration feature.
Console > Message Center – included the year in dates shown
Messages shown on the Console Dashboard include the date they were sent, and that now includes the year too.
Console > Task Usage – a Cycle’s “On Step Error” setting could prevent Incidents being logged
Corrected Incident Tasks not being recorded when a Template/Cycle is using the “Stop the transaction” option of the On Step Error setting.
Console > Templates – Collection Mappings retained when using Custom Fields
When installing a Template, if Custom Fields were used within a Step’s Collection Mapping options – which tell Cyclr how 2 collections of data relate to each other – those Collection Mapping options would not be retained in the newly created Cycle. That has been resolved in this Release so the Collection Mappings are now retained.
Console > Templates – upgrading a Cycle could create duplicate Versions
Resolved the situation that in some cases it was possible for 2 new Versions of a Cycle to be created when upgrading to the latest Release of a Template.
Cycle Execution – DateTime values now default to ISO 8601 format within application/x-www-form-urlencoded requests
When building an HTTP Request to be sent using a Content-Type of application/x-www-form-urlencoded, if a Request Field uses the DateTime Data Type and no Format has been specified, the value provided will now default to ISO 8601 formatting. Previously it was simply serialized so was in an undefined format.
Cycle Execution – internal memory usage improvements
We’ve made some internal changes in how Cyclr executes a Step when running a Template or Cycle so that less system memory is used.
Cyclr API – deprecated XML support
Support for XML by the Cyclr API has been deprecated so requests which use a Content-Type HTTP Header of application/xml or text/xml or XML content within a request body are no longer accepted. This doesn’t affect Cyclr’s ability to make calls to external systems where XML is used in either the request or the response.
Cyclr Interface – automatic loading of supporting files after new Cyclr Releases live
Small update so web browsers automatically retrieve new versions of files relating to the Cyclr interface after a new Cyclr Application Release is live.
Cyclr Interface – changed paging controls
When viewing lists of data, such as Transactions, the paging controls to move between pages have been changed from a dropdown (which listed all pages and could be unwieldy in some situations) to a textbox, still allowing you to jump to a specific page.
Cyclr Interface – deleting a Folder no longer opens it first
Previously, selecting the Delete button on a Folder within the Console or an Account would confusingly also open it before displaying a confirmation to delete it.
Embedding > Marketplaces – corrected image caching issue
When building a Marketplace and selecting an existing image to use on a Card, an issue with the caching could have resulted in images within the Logo Library appearing repeated many times.
Webhook Processing – queuing system disconnections resolved
When processing received requests to Cyclr Webhooks, we have identified and resolved an issue where the internal queuing system could – in certain situations – become disconnected, resulting in delays in processing. Changes have been made to automatically reconnect and continue should that occur.