Managing plugins
Data protection, costs, plugins on request, retirements and apps on the plugin page, and who sets up what in the workspace.
Plugins connect MeinGPT to other systems, such as Google Drive, Jira or your own MCP server. You manage them under Settings → Knowledge & integrations → Plugins. Every plugin has its own page there.
This page explains what a plugin page shows about data protection, costs and availability, and who sets up what in the workspace. How you decide which plugins and functions are allowed is described under Tool Access Policy.
Data protection
Every plugin page has a Data protection section. It always says where the rules for data from plugins are set out: in the platform Privacy policy, the DPA and the list of Subprocessors.
Once a plugin's details have been legally reviewed, the section also says who processes the data and under which contract:
| Statement | Meaning |
|---|---|
| Runs entirely within MeinGPT | Your data processing agreement with MeinGPT applies. |
| Processed by a provider as a subprocessor of MeinGPT | Your data processing agreement with MeinGPT applies as well. |
| Runs through your own account at the provider | Your contract with the provider governs processing there, for example with Google or Microsoft. |
| Runs on your own system | You are responsible for the data there. |
| Calls an external service | The provider's terms and privacy policy apply. |
| Added or run by your workspace | Your workspace is responsible for processing, for example for workspace MCP servers and Outpost services. |
Next to it is the place of processing, as far as the provider states it: Germany, Austria, EU, EU and USA, USA, USA (DPF) for the EU-US Data Privacy Framework, "Depends on model" or "Depends on account". "Depends on account" means you set it in your account at the provider. Where available, the section links the provider's privacy policy and terms.
Costs
Most plugins cost nothing extra. Some use credits every time they are used, for example the image generator. Once the details for such a plugin have been reviewed, it carries the Credits per use marker in the data protection section. How many credits it uses depends on the chosen model; prices are listed under All Models.
Plugins on request
Some plugins are not part of your workspace's standard scope. They are listed in the overview under On request.
Request
Click Request on the plugin and confirm. MeinGPT gets back to you with a price and terms. Until then, the plugin shows Requested.
Booking by MeinGPT
Once booked, MeinGPT switches the plugin on for your workspace.
Release
You then release the plugin like any other, depending on the Who installs setting.
If a request is not booked, the plugin shows Not booked · request again. As long as a plugin is not booked, it can neither be installed nor connected.
Retired plugins
When a plugin is discontinued, its page shows Retired on … and, if there is one, the Successor. Where the plugin is installed or in use, it keeps working until that date. It can no longer be newly installed.
Plugins as apps
Some plugins are also available as their own app in the sidebar, currently Images (image generator) and Web search. It is the same product as in chat.
On the plugin page, As an app switches whether it appears In the sidebar or is Hidden. Who may use the app is set under Settings → AI & features → Apps.
Who sets up what
| Who | Sets up |
|---|---|
| Admins | Who installs plugins, the default permission, which plugins are installed or blocked, use as a knowledge source, rules for custom MCP servers, workspace MCP servers, plugins as apps, requests for plugins on request |
| Members | Their own account for a plugin, installing allowed plugins (with Members themselves), custom MCP servers (if allowed) |
| Editors of an assistant | Which plugins the assistant uses, which of their functions, and which folders or projects it may access |
| MeinGPT | Booking plugins on request |
For accounts: everyone connects their own account, usually when adding the plugin to an assistant. There is no shared account for the whole workspace for plugins yet.
Attention
The exception is custom MCP servers with a fixed API key. If someone adds such a server to an assistant, everyone who uses the assistant uses that key too. See Custom MCP Server.