Promethist for Claude

Sign-In and Permissions

How Claude Signs In

The connector uses the standard MCP authorization flow (OAuth 2.1 with PKCE):

Claude calls the MCP server, which answers that a sign-in is required and where to perform it.
Claude registers itself with Promethist’s authorization service and opens the Promethist sign-in page in your browser.
You sign in with the same account as in the Studio — Google, Microsoft or your company’s single sign-on (Continue with work email). If you are already signed in to the Studio in that browser, this step may pass without a prompt.
Promethist issues Claude a token for the MCP server of that region. Claude stores it with your Claude account; your Promethist credentials are never given to Claude.

Promethist sends sign-in results only to Claude’s own callback addresses and, for command-line clients such as Claude Code, to a callback on your own computer.

A token is valid for one hour and Claude renews it automatically. The sign-in itself stays valid as long as the connector is used at least once every 30 days; after a longer pause, Claude asks you to sign in again. To end it sooner, disconnect or remove the connector in Claude.

Your Permissions Apply

Every tool call runs as you. The server checks your roles in Promethist at the moment of each call, exactly as the Studio does, so a role change — or the removal of your membership — applies to Claude immediately.

Role	What Claude can do for you
Viewer	Read the accounts, projects, agents and project assets you have access to; read analytics, conversations and test results; read the account’s subscription, invoices and usage; hold live test conversations with agents.
Editor	Everything a Viewer can, plus create, change and delete agents and project assets, promote and publish agents and evaluations, create and run test suites, and change project settings, including the terms and conditions. An Editor of an account can also change the account’s name and logo and create projects in it.
Owner	Everything an Editor can, plus manage members and invitations of the account or project.

Role

What Claude can do for you

Viewer

Read the accounts, projects, agents and project assets you have access to; read analytics, conversations and test results; read the account’s subscription, invoices and usage; hold live test conversations with agents.

Editor

Everything a Viewer can, plus create, change and delete agents and project assets, promote and publish agents and evaluations, create and run test suites, and change project settings, including the terms and conditions. An Editor of an account can also change the account’s name and logo and create projects in it.

Owner

Everything an Editor can, plus manage members and invitations of the account or project.

Some things are deliberately not available through Claude: buying or changing a subscription, payment details, identity-provider settings and the account privacy settings stay in the Studio.

Confirmation Before Irreversible Actions

Operations that remove something cannot be performed until you have confirmed them: deleting an evaluation, knowledge source, interactive-content element, integration, connector or test suite; removing an evaluation’s output data element or group; archiving or reverting an agent; reverting an evaluation; removing a member or revoking an invitation. Claude asks you first and repeats the call with your confirmation. If it does not, the server refuses the call and nothing happens.

Promoting and publishing agents and evaluations are not gated, because the previous revisions are kept. Publishing still makes the new revision live at once — an agent for every end user, an evaluation for every agent it is attached to — so tell Claude when you want to decide on that step yourself.

Tools Reserved for Promethist Staff

The server lists a few tools that only Promethist staff can use: authoring the global agent templates, administering skills, and the low-level test-harness tools. For any other account they refuse the call; there is no role that unlocks them. Using templates and skills is open to everyone.

Account Settings That Affect Claude

Account Owners control three privacy settings in the Studio, and they apply to Claude as well:

Setting	Effect through Claude
Display full conversation data	When off, Claude cannot read conversation transcripts or the raw conversation data of the account, and exports contain no transcripts.
Include evaluation results in exports	When off, analytics exports contain no evaluation results.
Hide single-user evaluation results	When on, analytics leave out every evaluation result that fewer than two users stand behind.

Setting

Effect through Claude

Display full conversation data

When off, Claude cannot read conversation transcripts or the raw conversation data of the account, and exports contain no transcripts.

Include evaluation results in exports

When off, analytics exports contain no evaluation results.

Hide single-user evaluation results

When on, analytics leave out every evaluation result that fewer than two users stand behind.

Credentials stored in your integrations — authorization headers of webhooks and MCP servers — are redacted in what the server returns to Claude.