Connect Cassis for your whole organization

Every route uses https://app.getcassis.com/mcp/, and every question runs as the person who asked it, with their role and chat history. Give people access first.

Choose a route

Route	Who signs in	Choose it when
Company MCP gateway	Nobody	Your company runs an MCP gateway or internal agent
Claude organization connector	Each member, once	Your company uses Claude Team or Enterprise
ChatGPT workspace plugin	Each member, once	Your company uses ChatGPT Business or Enterprise
Repository config	Each developer, once	Engineers work in Claude Code or Cursor

Through a company MCP gateway

The gateway already knows who is asking and passes that identity on every request.

Ask Cassis to claim your company’s email domain. A person from a claimed domain who has no Cassis account is added as an Explorer on their first question; anyone else must be invited.
As an organization admin, open Settings → API keys, choose New API key, pick the Project, turn on Gateway key, and choose Create key. Copy the key into your gateway’s secret store; it is shown once.
Configure the gateway to call the endpoint with the key, and to name the asker on every request from your own sign-in, as below.

http

Authorization: Bearer sk-k6-...
X-Cassis-User-Email: firstname.lastname@example.com
X-Cassis-User-Name: Firstname%20Lastname

A gateway key covers one project, so several projects take one key each. It stops working when its creator stops being an admin and lasts a year at most, so plan its rotation. Header rules and refusals are in Gateway delegation.

A gateway key can act as any member on its project, admins included. Give it only to a gateway your company operates and authenticates people through.

In Claude

On Claude Team and Enterprise, an owner adds Cassis for the whole organization:

In Organization settings → Connectors, choose Add, then Custom, then Web.
Name it Cassis, paste the endpoint, and keep OAuth sign-in. Leave Request headers empty: a key there would make every member act as the key’s creator.
Each member opens Customize → Connectors, finds Cassis, and chooses Connect to sign in with their own account.

It then works in Claude on the web and Claude Desktop, and in Claude Code for members logged in with their Claude account. See Anthropic’s custom connector guide for the current screens.

In ChatGPT

On ChatGPT Business and Enterprise, a workspace admin adds Cassis as a plugin from Plugins, using Add custom MCP server with the endpoint and OAuth, then publishes it to the workspace. Set its installation policy to Installed to add it for everyone, or Available to let people install it. Each member connects once with their own account.

ChatGPT keeps the tool list it first saw, so an admin refreshes the plugin when Cassis adds a tool. See OpenAI’s custom MCP server guide.

In Claude Code and Cursor

Commit the server to the repositories your engineers work in: .mcp.json for Claude Code, .cursor/mcp.json for Cursor. Neither file carries a secret; each developer signs in once.

.mcp.json

{
"mcpServers": {
  "cassis": { "type": "http", "url": "https://app.getcassis.com/mcp/" }
}
}

.cursor/mcp.json

{
"mcpServers": {
  "cassis": { "url": "https://app.getcassis.com/mcp/" }
}
}

To give every Claude Code user the server regardless of repository, IT can add it to Claude Code’s managed MCP settings.

Check it

Have a colleague who was not part of setup ask a starter question from their own client. The answer should come with SQL, and the chat should be theirs, not yours.