The admin side: how to sign in, connect a GitHub repository, wire up MCP clients and Slack, and manage your organization. Most of this is done once by an org admin. If you just want to ask questions, head to Ask questions.
Access is limited to selected design partners today. Leave your email at getcassis.com to be notified when it opens up.
Sign in
The web app is at app.getcassis.com. Sign in with Google, or set a password through "Reset password" on the sign-in screen. Access is limited to design partners today.
Connect your warehouse
How Cassis reaches your data. Each project runs in one of two modes.
Warehouse-connected
Connect your warehouse and Cassis runs the generated SQL, returning the answer and the results.
Generate-SQL-only
No warehouse connection. Cassis grounds the question and returns the SQL for you to run. The cassis-snowflake-mcp workflow pairs it with the Snowflake MCP to execute.
Connect a GitHub repository
Back your ontology with git. Connect a repo and Cassis treats published versions as commits and reviews as pull requests, so ontology changes flow through the same review you already use for code. Connecting is optional; projects without a repo publish directly in Cassis.
How it works
Publishing opens a PR
With a repo connected, "Publish changes" opens or updates a pull request instead of applying the change right away. The version goes live in Cassis when the PR merges.
Pull from the repo
Import the ontology from the repo's main branch at any time (a full replace), so the repo can be the source of truth.
Stored in a cassis/ folder
Cassis keeps the ontology files in a cassis/ folder in the repo, so they live alongside your code (for example in your dbt repo) without taking over the root.
Bot identity
Commits and pull requests are made by the Cassis app (cassis[bot]), so they survive people joining or leaving.
Install the Cassis GitHub App
In the project's Git sync settings, pick the repository and, optionally, a folder, then start the connection.
Approve the Cassis GitHub App on GitHub for the repositories you choose. Installing it grants the permissions Cassis needs, so there is nothing to hand-assemble.
GitHub sends you back to settings, connected. No tokens to paste.
Permissions requested
Contents (read and write), Pull requests (read and write), and Metadata (read), on the repositories you select.
Connected before with a token?
Projects set up with a personal access token show as not connected until you reconnect once through the app. No data is lost.
GitHub only
Git sync supports GitHub. GitLab has no equivalent installable app, so it is not supported today.
Connect MCP clients
The Cassis MCP server lets analytics agents query your ontology from any MCP client. Add a new server with the endpoint below; the client opens a browser for OAuth, you sign in with your Cassis account, and you're connected. The token is stored and refreshed automatically, and an expired session just re-runs OAuth. For the tool definitions, see the MCP reference.
Endpoint
https://app.getcassis.com/mcp/
Transport
Streamable HTTP. No stdio mode.
Auth
OAuth 2.1 for interactive clients, or a long-lived API key for non-interactive agents and scripts (see Long-lived API keys). Active Cassis account, design partners only today.
Where to paste the URL
Claude Desktop
Settings → Connectors → Add custom connector.
Claude Code
claude mcp add --transport http cassis https://app.getcassis.com/mcp/, or /mcp inside the CLI.
Cursor
Settings → MCP → Add new MCP server.
Long-lived API keys
For agents and scripts that can't run a browser sign-in (LangChain, custom agents, scheduled jobs), an org admin issues a long-lived API key and passes it to the MCP server as a bearer token instead of running OAuth.
Who issues
An org admin, under Organization → API keys. Choose how long the key lasts (up to one year). The key is shown once at creation, then stored masked.
Scope
A key authenticates as the issuing user, within that user's organization. Revoke it any time from the same page.
How to send it
Keys start with sk-k6-. Send it as Authorization: Bearer sk-k6-... to the same MCP endpoint.
Install the Slack app
An org admin installs the app once for the whole organization. No server config, no environment variables, no dev work. For how your team asks questions once it's installed, see Ask in Slack.
Who installs
An org admin. In the web app, open Organization → Slack and click install. Slack runs its standard OAuth consent screen, you approve, and the workspace is connected.
Uninstall
The same Organization → Slack page. One click revokes the install and wipes the bot token. Channel mappings are preserved in case you reinstall.
Responds
Only when @-mentioned. Cassis never reads the channel-wide message stream, so you can discuss freely in a thread without it chiming in.
Connect channels to projects
On the same Organization → Slack page, map each channel to one Cassis project, then invite the bot into the channel. A channel maps to exactly one project; that's how the bot knows what to answer about.
Slackacme.slack.com connected
Uninstall
Channel
Cassis project
#race-analytics
Formula 1
✕
#strategy
Formula 1
✕
+ Add binding
Accounts and access
Every Slack user who @-mentions the bot needs a verified Cassis account in the workspace's organization, matched by email. Anyone without one gets a one-click path to set up, without leaving Slack.
No account yet
Cassis replies in the thread with the admins who are in that channel. The requester picks one, and that admin gets an "Approve & create account" button right in the thread. One click creates the teammate's account (no password needed; they sign into the web app later with Google) and answers their original question immediately.
Guests
If the requester is a Slack guest, the approving admin sees a warning before vouching for them.
No admin in the channel
Cassis lists the organization's admins by name so the requester knows who to ask.
Manage your organization
Org admins get an Organization area in the sidebar.
Users
Everyone in the organization: name, email, role (member or admin), and status. Changing a user's role is handled by Cassis staff during the design-partner phase.
Conversations
Browse every chat in any project and open it. Reading colleagues' chats is allowed; authoring stays with the chat's owner.
Slack
Install the Cassis Slack app and map each channel to a project. See Install the Slack app above.
GitHub
Install the Cassis GitHub App for the organization and manage the repositories it can reach. One install covers every project; each project still picks its own repository. See Connect a GitHub repository.
API keys
Create and revoke long-lived API keys for non-interactive MCP access. See Long-lived API keys.
Project settings
Review and manage every project in the organization from one place.
Want to try Cassis?
Access is limited to selected design partners today. Leave your email to be notified when it opens up.