Connect your AI client

Point any MCP-compatible client at your endpoint and authenticate either with a browser sign-in (OAuth) or with the X-Kapptivate-API-Key header. This page covers the common developer clients (Claude Code, Cursor, Claude Desktop, and GitHub Copilot). For Microsoft 365 Copilot Studio and Google Gemini, see their dedicated pages in this section.

Your endpoint

https://mcp.kapptivate.com/mcp

Sign in somewhere else and your endpoint carries the name of your environment. Take the first part of the address you sign in with, and put it after /t/:

https://mcp.kapptivate.com/t/<environment>/mcp

An account on acme.kapptivate.com connects to https://mcp.kapptivate.com/t/acme/mcp. Every example below carries the app.kapptivate.com address, so substitute yours before you copy one.

Get your API key

Open your profile

Copy your API key

Copy your personal API key. It carries the same access as your account. Workspace-level keys, scoped to teams, are managed under Administration > API keys.

Treat the key like a password. Prefer an environment variable over pasting it into a config file you might commit.

Prefer signing in with your browser? Clients that implement MCP authorization (Claude custom connectors, for example) can skip the API key entirely: add the server URL without any header and the client walks you through a browser sign-in (OAuth). This works with clients that carry MCP authorization natively, such as Claude custom connectors. It does not work through mcp-remote: that proxy requires dynamic client registration, which this authorization server does not offer, so it exits at startup with Incompatible auth server. Keep the API key for the Claude Desktop setup below.

Access scopes

A browser sign-in grants three scopes. An API key carries the full rights of your account.

Scope	What it allows
`read`	Browse every Kapptivate resource: tests, monitors, dashboards, metrics, robots
`write`	Create, edit and run those resources
`admin`	Privileged actions: shell commands on robots, restart and maintenance, incident closure

admin lets an assistant restart your robots, so read the consent screen before you approve it. To see what a client holds today, or to take it back, open https://<your-environment>/o/authorized_tokens/. Revoking there cuts off that client immediately and changes nothing else.

Configure your client

claude mcp add --transport http kapptivate https://mcp.kapptivate.com/mcp \
  --header "X-Kapptivate-API-Key: $KAPPTIVATE_API_KEY"

claude mcp list

Verify the connection

Ask your assistant for something read-only, for example: "List the operators I can access." If it returns results, you are connected.

Common errors

Connecting only proves the address exists. Your environment is resolved later, when a tool runs, so a client can report the server as connected and still fail on its first call. In its error messages, the server calls an environment a tenant.

A green connection status is not proof that your endpoint is right. Run the read-only check above.

What you see	What it means	What to do
401	No credentials, or credentials issued for another environment	Send your API key in the `X-Kapptivate-API-Key` header, or sign in through the browser, which carries an `Authorization: Bearer` session instead. Check that the key belongs to the environment in the URL.
404	The path is missing its `/t/` segment	Write `https://mcp.kapptivate.com/t/<environment>/mcp`, never `https://mcp.kapptivate.com/<environment>/mcp`.
400, `invalid tenant path`	The path carries a full address	Keep only the first part of your sign-in address, without `.kapptivate.com`.
Connects, then every tool call fails	The key and the path name two different environments	Line them up, then reconnect the client.

Still stuck? Write to support@kapptivate.com with the endpoint you used and the code you got back.

What's next?

Microsoft Copilot Studio

Connect from Microsoft 365.

Google Gemini

Connect Gemini, from CLI to enterprise.

Example prompts

What to ask once you are connected.

Core concepts

Operators, products, variables, and the safety model.