Providers
Each provider decides how you supply its credential and what a connection to it can be used for. The Can be used for column shows what each provider supports. A new connection starts with the provider’s usual capability, and you change which ones it holds under Edit.
Cloud and infrastructure
Section titled “Cloud and infrastructure”| Provider | Credential | Can be used for |
|---|---|---|
| AWS | Access keys: an access key ID and a secret access key. A default region comes with it, and a workflow step can override it. | Workflows, AI |
| Azure | A service principal: directory (tenant) id, application (client) id, client secret, and a default subscription id. | Workflows |
Both allow more than one connection, so a production account and a staging account are two rows.
The IAM policy on the AWS keys, or the Azure role assignment, decides what a step can do with the credential. There’s no second permission list inside KloudMate, so narrow the policy or the role itself, and create a separate connection with its own keys for each job. Gate risky steps with an approval.
Chat and issue tracking
Section titled “Chat and issue tracking”| Provider | Credential | Can be used for |
|---|---|---|
| Slack | OAuth install. | Notifications, Workflows |
| Jira Cloud | OAuth through Atlassian. | Notifications, Workflows |
| Microsoft Teams | The KloudMate app, added to a team in Teams. One connection per team. See Microsoft Teams Integration. | Notifications |
One Slack install serves alert notifications, incident ChatOps, the Slack workflow actions, and Slack event triggers. A Slack or Jira Cloud connection made in Settings → Connections starts out used for Notifications. Add Workflows under Edit before a workflow step or trigger can use it, and reconnect it if it’s then marked Needs reconnect.
One Jira credential can access several Atlassian sites, which is why every Jira action and trigger starts with a site picker.
Meetings
Section titled “Meetings”These create the conference call for an incident war room. The war room settings list only connections that can be used for Meetings.
| Provider | Credential | Can be used for |
|---|---|---|
| Google Workspace | Google sign-in, as the Workspace account that should own the meeting spaces. | Meetings |
| Zoom | An install of the KloudMate app, from a Licensed Zoom account. See Zoom. | Meetings |
Meetings hosted by a Basic Zoom account end after 40 minutes, so install the Zoom app from a Licensed account. See Set up war rooms for what each provider adds to a room.
Tools and custom endpoints
Section titled “Tools and custom endpoints”| Provider | Credential | Can be used for |
|---|---|---|
| Custom MCP Server | A server URL, a transport of Streamable HTTP or SSE, and one Authentication option: None, Bearer token, Basic auth (a username and a password or API token), API key (sent in a header you choose), or OAuth (sign in on the server’s own page). Extra headers can be sent alongside, for a server that wants a routing header as well as a credential. | Workflows, AI |
| OAuth 2.0 | Your own authorize and token URLs, scopes, client id, and client secret, with either the client-credentials or the authorization-code grant. | Workflows |
Use OAuth 2.0 to give an HTTP Request step a credential that’s refreshed for you and never stored in the workflow definition.
AI assistant tools
Section titled “AI assistant tools”These connect an MCP server that the KloudMate Assistant can call as a tool. They can be used for AI only. Any connection that’s used only for AI can be private, including an AWS or Custom MCP Server connection.
| Provider | Credential |
|---|---|
| GitHub | A GitHub token. |
| Atlassian | A scoped personal API token or a service account API key. See Atlassian. |
| Sentry | OAuth. |
| Google Cloud BigQuery | Google OAuth. |
| Google Cloud Compute Engine | Google OAuth. |
| Google Cloud GKE | Google OAuth. |
| Google Cloud Logging | Google OAuth. |
| Google Cloud Monitoring | Google OAuth. |
| Google Cloud Resource Manager | Google OAuth. |
An Atlassian personal API token needs the agent-interface scopes for the tools you want, such as read:jira:agent-interface. A token with only REST API scopes can’t call tools. Before either kind of Atlassian credential works, an Atlassian organization admin must allow API tokens under Atlassian Administration > Rovo > Rovo MCP server > Authentication.
AWS and Custom MCP Server can also be used for AI. See the tables above.
Providers in your plan
Section titled “Providers in your plan”Your plan decides which providers you can connect. The Connect picker shows only the providers your plan includes and the platform currently offers. If you expect a provider but can’t see it, either your plan doesn’t include it or the platform doesn’t offer it right now. Upgrading fixes only the first.
The platform can also offer a provider for some uses and not others. If a provider appears in the picker but you can’t grant it the capability you wanted, the platform doesn’t offer that capability for it right now.
If the platform stops offering a provider, or one of its uses, only new connections are affected. Existing workflows, dashboards, and notification channels keep working.
Link your Slack account for ChatOps
Section titled “Link your Slack account for ChatOps”One Slack step is done per person, not per workspace. After someone with the Developer role connects Slack and adds a ChatOps channel, each responder links their own Slack account before they can acknowledge or resolve incidents from Slack.
Open Incidents → Settings, find the Slack panel of the ChatOps card, and under Your account click Connect account. This step needs the Developer role. It’s a one-time step that links your KloudMate account to your Slack user.
Everyone links their own account, because KloudMate has to match the Slack user who pressed a button to a workspace member before it acts.
See Slack Integration for the full setup.