IMPORTANT: This feature is available in public preview mode.
This article answers frequently asked questions about the regulatory classification of the Synerise MCP Server, how it processes data, and the responsibilities related to third-party AI clients. In this article, "Customer" means the organization that uses the Synerise Platform under an agreement with Synerise.
Regulatory classification
Is the Synerise MCP Server an AI system under the EU AI Act?
The Synerise MCP Server itself is an integration interface implementing the Model Context Protocol (MCP). It enables MCP-compatible external AI clients selected by the Customer to connect to the Customer's Synerise workspace and access permitted data and tools. The MCP Server does not itself provide the underlying AI model used by the connected external AI client.
Is the Synerise MCP Server a general-purpose AI (GPAI) model?
No. The Synerise MCP Server is not a general-purpose AI model. It is an integration interface that enables MCP-compatible external AI clients to access permitted data and tools within the Customer's Synerise workspace. The AI client connected by the Customer may separately rely on a general-purpose AI model provided by a third party.
Who is responsible for assessing the AI client connected to the Synerise MCP Server?
The Customer is responsible for selecting and assessing any third-party AI client connected to the Synerise MCP Server, including verifying the relevant provider's terms of service, including terms of data processing, and applicable AI Act and GDPR requirements. Synerise does not select, verify, or approve such third-party AI clients and does not control their processing of prompts, outputs, or Customer data.
Data processing
Does the Synerise MCP Server process the Customer's business or personal data, including profiles?
Yes, depending on the Customer's configuration, user permissions, and the tools used. The Synerise MCP Server may retrieve data from the Customer's workspace that contains personal data, including customer profiles, contact details, and event history.
Is the processing of personal data by the Synerise MCP Server covered by the agreement between the Customer and Synerise, including the applicable DPA?
Yes. The Synerise MCP Server operates within Synerise's infrastructure and is covered by the Customer's existing agreement with Synerise, including the applicable Data Processing Agreement (DPA).
Can personal data retrieved through the Synerise MCP Server be transmitted to a third-party AI provider?
Yes. If the Customer connects the Synerise MCP Server to a third-party AI client, data retrieved from the Customer's workspace may be transmitted to and processed by that third-party provider in order to generate a response. Such processing takes place outside Synerise's infrastructure and outside Synerise's control.
Does the agreement between the Customer and Synerise cover data processing performed by the third-party AI client selected by the Customer?
No. The agreement between the Customer and Synerise, including the applicable DPA, covers only processing performed by Synerise in connection with the provision of its services, including the Synerise MCP Server. Any processing performed by a third-party AI client selected and connected by the Customer is subject to the terms agreed between the Customer and that provider. The Customer is responsible for reviewing those terms and ensuring that appropriate contractual and data protection arrangements are in place.
Where is Customer data processed when using the Synerise MCP Server?
The Synerise MCP Server operates within Synerise's infrastructure. If the Customer connects a third-party AI client, data retrieved through the MCP Server may subsequently be processed within the infrastructure of that provider. The location of such downstream processing depends on the provider and service selected by the Customer and is outside Synerise's control.
Access control
What data can a connected AI client access?
The connected AI client may access only the data and tools available to the Synerise user account used to authenticate the MCP connection. The Synerise MCP Server acts on behalf of that user and applies the user's existing permissions within the relevant workspace; it does not grant additional rights, bypass access restrictions, or elevate privileges. Accordingly, the scope of access may differ between users and will change if the Customer modifies or revokes the relevant user's permissions. The Customer is responsible for assigning and regularly reviewing those permissions in accordance with the principle of least privilege.
The actions that connected AI clients can perform in a workspace are also limited by the Synerise MCP Server settings.
Agreement and usage
Is the Synerise MCP Server covered by the existing Synerise Agreement?
Unless otherwise agreed, the Synerise MCP Server is provided as part of the Synerise Platform and is subject to the existing Agreement, including applicable Terms and Conditions, limitations of liability, and other contractual provisions. Additional terms may apply to this functionality.
Please note that the disclaimers indicated in Data privacy and third-party AI clients also apply to the Synerise MCP Server.
Who is responsible for AI-generated outputs and actions performed through the Synerise MCP Server?
The Customer is responsible for reviewing and verifying AI-generated outputs before relying on them. Synerise does not guarantee the accuracy or completeness of such outputs. The Customer is also responsible for the configuration and authorized use of third-party AI tools connected through the Synerise MCP Server.
Is the use of the Synerise MCP Server mandatory, and how can the Customer enable this functionality?
No. The use of the Synerise MCP Server is entirely optional and remains at the Customer's sole discretion. This functionality will not be enabled or activated by Synerise without the Customer's explicit request or authorization. The Customer may choose whether and when to activate and use it.
Access for external AI clients is disabled by default. To enable it, a user with the PROFILE_ADMIN role changes the access level in the Synerise MCP Server settings.