Connect an AI assistant

Use Deutsche Cloud from Claude, Cursor, VS Code, ChatGPT or any client that speaks the Model Context Protocol (MCP).

Deutsche Cloud runs an MCP server. Add its URL to your assistant, sign in once on a Deutsche Cloud consent screen, and the assistant can list, describe, create and change resources for you, with exactly your IAM permissions and nothing more. Every call it makes goes through the same permission check and audit log as a click in this console.

Connect in one step

Copy the server URL into your app, or use a one-click install. The first time the app connects, it opens a browser window where you sign in to Deutsche Cloud and choose what it may do.

Server URL

https://console.platform-development.deutschecloud.app/api/mcp

Claude Code

claude mcp add --transport http dcloud https://console.platform-development.deutschecloud.app/api/mcp

Then run /mcp inside Claude Code and choose dcloud to sign in.

Claude (claude.ai and Claude Desktop): Settings → Connectors → Add custom connector, paste the server URL, then Connect. ChatGPT and other apps: add a custom MCP connector or remote server with the same URL. Every app signs in through a Deutsche Cloud consent screen, so there is no key to paste.

Client by client

Claude (claude.ai and Claude Desktop)

Open Settings → Connectors → Add custom connector. Name it Deutsche Cloud, paste the server URL and save, then press Connect. Claude opens the Deutsche Cloud consent screen; after you allow it, the Deutsche Cloud tools appear in the tools menu of a chat. On Team and Enterprise plans an owner may need to add the connector for the organization first.

Claude Code

Add the server

claude mcp add --transport http dcloud https://console.platform-development.deutschecloud.app/api/mcp

Then run /mcp in Claude Code, pick dcloud and choose Authenticate. Add --scope user to make it available in every project.

Cursor

Use Add to Cursor above, or add this to ~/.cursor/mcp.json (or .cursor/mcp.json in a project). Cursor shows a Needs login button for the server; press it to sign in.

mcp.json

{
  "mcpServers": {
    "dcloud": {
      "url": "https://console.platform-development.deutschecloud.app/api/mcp"
    }
  }
}

VS Code (GitHub Copilot agent mode)

Use Add to VS Code above, or run MCP: Add Server from the command palette, choose HTTP and paste the URL. VS Code asks you to allow the sign-in, then opens the consent screen.

.vscode/mcp.json

{
  "servers": {
    "dcloud": {
      "type": "http",
      "url": "https://console.platform-development.deutschecloud.app/api/mcp"
    }
  }
}

ChatGPT

Add a custom connector (in Settings → Apps & Connectors; depending on your plan, custom connectors may first need developer mode turned on), choose OAuth authentication and paste the server URL. ChatGPT discovers the sign-in endpoints by itself.

Any other MCP client

Any client that supports remote servers over Streamable HTTP with OAuth works: give it the server URL and nothing else. It finds the sign-in endpoints from the server’s discovery documents.

What the assistant can do

On the consent screen you choose the organization and the most the app may ever do. Read-only is preselected:

  • Read-only: list and describe only. No changes, no secret values and no source code, even where your policies would allow them.
  • Can ask to make changes: create and change resources, never delete, overwrite, stop or revoke.
  • Can ask to change and delete: also the destructive calls, each with a plan and a confirmation.

Never more than your IAM policies allow, in that organization: if your policies cannot delete a database, neither can the assistant. The app acts as your IAM user, so its calls show up under your name in the audit log, each tagged with the agent session, the client and the tool. Being removed from the organization, or having your IAM user deactivated, disconnects every app you connected there at once.

Agent sessions: read-only until you allow more

Whatever the connection allows, every agent session starts read-only. A session is one run of the assistant: restarting it starts a new one, and a session idle for 30 minutes ends.

  • You allow more, per session. The assistant calls dcloud_session_request_access with what it wants to do and why, and gives you a link to IAM → Agent sessions. There you allow writes (15 minutes, 1 hour or 8 hours) or destructive calls. Only a person signed in to the console can do that; an access key or a token cannot, so an assistant cannot raise its own session.
  • Every write can be planned. With "dryRun": true a tool returns the request, the target’s current state, what still depends on it, and the cost per hour and month, without changing anything. Planning works in a read-only session.
  • Destructive calls need a confirmation token. Deleting, overwriting, stopping or revoking never runs on the first call: it returns the plan and a token good for five minutes (30 while it waits for your approval), once, for exactly those arguments. If the target changed in between, the token is spent and the assistant has to plan again. If the session may not destroy, you can approve that one call on the agent sessions page instead of the whole session.
  • Rate limits per agent: 120 tool calls a minute, 30 writes a minute and 10 destructive calls per 10 minutes by default, counted per connection; an administrator changes them on the same page.
  • Kill switch. An administrator can switch off changes by every agent in the organization at once; reads keep working.

The agent sessions page lists every session with its client, what it may do and until when, who allowed it, and its calls, writes and refusals. End a session, or revoke its connection: a connected app is disconnected, an access key is refused by this server from then on.

Seeing and disconnecting apps

My account → Connected apps lists every app you connected, with its access level, organization and when it was last used. Disconnect revokes it immediately. An app you do not use for 30 days has to sign in again.

Headless agents and CI

A script, a CI job or an agent with no browser cannot click through a consent screen. Give it an access key instead, ideally for a dedicated IAM user with only the permissions it needs, and send it as a header. Its sessions start read-only and follow the same rules as above. The key itself still works for the API and the CLI, so an agent that can read it can step around this server; where that matters, connect with OAuth instead, whose tokens are read-only anywhere but here.

Claude Code with an access key

claude mcp add --transport http dcloud https://console.platform-development.deutschecloud.app/api/mcp \
  --header "Authorization: EWS-ACCESS-KEY EWS1…:<secret>"

Documentation only, no sign-in

A second server answers questions about Deutsche Cloud from this documentation and does nothing else. It needs no account and no sign-in, so an assistant can use it in a repository where nobody has signed in, or before you have an organization. Its tools are dcloud_docs_search (search every page, with links to the matching section) and dcloud_docs_read (read a page or one section as markdown). The server above has the same two tools next to the resource tools, so a signed-in assistant needs only that one.

Docs server URL

https://console.platform-development.deutschecloud.app/api/mcp/docs

Claude Code

claude mcp add --transport http dcloud-docs https://console.platform-development.deutschecloud.app/api/mcp/docs

In Claude, add it as a custom connector with the same URL and no authentication. Requests are limited per address to keep the server fast for everyone.

For client developers

Everything a client needs is discoverable; these are the details for the curious.

  • Transport: Streamable HTTP at https://console.platform-development.deutschecloud.app/api/mcp, POST only. Protocol revisions: 2026-07-28 (stateless, server/discover) and the initialize handshake for 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05.
  • Tools: one per API operation, named dcloud_<service>_<resource>_<operation>, filtered to what the caller may do. The API & CLI reference lists the same operations.
  • Authorization: OAuth 2.1 with PKCE (S256 only). Metadata at https://console.platform-development.deutschecloud.app/.well-known/oauth-protected-resource/api/mcp and https://console.platform-development.deutschecloud.app/.well-known/oauth-authorization-server. Clients may identify themselves with a Client ID Metadata Document (preferred) or register dynamically.
  • Scopes: ews:read and ews:write. Tokens are bound to the server URL (RFC 8707). Access tokens last 60 minutes; refresh tokens rotate on every use, and reusing an old one revokes the connection.