Your connectors in a connected AI assistant
How an AI client such as Claude or ChatGPT uses the services you connected in DeutschlandGPT (Jira, Outlook, MCP servers, WebDAV) over MCP, which permission it needs and which rules apply.
An AI client you connected to DeutschlandGPT over MCP can also use the services you connected here: built-in integrations such as Jira, Outlook or Confluence, MCP servers and WebDAV. It works with your own account in each service, under your organization's rules and your own permissions. Your access data stays in DeutschlandGPT; the client never sees it.
Two tools, whatever you connected
The client always gets the same two tools, however many services you connect:
| Tool | What it does |
|---|---|
connectors_search | Finds the tools of your services that fit a task, each with its address, its parameters and the tier it needs |
connectors_call | Runs one tool by its address, for example jira:createIssue, with the parameters it needs |
If you have several connections to one service, the client names the one to use. A tool that would be refused is marked as refused in the search results, with the reason.
The Connectors permission
On the consent screen, Connectors is one row with three tiers. Which tier a tool needs depends on the tool, not on you:
| Tier | Covers |
|---|---|
| Read | Searching your services and tools that only read, from a built-in integration or from an MCP server DeutschlandGPT has reviewed |
| Edit | Also tools that create or change something, such as creating a Jira issue or sending an e-mail. Every tool of an MCP server you added yourself counts as this tier, also one that says it only reads |
| Delete & manage | Also tools a reviewed provider marks as destructive |
As everywhere on the consent screen, only Read is ticked when it opens.
Which rules apply
Every call is checked again when it is made, so a change applies at once, also to clients already connected.
- Your organization decides whether connected clients may use members' connectors at all (off by default), and the highest tier a client may be granted. A tool it blocked is refused. A tool it set to require a confirmation is also refused here, because DeutschlandGPT cannot see the client's own confirmation. Use such a tool in a DeutschlandGPT chat.
- Your permissions: a tool or service you set to Never allow is refused.
- Ask every time: by granting Edit or Delete & manage on the consent screen, you already answered the question for a built-in integration or a reviewed MCP server, so the tool runs. For an MCP server you added yourself it is refused instead, because nobody can confirm it there. To use such a tool from the client, set it to Always allow under Permissions, or use it in a DeutschlandGPT chat.
- A service your organization turned off for you is refused.
A refusal tells the client the reason in words it can pass on to you, and that trying again will not help.
For administrators
Under Tool policies, in the section Connected AI assistants, the switch Apps may use members' connectors turns this on for your organization. It is off by default and needs Members may connect AI assistants. Turning it off cuts off clients that are already connected at their next call. Your rules for single tools and the highest access an app may be granted apply on top.
Every call through a connected client is recorded, like the calls from the chat: who made it, which service and tool, and how it ended. The parameters and results are not recorded.