Skip to main content
If your question isn’t here, reach out to hello@klarity.ai.
The most common cause is that the MCP hasn’t been enabled in your Klarity workspace yet. Both OAuth and API-key auth require this one-time setup:
  1. Log in to Klarity in a browser.
  2. Go to Settings → MCP.
  3. Pick the workspace you want to expose and complete the in-app setup.
Then retry the sign-in or Bearer-token request from your AI client. See Authentication → Enable the MCP in your workspace for the canonical reference.
Not directly. Klarity is a commercial service — you need an active workspace and a provisioned user account to use the MCP. Contact hello@klarity.ai to talk about access.
Your organization’s Klarity workspace admin needs to approve the Klarity connector (Claude) or app (ChatGPT) before users can sign in. Ask your admin, or have them reach out to hello@klarity.ai.
A connection is scoped to one workspace, so you switch at the auth level rather than from inside the assistant. How you do it depends on your authentication method:
  • OAuth: disconnect the Klarity connection in your client and reconnect. The reconnect flow shows a workspace picker.
  • API key: keys are bound to the workspace they were generated in. Generate a new key in the other workspace and swap the Bearer token in your client.
See Authentication → Switching workspaces for the full walkthrough.
Go to Settings → MCP in your Klarity workspace. You can view, disable, or rotate existing keys from the same screen where you generated them.If you suspect a key has been exposed, revoke it immediately, generate a new one, and update your client configuration. See Authentication → Keep keys safe.
In your AI client, ask something like:
Search Klarity for AI transformation opportunities across our processes — where could we build skills or deploy agents?
If the assistant calls the search tool and returns processes from your workspace, you’re connected. If it falls back to generic answers or says it has no access to Klarity, the install hasn’t completed — re-check the install steps for your client.
No. Every tool in production is read-only. All process, artifact, and graph edits happen in the Klarity Architect UI. See Limitations.
Usually not. That response means the workspace doesn’t yet have captured data covering the question — typically a capture gap, not an MCP bug. The gap itself is useful: it tells you what to capture next.If the question should have evidence and the assistant can’t find it, try refining the query — single searches miss, and processes use organization-specific names. See Operating principles.
Any MCP-compatible client works. Use the install page that matches what you have today: