Skip to main content

Managing MCP API Keys

MCP keys authenticate your AI coding assistant to PrompTick's MCP Server. They're different from PrompTick Agent API keys (which start with pk_live_) — MCP keys start with mk_live_ and are managed separately.

Create a key​

  1. Sign in at app.promptick.ai.
  2. Open MCP in the sidebar (or go to /mcp).
  3. Click Create Key, give it a descriptive name (e.g. "Claude Code — MacBook"), and copy the key immediately. Full key values are shown only once.

The key format:

mk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Use the key​

Pass it as a Bearer token in the Authorization header:

Authorization: Bearer mk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Every client config page shows exactly where this goes.

List and revoke keys​

On the /mcp page, each key shows:

  • Name and creation date
  • Last used timestamp
  • Revoke button

Revoking a key takes effect immediately. Any client still using it will start getting 401 Unauthorized responses.

Rotation advice​

  • One key per machine or per client. If a laptop is lost, you can revoke just that key without disrupting other devices.
  • Rotate on role changes. When a team member leaves, revoke any keys they created.
  • Don't check keys into source control. Every supported client config goes in a user-level or project-level file that's typically gitignored (.cursor/mcp.json, ~/.codeium/windsurf/mcp_config.json, etc.). If you must commit the config, use an environment variable placeholder.
  • Name keys descriptively. Future-you will want to know which key is which.

Where keys are stored​

MCP keys are tracked separately from your PrompTick Agent API keys. They share your PrompTick identity (user and organization), so tool executions correctly deduct from your organization's AI Action quota.

Scopes​

Each key carries scopes that determine which tools it can call (mcp:generate, mcp:improve, mcp:enrich). By default new keys are granted all three. Contact support if you need scope restrictions for compliance.