Kater meets your teams where they already work. Business teams ask their own AI agent or Slack, data teams build in VS Code, and admins point Kater at the warehouse and, if they want, at GitHub. Each integration uses the same governed definitions, so a figure reads the same everywhere.

AI agents

Connect the agent you already use to your organisation’s Kater MCP. Each person signs in with their own Kater account. The agent then answers from your data, builds apps and asks before it changes anything. An admin selects which AI providers people can use, and adds Kater for everyone in Claude and ChatGPT, on Set up the Kater MCP.

For every tool, prompt and rule your agent gets, see MCP server and tools. To ask your agent about the Kater page you have open, see Ask Kater MCP.

Slack

Ask your data assistant from Slack, and get DMs from Kater when an answer, a schedule or a request is for you.

Data and code

What each one is for

Integration	Use it to	Who sets it up
AI agents	Ask questions, build apps and workspaces, and fix queries in the agent you already use	Each person, in about a minute
Slack	Ask from Slack, and get answers, scheduled figures and requests as DMs	An admin installs the app. People connect by email or with Connect
Warehouses	Give Kater the data to model and query: Snowflake or DuckDB	An admin, during onboarding or with the Kater CLI
VS Code	Write and run Kater SQL next to your other files, in a local copy	Each person on the data team
GitHub	Keep a copy of the shared layer in your own repository, for review and CI	An admin. It is optional

Your own access, everywhere

Kater never gives an integration a shared account. Each one works as a person, and Kater’s access rules apply to that person.

• AI agents. Each person signs in with their own Kater account. Their agent reads only what they can read, and asks before it changes anything outside their brainstorm folder.
• Slack. A question uses the asker’s own Kater sign-in. Before Kater posts a DM, it checks that the recipient can read everything in it.
• VS Code. The extension signs in as you, and your local copy holds only what you can read.
• Warehouses. Kater keeps the warehouse credential, encrypted for your organisation. Queries run on Kater’s server, only from content the person can read. No agent, editor or person sees the credential.
• GitHub. Write-back is one-way and publishes only the shared layer. Nothing is read back from GitHub.

Next steps

• Connect your agent
• Set up Slack
• VS Code extension
• GitHub
• Connections and schema sync