Looking for Claude Code (the terminal/IDE coding agent) instead? See its separate setup page — different product, different connector flow.
Get an API key
- Log into cloud.perfai.ai.
- In the left sidebar, click API Keys.
- Click + Create key.
- Name: something that identifies where it’s used, e.g.
Claude. - Expires after (days): optional — leave blank for the 90-day default, or set up to 365.
- Click Create key and copy the value immediately — it’s shown once and never shown again. Store it like a password.
Installation
This is a two-step dialog — fill in one screen, click Continue, then the next screen appears.- Open Settings in Claude, then go to Connectors.
- Click + Add (top right).
- The “Add custom connector” dialog opens. Fill in:
- Name:
perfai-mcp - MCP server URL:
https://mcp-server.perfai.ai/mcp
- Name:
- Click Continue.
- On the next screen, under Authentication, select No sign-in
- Under Request headers, click + Add header if one isn’t already there. It adds a row with a header-name dropdown and a Value field:
- Header name dropdown: select authorization
- Value: type the full scheme and key together —
Bearer pfk_xxxxxxxxxxxx_...(your key from above). The field’s own hint confirms this: “Include the auth scheme in the value… the value is sent exactly as entered.” - Leave Required checked.
- Click Add. Back in the Connectors list, perfai-mcp should appear with a checkmark under Status.
“Sign in now” (Claude’s default, auto-detected) tries a real OAuth handshake and will fail here — Perfai Cloud doesn’t implement that discovery flow. No sign-in is correct; the Authorization header does the authenticating instead.
Confirm you’re signed in
The API key signs you in, there is no separate login step. Every tool call runs as the user who created the key, with that user’s organizations and role. In a chat, ask:pfk_xxxxxxxxxxxx_…), never the secret. If a tool call fails with 401, the key has expired or been revoked — create a new one and update the connector’s header.

