Skip to main content
3RD’s data doesn’t have to stay in the dashboard. API keys power integrations and your own scripts; the MCP endpoint lets AI tools query your data conversationally.

​
API keys

Manage API keys from the MCP → API Keys tab in 3RD:
  • Create and label keys per integration or script, so you always know what a key is for
  • Revoke any key instantly
  • Rotate keys periodically, like any credential
These keys authenticate the MCP endpoint and anything you build against the REST API. The Looker Studio connector uses a separate key family, managed under Settings → Looker Studio — not the MCP → API Keys tab described here.

​
Copy your key when it’s created

When you create a key, 3RD shows the full value once in a reveal dialog with a Copy button. Copy it and store it somewhere safe (a password manager, your CI/CD secret store, or your integration’s config) — the reveal dialog is the only place the key is surfaced on the API Keys tab.
Lost or leaked a key? Revoke it and create a fresh one — revoking takes effect immediately.
Treat API keys like passwords: never commit them to a repository or share them in plain text. Label each key by use, so revoking one doesn’t break something else.

​
MCP

The MCP endpoint exposes your 3RD data through the Model Context Protocol — the open standard that lets AI assistants query external tools. Connect an MCP-capable client and ask questions about your visibility right from the assistant:
“How did our visibility on Must-Win prompts develop in the German market this month?”

MCP documentation

What the connector can access, example queries, and step-by-step setup for Claude and Claude Code — in the MCP tab.