Skip to main content

​
At a glance

  • Availability: Experimental (how to enable).
  • Authentication: API key.
  • Connection: The key from STACKIT_SERVICE_ACCOUNT_TOKEN is sent as the Bearer prefixed Authorization header.
  • Provider documentation: Authentication reference.

​
Credentials

Set these per environment. See Connect an integration.

​
Setup

  1. Get a STACKIT account and project: STACKIT is a B2B cloud by Schwarz Digital - request an organization at https://www.stackit.de, then create a project in the STACKIT Portal (https://portal.stackit.cloud).
  2. Create a service account with a key: In the Portal, open your project > Service Accounts, create one, assign it a role (e.g. reader), and create a service account key (key flow). The legacy static token flow was removed on 17 December 2025.
  3. Obtain a short-lived access token: Exchange a self-signed JWT (signed with the key’s private RSA key) at the service account token endpoint, or simply run the STACKIT CLI: ‘stackit auth activate-service-account —service-account-key-path key.json’ and export the resulting access token.
  4. Set the environment variable: Put the access token into your .env as STACKIT_SERVICE_ACCOUNT_TOKEN.
  5. Verify access: Run List Projects with member set to the service account’s email, then List Servers for a returned projectId in your region (e.g. eu01).

​
Provider notes

  • Access tokens from the key flow are short-lived (refresh roughly every 10 minutes) - automate token renewal for long-running agents
  • List Projects requires at least one filter: containerParentId (organization/folder) or member (email)
  • The IaaS API v2 is the stable release; v1 is deprecated and will be removed after 1 March 2027
  • IaaS URLs are region-scoped via the {region} path segment, e.g. eu01
Provider API reference.

​
Tools

​
Verify the connection

Call a read tool such as stackit__list_projects with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.