What a connected AI assistant can do
The DeutschlandGPT capabilities an AI client such as Claude, Cursor or VS Code can use over MCP, and the permission each one needs.
An AI client you connect to DeutschlandGPT over MCP works in your name. It can do exactly what your role allows, and only what you granted it on the consent screen. Each area below is one permission group on that screen, with up to three tiers: Read to look things up, Edit to create and change, Delete & manage to also delete for good. A higher tier includes the lower ones.
How to connect a client is described in Wiki over MCP. Your organization may switch the MCP server off for its members, or allow nothing above a given tier. A permission it does not allow is not offered on the consent screen.
The consent screen
The consent screen shows one row per area and one column per tier. A box is missing where the client did not ask for that tier. The ⓘ next to an area or a tier explains it.
- Read only is ticked when the screen opens. Read and edit and Everything tick more at once; you can still change single boxes. Ticking a tier ticks the ones below it, unticking one unticks the ones above it.
- The line above the buttons says how many areas the client may read, edit and manage with your current choice.
- Allow and Deny stay visible however long the list is.
After Allow you see Connected with the areas you granted, and the browser goes back to the client. After Deny you see Access denied, and the client is told. You can then close the window. You can withdraw a client's access at any time under Connected apps.
Chats
| Tool | What it does | Tier |
|---|---|---|
chats_list | Lists your chats, most recently used first | chats.read |
chats_search | Searches your chats by title and, where enabled, by what was written | chats.read |
chats_get_messages | Reads the text of one chat; tool calls, files and images are left out | chats.read |
chats_share | Creates a share link for the organization or, if your role allows, public | chats.write |
chats_revoke_share | Turns a share link off | chats.write |
Incognito chats are never reachable. A project chat of a colleague can be read when you have access to the project, as in the app.
Projects
| Tool | What it does | Tier |
|---|---|---|
projects_list | Lists your own projects and those shared with you | projects.read |
projects_get | Reads a project: its instructions and its chats | projects.read |
projects_create | Creates a project, optionally with instructions | projects.write |
projects_update | Renames a project or changes its instructions | projects.write |
projects_move_chat | Moves one of your chats into a project or out of it | projects.write |
projects_delete | Deletes a project together with its chats | projects.manage |
Moving a chat into a project needs edit access to that project, because everyone in it can then read the chat.
Your account
Besides your profile, preferences and models, the account group covers:
| Tool | What it does | Tier |
|---|---|---|
account_use_prompt_template | Returns a saved prompt and counts it as used | account.write |
account_delete_prompt_template | Deletes a saved prompt for good | account.manage |
account_create_scheduled_task | Schedules a task, once or recurring | account.write |
account_run_scheduled_task_now | Starts a run of a scheduled task now, without a result mail | account.write |
account_list_task_runs, account_get_task_run | Lists the runs of a task and reads one result | account.read |
account_create_document_folder, account_update_document_folder | Creates or renames a knowledge folder | account.write |
account_list_document_folder_files | Lists the documents in a knowledge folder | account.read |
account_delete_document_folder, account_remove_document_folder_file | Deletes a knowledge folder or one document in it, for good | account.manage |
Documents are uploaded to a knowledge folder in the app. Deleting a scheduled task stays in Tasks.
Workflows
| Tool | What it does | Tier |
|---|---|---|
workflows_run_workflow | Starts a run by hand, also of a draft or switched-off workflow | workflows.write |
workflows_get_run | Follows a run: its status and each step's status, never its data | workflows.read |
A run uses the workflow owner's connections and counts toward your run limits. In an organization under professional secrecy (§ 203), only the editor starts a run, because it shows the required notice first.
Your organization (admins)
Admins can also manage the organization from a connected client. These tools need the separate permission Organization: manage (organization.manage). If your organization allows connected clients nothing above "read and edit", it is never offered.
| Tool | What it does |
|---|---|
organization_invite_members | Invites people by email with one role (organizations that sign in with email and password) |
organization_withdraw_invitation | Withdraws an open invitation |
organization_remove_member, organization_restore_member | Removes a member, or restores one while their data is still kept |
organization_set_member_role | Gives a member a role or takes it away |
organization_create_group, organization_update_group, organization_delete_group | Creates, renames or deletes a group |
organization_add_group_member, organization_remove_group_member | Adds a member to a group or removes one |
A client can do exactly what your role allows: nobody can hand out a role with permissions they do not hold themselves, and nobody changes their own roles. Members are named by their email address. Every change appears in the audit log like a change made in the settings.
Documentation
| Tool | What it does | Tier |
|---|---|---|
docs_search | Searches this documentation | docs.read |
docs_read | Reads one page as Markdown | docs.read |
You only find pages for the features you have. Without signing in, the public documentation MCP server offers the general pages.