Create an MCP key

An MCP key is a personal API key that lets an assistant or a script, such as OpenAI Agent Builder, Cursor, or Claude Desktop, connect to Performance Hub through its MCP server. You create and manage these keys yourself from User Preferences; each key belongs to your account and inherits your access.

Before you start

  • MCP keys are tied to your user account, not to a single facility - the key carries whatever access your account already has.
  • The new key's secret value is shown only once, at creation. Have somewhere secure ready to store it (a password manager or your MCP client's settings).
  • You'll need two things to configure your MCP client: the Server URL and an active key. Both are on the MCP & API Keys tab. If you have no keys yet, the tab says No MCP keys yet.

Open MCP & API Keys

1

Open User Preferences

Click your profile icon at the right of the top bar, then choose User Preferences.
Profile menu with User Preferences highlighted
Figure 1: The profile menu. User Preferences opens the drawer.
2

Open the MCP & API Keys tab

In the User Preferences drawer, open the MCP & API Keys tab. The other tab is Profile & Preferences.
3

Read the callout, then the key list

The tab opens with These keys belong to your user account: "Anything you connect with one of these keys, such as an AI assistant or a script, acts as you and can do what you can." A key for a Performance Hub service, such as the Model Router, is created in the Model Router's Service Access & API Keys instead. Open Service Access & API Keys goes there.

"All requests made with these keys are logged in the audit logs." "Retention settings are configured by your organisation administrator." View logs opens Audit Logs filtered to your MCP calls.

Your MCP Keys has View MCP Docs, Download CSV and Create Key. With at least one key, MCP Server Configuration shows the Server URL https://app.performancehub.co/mcp and tells you to use any active key from the list.

The MCP and API Keys tab, with the server URL and a key
Figure 2: MCP & API Keys, with the server URL and a key. Allow integration secrets is off.

Create a key

1

Start a new key

Click Create Key. A small inline form appears with a single Label field.
2

Give it a label

Enter a Label that describes where the key will be used - for example OpenAI AgentKit. The label is just for your own reference; you can rename it later. Click Create (or Cancel to dismiss the form).
Create key inline form
Figure 3: The inline create form - give the key a descriptive label
3

Copy the key now

The key is generated immediately and shown in a highlighted New MCP key (shown once) panel at the top of the list. From here you can Copy the key value to your clipboard, or use CSV to download it for safe keeping. Once you close or refresh the drawer, the full value can no longer be retrieved. Only a redacted preview is shown afterwards.
New key shown once
Figure 4: The newly created key - copy or download the secret now, it won't be shown again

Security: Treat an MCP key like a password. Don't paste it into shared documents, screenshots, or chat. If a key is ever exposed, deactivate it (and delete it) straight away and create a replacement.

Connect your MCP client

Use the details from the MCP Server Configuration panel to set up your client:

FieldWhere to find itNotes
Server URLMCP Server Configuration, on the MCP & API Keys tabClick Copy to copy it. This is the address your MCP client connects to.
API KeyAny Active key in the listUse the secret value you copied/downloaded when the key was created.

For client-specific install snippets (Cursor, Claude Desktop, and more), see Set up & integrate.

Manage existing keys

Each key in the list shows its redacted identifier, a status badge, an editable Label, and its Created (and, if used, Last used) timestamps, alongside lifecycle controls.

Key management controls
Figure 5: A key's lifecycle controls - rename, deactivate, reactivate, or delete

Key statuses

StatusMeaning
ActiveThe key works and can authenticate MCP requests.
DeactivatedThe key is disabled and will be rejected. It can be reactivated or permanently deleted.

Available actions

ActionWhen it's shownWhat it does
Label (edit field)AlwaysRename a key inline. A green check confirms Changes Saved.
DeactivateActive keysDisables the key immediately. MCP clients using it will stop working.
ReactivateDeactivated keysRe-enables a previously disabled key.
DeleteDeactivated keys onlyPermanently removes the key. A key must be deactivated before it can be deleted, and this cannot be undone.
Download CSVHeader, once after first key creationExports your key list (identifiers, labels, status, timestamps) as a CSV.

To retire a key safely: Deactivate it first (this immediately blocks any client still using it), confirm nothing breaks, then Delete it if you no longer need it.

Allow integration secrets

Each key has an Allow integration secrets switch, off unless you turn it on. "Lets scripts using this key read API keys and passwords from External Integrations when they ask for them." Turning it on asks you to confirm. Leave it off unless you trust the script that will use the key. A script with the switch on can read those secrets as you.

Allow integration secrets switched off on a key
Figure 6: Allow integration secrets, left off
Next: Set up & integrate your client