Setup

Create, test, deploy your MCP key

Five clear steps: generate the key, validate it in 30 seconds with cURL, configure your client of choice, store it safely, rotate. Bilingual FR / EN, atemporal, MiCA-aware.

1Create your MCP key
Go to Dashboard → Settings → MCP API keys → "Create MCP key". Pick a descriptive name (e.g. claude-desktop-laptop, cursor-personal, my-hermes-agent). The plaintext secret is shown exactly once - copy it straight into your secret manager.
Open the dashboard →

2Smoke-test the key in 30 seconds (cURL)

Run a direct call to the MCP endpoint to confirm Bearer auth works. A 200 OK with a valid JSON-RPC initialize response means your key is live.

curl -sX POST https://mcp.trinityinsights.io/mcp \
  -H "Authorization: Bearer <paste-your-tr_mcp_key-here>" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2025-11-25",
      "capabilities": {},
      "clientInfo": { "name": "trinity-smoke-test", "version": "1.0.0" }
    }
  }'

3Configure your MCP client
Pick your client below. Each guide gives the exact configuration (file path, JSON snippet, restart required) for Claude Desktop, Claude Code, Cursor, ChatGPT Apps SDK, Gemini Antigravity, Windsurf, VS Code Copilot, and Perplexity Spaces.
See per-client guides ↓
4Store the key safely
Never commit the plaintext key to a git repository. Use OS-native secret stores (macOS Keychain, Linux gnome-keyring, Windows Credential Manager) or a managed secret backend (1Password, Bitwarden, Doppler, AWS Secrets Manager, Vault).
5Revoke or rotate the key
A key can be revoked at any time from the dashboard ("Revoke" button on the row). Propagation is within 60 seconds (MCP cache TTL). To rotate: create the new key, update your clients, then revoke the old key.

Canonical endpoint

https://mcp.trinityinsights.io/mcp

Transport: Streamable HTTP (MCP 2025-11-25)
Authentication: Bearer header (Phase 1). OAuth 2.1 PKCE in Phase 2.
Key format: tr_mcp_ + URL-safe secret (≥ 256 bits of entropy)
TLS: HTTPS strict + HSTS preload

Per-client setup guides

Eight major MCP clients are supported through the same canonical endpoint. Each guide details the config file path, the exact JSON snippet to paste, and post-installation checks.

Recommended pattern: environment variable

Rather than pasting the plaintext key into your client's config file, export it as an environment variable and reference it from the client JSON. That simplifies rotation and prevents accidental leaks.

macOS / Linux

# In ~/.zshrc or ~/.bashrc (then `source` it)
export TRINITY_MCP_API_KEY="tr_mcp_..."

Windows (cmd / PowerShell)

# Persistent per-user env var - open a new shell after the command
setx TRINITY_MCP_API_KEY "tr_mcp_..."

Troubleshooting

HTTP 401: The Bearer header is missing or the key is not recognised. Verify the tr_mcp_ prefix and that the key is not revoked.
HTTP 403: Tier insufficient for the requested tool or metric. The JSON response includes the required tier and a link to /pricing.
HTTP 429: Rate limit exceeded. The Retry-After header tells you how many seconds to wait. Per-tier limits are documented at /mcp/docs/tier-access.
Lost key: The plaintext key is never retrievable. Revoke the lost key from the dashboard and create a new one. Rotation takes less than a minute.

Chargement…

curl -sX POST https://mcp.trinityinsights.io/mcp \ -H "Authorization: Bearer <paste-your-tr_mcp_key-here>" \ -H "Content-Type: application/json" \ -H "Accept: application/json, text/event-stream" \ -d '{ "jsonrpc": "2.0", "id": 1, "method": "initialize", "params": { "protocolVersion": "2025-11-25", "capabilities": {}, "clientInfo": { "name": "trinity-smoke-test", "version": "1.0.0" } } }'

Recommended pattern: environment variable

macOS / Linux

# In ~/.zshrc or ~/.bashrc (then `source` it) export TRINITY_MCP_API_KEY="tr_mcp_..."

Windows (cmd / PowerShell)

# Persistent per-user env var - open a new shell after the command setx TRINITY_MCP_API_KEY "tr_mcp_..."

Troubleshooting

HTTP 401

The Bearer header is missing or the key is not recognised. Verify the tr_mcp_ prefix and that the key is not revoked.

HTTP 403

Tier insufficient for the requested tool or metric. The JSON response includes the required tier and a link to /pricing.

HTTP 429

Rate limit exceeded. The Retry-After header tells you how many seconds to wait. Per-tier limits are documented at /mcp/docs/tier-access.

Lost key

The plaintext key is never retrievable. Revoke the lost key from the dashboard and create a new one. Rotation takes less than a minute.

1Create your MCP key

2Smoke-test the key in 30 seconds (cURL)

3Configure your MCP client

4Store the key safely

5Revoke or rotate the key

Canonical endpoint

Per-client setup guides

Recommended pattern: environment variable

Troubleshooting

1Create your MCP key

2Smoke-test the key in 30 seconds (cURL)

3Configure your MCP client

4Store the key safely

5Revoke or rotate the key

Canonical endpoint

Per-client setup guides

Recommended pattern: environment variable

Troubleshooting