Developers

Connect TickClip to an MCP client

Generate a scoped API key, connect it safely, and rotate or revoke access when needed.

Last reviewed

Generate an API key

  1. Sign in to TickClip AI.
  2. Open your account menu, choose Your account, then open MCP.
  3. Give the key a name that identifies the client, such as Claude Desktop.
  4. Select Generate API key, then copy the key immediately.

TickClip shows the full key once. We store only a cryptographic hash, so a lost key cannot be recovered. Generate a replacement and revoke the lost key instead.

Connect your MCP client

Copy the MCP server URL shown beside your keys. Configure your client to send the generated key as an HTTP bearer credential:

{
  "mcpServers": {
    "tickclip": {
      "type": "http",
      "url": "https://YOUR-CONVEX-SITE.convex.site/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_TICKCLIP_API_KEY"
      }
    }
  }
}

Configuration fields differ between MCP clients. Prefer the client's secret or environment-variable support. If the client requires a local configuration file, keep that file private and out of source control.

Never put an API key in a URL, browser address bar, screenshot, support message, analytics field, or public repository.

Available tools

The MCP server exposes a deliberately small, read-only catalog:

  • verdict_get returns one published TickClip decision dossier.
  • verdicts_list returns a bounded list of recent published verdicts.
  • brand_summary_get returns bounded aggregate verdict and manipulation signals for a brand.

Keys carry only the mcp:verdicts:read scope. They cannot publish verdicts, access private conversations, change account data, or call admin functions.

Rotate or revoke a key

Use Rotate when replacing a key in a client. Copy the new key and update the client promptly; the old key remains valid for five minutes, then stops working.

Use Revoke when a device is lost, a client is retired, or a key may have been exposed. Revocation is immediate and cannot be undone.

Each key expires after 90 days. Create one key per client so you can revoke access without disrupting your other integrations.

Troubleshooting

  • Unauthorized: confirm the request uses Authorization: Bearer …, the key has not expired or been revoked, and no extra spaces were copied.
  • Too many requests: wait 60 seconds, then retry more slowly.
  • Missing tools: reconnect the client so it starts a fresh authenticated MCP session.
  • Lost key: create a new key and revoke the old entry. TickClip cannot reveal it again.

For help that does not require sharing a key, contact support@tickclip.ai.