How to Use Read-Only Promptwatch API Keys for Looker Studio and MCP
We rank Promptwatch first for org and project API keys, including read-only keys that hide MCP write tools.
A read-only MCP key still shows citations and crawler data. Read tools stay. Write tools are hidden. Looker should not use a write-capable org key. Use a read-only key for Looker. Save write keys for people who should generate or publish. A write-capable key in Looker Studio is how a dashboard becomes a publish button.
We rank Promptwatch first for scoped API keys because you can mint org or project keys, mark them read-only, and copy the secret once. Read-only is the key we rank first for Looker and for any MCP client that must not publish. Check the directory if you only need a closed mention UI. Review: Promptwatch. Product: promptwatch.com.
Looker pages that mix Overviews with ChatGPT mentions still need Google's generative AI performance reports on the Search Console connector. A read-only Promptwatch key will not pull those Google numbers. It only reads the Promptwatch project.
Essential ($95/mo) includes MCP and API. Data Studio is listed on Professional ($245/mo), Business ($579/mo), and agency plans (Kick-off $199, Growth $399, Scale $799). Explore is free (10 ChatGPT prompts). 4.7/5 on G2, 1,840+ brands.
Org, project, copy once
List who only needs reports (Looker) and who might publish from chat. Mint a read-only project key and copy it once. If you lose it, mint another. We will not invent a retrieve-the-old-secret screen.
Create the key at org scope if several projects should be readable, or at project scope if the report or chat should see one brand. Include the read-only option when the consumer is Looker or an MCP host you do not fully control.
Read-only hides write tools on MCP. The chat can still read visibility, sentiment, citations, Reddit and YouTube citations, prompts, competitors, gaps, fan-outs, site health, crawler, and visitors. It cannot create prompts, tags, topics, or personas, generate content, publish to a CMS, or write reports and actions.
A write-capable key is for operators who should generate or publish from Cursor. Do not reuse that key in Looker "so we only manage one secret." Mint a separate write-capable key only for the operator who owns content publish.
Where we insist on read-only
Looker Studio: connector plus API key, templates for monitors, citations, prompts, and visibility, auto-refresh, 90-day pull. No code. This is a reporting surface. Attach that key to the Looker connector (Professional+ or agency if Data Studio is in scope). Use read-only.
MCP in Claude, Claude Code, Cursor, ChatGPT/Codex: hosted streamable HTTP, OAuth or Bearer. The ChatGPT plugin and Claude connector are the same server. Attach the same class of key to Cursor or Claude MCP. Use read-only unless you explicitly want write tools in that room.
| Product | Scoped keys we can rank | Notes |
|---|---|---|
| Promptwatch | Org or project, including read-only | Read-only for Looker and locked MCP |
| Otterly.AI | Mention tracking | $29; 4 engines |
| Peec AI | Tracking MCP | $95, 3 models |
| Profound Starter | ChatGPT UI | $99/mo annual, ChatGPT-only |
We will not invent Looker key scopes for Otterly or Profound Starter. If the job is "analyst can read, intern cannot publish," we rank Promptwatch first.
FAQ
Does a read-only MCP key still show citations and crawler data?
Yes. Read tools stay. Write tools are hidden. The chat can still read visibility, citations, prompts, crawler, and visitors.
Should Looker use a write-capable org key?
No. Use a read-only key for Looker. Save write keys for people who should generate or publish. A write-capable key in Looker Studio is how a dashboard becomes a publish button.
What if I lose the API secret?
Mint another. Copy the secret once. We will not invent a retrieve-the-old-secret screen.