---
title: "MCP Keys"
description: "Create, scope, and revoke workspace-scoped MCP keys for AI assistant integrations like Claude and Cursor."
date: "2026-06-02"
tags: ["MCP", "AI assistant", "Claude", "Cursor", "token", "keys"]
nav_order: 6
nav_display: true
---

# MCP Keys

From the profile menu at the bottom of the sidebar, choose **MCP**, or open the workspace switcher in the sidebar, choose **Manage workspace**, and select **MCP** to manage your MCP access keys.

Keys belong to your user account, even though the page appears inside a workspace Settings URL. Each key is **scoped to the workspaces you choose** — an AI assistant using the key can only reach those workspaces, and only while you remain a member of them. You can create as many keys as you need, for example one per AI assistant.

For the full MCP setup guide, see [Use the Perspective AI MCP](/docs/build/mcp).

## Create a Key

Under **Create a new key**:

1. Enter a **Key name** (for example, `Claude Desktop`) so you can recognize it later.
2. Select the **workspaces** this key can access. You can only choose workspaces you belong to.
3. Click **Create key**.

The new key appears under **Your keys** with:

- A one-time key reveal dialog with the full token and copy button
- The workspaces it can access
- Creation time and last used time
- Ready-to-copy setup instructions for Claude Desktop, Claude Code, and Cursor

Copy the token before closing the dialog. For security, Perspective will not show the full token again. After the dialog closes, the key list shows only a masked token, workspace scope, and delete action.

Treat the token like a password. Copy it only into MCP clients you trust, and scope each key to just the workspaces that client needs. If you lose the token, delete the key and create a replacement.

## Configure an MCP Client

Each key card includes ready-to-copy setup options:

- **Claude Desktop** - paste the generated `mcp-remote` config into the Claude Desktop config file.
- **Claude Code** - run the generated `claude mcp add --transport http --scope user perspective ...` command.
- **Cursor** - paste the generated config into `~/.cursor/mcp.json`.

The endpoint shown under **MCP Endpoint** is the Perspective MCP server URL, and the Authorization header is `Authorization: Bearer <your-token>`.

## Revoke a Key

Click **Delete** on a key to revoke it. AI assistants configured with that key lose access immediately. To rotate a key, delete it and create a new one — there is no in-place regenerate.

## Legacy Token

If you generated a single MCP token before workspace scoping existed, it appears under **Legacy token**. This token can access **all** of your workspaces and keeps working for backward compatibility, but you can no longer create a new one.

We recommend replacing it with scoped keys and clicking **Revoke** to delete it. Any assistant still using the legacy token loses access immediately.

## OAuth Alternative

Some MCP clients support OAuth. OAuth connections do not require a copied token and appear under [Connected Apps](/docs/guide/settings/connected-apps), where you can disconnect them.

Use a key when your MCP client does not support OAuth or when you prefer a manually managed, workspace-scoped credential.