Promptwatch MCP Server, REST API, Slack, and Looker Studio for AI Visibility Data

A GEO login is fine until finance wants Looker, an engineer wants an API, and the SEO channel lives in Slack. The function here is getting AI visibility data out of the dashboard and into the tools people already open. Promptwatch ships that as an MCP server, REST API v2, official ChatGPT and Claude connectors, a Slack agent, a Looker Studio connector, and Google Search Console OAuth at the org level.

The premise is that a visibility number is only useful where the people who act on it already work. A CMO does not log into a GEO app. An engineer does not read a dashboard. A channel team lives in Slack. If the data cannot reach those surfaces, it stays inside a tool that one person opens and nobody else reads. The integrations are how the data escapes the dashboard.

Promptwatch includes MCP and API access from Essential ($95/mo, 7-day trial). We do not have a published add-on price for API calls. Do not budget a phantom API SKU. Explore is free (ChatGPT, 10 prompts) and is the in-app taste, not a developer plan. Site: promptwatch.com.

MCP, ChatGPT plugin, Claude connector

The MCP server talks to ChatGPT, Claude, and Cursor. You can query visibility scores, citations, prompts, page tracker data, and generate content from those clients. Setup is OAuth. The official ChatGPT plugin and Claude connector are the store listings powered by the same MCP server. If your analyst already lives in Claude, they should not be CSV-ping-ponging the dashboard.

MCP is not a second source of truth. It reads the project you already monitor. Garbage prompts in, confident answers out.

The "not a second source of truth" line is the one to keep. MCP does not re-collect data. It reads the project you already set up in the dashboard, which means the quality of the answers depends on the quality of the prompts you put in. An analyst asking the MCP server about a project full of bad prompts gets confident answers about bad data. The fix is upstream, in the prompt list, not in the connector.

REST API v2 and scoped keys

REST API v2 covers content generation, topics, Reddit and YouTube socials, page tracker endpoints, plus later additions for Ads Radar, Shopping, Content Agent slots, and reports. Endpoint availability still follows the account's plan gates. API access on Essential does not unlock Shopping or custom reports. Docs live at promptwatch.com/docs. Scoped API keys can be organization-level or project-level, including read-only keys. Copy the key once and store it like any other secret.

The plan-gate point matters for budgeting. API access on Essential does not unlock every endpoint. Shopping and custom reports stay behind the plans that list them, so a team that builds against the API on Essential will hit endpoints that return access errors, not data. Plan the integration against the plan you will pay for, not against the plan you start on.

Use read-only keys for Looker or a warehouse sync. Keep write keys off a shared laptop.

The read-only versus write distinction is operational hygiene. A read-only key synced into Looker or a warehouse can leak and the worst case is a copied dashboard. A write key on a shared laptop can leak and the worst case is someone publishing or deleting content through the API. Scope the key to the smallest job and keep the write keys on machines that do not travel.

Slack, Looker Studio, and GSC

The Slack agent maps channels to projects. You chat against live visibility data and get updates in the channel that owns that brand. That is more useful than a global #seo dump.

The channel-to-project mapping is the part that makes Slack useful. A global #seo channel gets every alert for every brand, which means people ignore it. A channel mapped to one project gets only that project's data, which means the people in that channel read it. The mapping is the difference between a Slack integration that gets used and one that gets muted.

Looker Studio has a free Promptwatch connector and templates for monitors, citations, prompts, and visibility. Auto-refresh and shareable dashboards are the point: a CMO who will never log into app.promptwatch.com. Professional ($245/mo) is the first brand plan that lists Data Studio. Agency access follows the selected self-serve tier rather than a blanket all-plans rule. Essential still has MCP and API if you would rather build the board yourself.

The Data Studio gate is the budget line to read. Essential has MCP and API, so a team that wants to build its own board can do it from $95. The first brand plan that lists the Looker Studio connector is Professional at $245. Agency access follows the self-serve tier, not a blanket rule, so an agency's Data Studio access depends on which agency plan it picked.

Google Search Console connects with org-level Google OAuth and per-project properties. You can import topics into Prompt Explorer from GSC. That is search performance sitting next to AI prompts, not a replacement for either.

Semrush AI Toolkit is $99/domain inside Semrush's own reporting. Ahrefs Brand Radar is $199/mo plus an Ahrefs plan. Otterly.AI from $29/mo does not sell this connector set. Method: how we rank. Tools list.

The split between MCP and the REST API is worth stating plainly. MCP is the path for an analyst who wants to ask a question in a chat client and get an answer from live data. The REST API is the path for an engineer who wants to pull that data into another system on a schedule. Both read the same project, and both follow the account's plan gates, so a feature you have not paid for is not unlocked by asking for it through a different surface. A team on Essential gets MCP and API but does not get Shopping or custom reports through either one. The gate is the plan, not the integration.

The plan-gate point is the one that catches teams out. A connector is not a back door into a higher tier. Essential includes MCP and API, which is enough to build a board yourself and to let an analyst query from Claude or Cursor. Professional is the first brand plan that lists Data Studio, which is the line for a team that wants the shared Looker dashboard more than it wants to build one. Agency access follows the selected self-serve tier rather than a blanket rule, so an agency on Kick-off does not get the same Data Studio access as one on Growth. Read the plan for the feature, not the marketing page.

FAQ

Is there a per-call API price?

Not one we can quote. Essential includes MCP and API. If you need volume beyond the plan, talk to Promptwatch. Do not invent a usage tariff.

Can we put client data in a shared Slack workspace?

Map each channel to one project and watch who is in the channel. The agent will answer from that project's data.

What to do this week

Start Professional on Promptwatch for this Looker and custom-report workflow, then create a read-only project key.
Connect MCP to Cursor or Claude and ask for this week's citation losses.
Map one Slack channel to one project. Do not map all clients to #general.
Attach Looker Studio with a template before you design a custom report.
Connect GSC at the org, then import topics into Prompt Explorer.