TreyzaHelp Center
AI Access (MCP)

Claude Desktop and claude.ai

You do not paste a key here; you give Treyza's address only, and you pick the store and the permissions yourself on the Treyza consent screen that…

Where to find: In the Claude app, Settings → Connectors Who it's for: People who use Claude from the desktop app or from claude.ai In short: You do not paste a key here; you give Treyza's address only, and you pick the store and the permissions yourself on the Treyza consent screen that opens in your browser.

First, know this: no key is used here

Claude's custom connector screen has no field for a custom header such as Authorization. The screen asks only for an address, plus OAuth fields under advanced settings.

So the connection is made like this:

  1. You give Claude Treyza's address.
  2. Claude sends you to Treyza's consent screen in your browser.
  3. There you choose which store and which tool packs you are granting.
  4. Treyza opens an access record for that grant in the background.

You never see a key, but the permission is still yours and you can take it back from the panel at any moment.

If you are on an enterprise (Team/Enterprise) Claude account there is a second route — see Enterprise accounts at the end of this page.

Step-by-step setup

  1. In Claude, open Settings → Connectors.

  2. Press "Add custom connector".

  3. Paste the Treyza MCP server address into the box:

    https://api.treyza.co/mcp

  4. Leave the OAuth Client ID and OAuth Client Secret fields under Advanced settings empty. Treyza identifies Claude by itself; you do not have to fill these in.

  5. Save. Claude redirects you to Treyza in your browser.

  6. Sign in to your Treyza account if you are asked to.

  7. On the consent screen that opens:

    • Pick the store (if you have more than one).
    • Review the tool packs.
    • Press Allow.

  8. You return to Claude and the connector shows as connected.

FieldWhat it is
ClientThe address of the app asking for access. For Claude it reads claude.ai.
StoreWhich store the grant is for
Tool packsWhich subjects may be asked about. The default is read only.
Basic packAlways on and cannot be turned off; it holds store identity and help search.
DenyTo leave without granting anything

The consent screen highlights the app's address, not the name it claims for itself. Do not approve a request that calls itself "Claude" but comes from an address you do not recognise.

Taking the grant back

A grant you gave appears in the panel like an ordinary key row — with an OAuth badge next to it.

  1. Open Settings → AI Access.
  2. Find the row with the OAuth badge.
  3. Press Revoke in its three-dot menu.

Revoking takes effect immediately: Claude's access stops that second.

Widening a grant

A grant cannot be widened afterwards. To open more packs to Claude you reconnect the connector and go through a new consent screen. There is no such thing as a grant that quietly widens.

Enterprise accounts (Team / Enterprise)

The administrator of an enterprise Claude account can define a fixed header when adding a connector (Anthropic's static_headers feature — beta). On that route your Treyza key can be used directly:

  1. Create a key in the panel: Creating a key

  2. On the connector screen in your organisation settings, give https://api.treyza.co/mcp as the address.

  3. Enter this as the header:

    Authorization: Bearer trz_mcp_live_...

This option exists only for the organisation administrator; individual (Pro/Max) accounts have no header field on the connector screen.

How do you know it works?

Ask Claude:

"Which store are you connected to in Treyza?"

If it writes your store's name, the connection is up. More questions to try: Example scenarios

Something went wrong?

  • If the consent screen does not open, or says the request is invalid or expired, delete the connector and add it again: consent requests have a short life.
  • If the connection is not made, check the address character by character; it must end with /mcp.
  • For other errors: Troubleshooting

The screen names on this page come from Claude's own connector documentation dated 20.09.2026. Menu names may change as the app is updated; the logic (give the address, approve in the browser) stays the same.

Was this page helpful?

Creating a key

A three-step wizard creates the key; it is shown only once, so you must copy and store it straight away.

Claude Code

One command connects you, your key is embedded in that command, and claude mcp list confirms the connection.

On this page

First, know this: no key is used hereStep-by-step setupWhat you see on the consent screenTaking the grant backWidening a grantEnterprise accounts (Team / Enterprise)How do you know it works?Something went wrong?