MCP Server Integration
In preeco | datenschutz, AI assistants can be connected directly to existing data via the Model Context Protocol (MCP). This allows, for example, querying processing activities or exporting revisions without having to open the application. Configuration is done in the profile section under "Integrations" and includes server URL, API token, and an overview of available tools. The same access rights apply as in the application, so only authorized data can be retrieved.
Via the Model Context Protocol (MCP), AI assistants can be connected directly to the data in preeco | datenschutz. This allows, for example, querying processing activities, listing teams, or exporting revisions as PDF without having to open the application itself. Configuration is done under "User profile > Integrations".
Via the "Download .mcpb file" button, a preconfigured file can be downloaded that simplifies setup in the AI assistant.
Via "Edit", the MCP server settings can be adjusted.
MCP server activated: Indicates whether the MCP server is active for your organization.
Server URL: The individual URL of the MCP server. This can be copied via the button next to it and pasted into the respective AI assistant.
API token: Generated upon first connection. The token is only displayed once when created and cannot be viewed again afterwards. It must therefore be saved immediately after creation. An expiration date can be set for the token. If no date is specified, the token does not expire.
Available tools: Lists the functions available to the AI assistant via the MCP server. These include, among others, retrieving teams, listing and viewing processing activities, and exporting revisions as PDF.
Changes and errors may occur. The information in this article has been carefully compiled, but does not claim to be complete or correct.