Integrations & API — get MentionBeat data into your stack

Three ways in

Integrations and API is how MentionBeat data leaves MentionBeat: a REST API with scoped keys, an MCP server for assistant clients, Slack and email digests after every scheduled run, CSV and PDF exports, direct CMS publishing, and OIDC single sign-on you configure yourself. A visibility number only changes behaviour if it reaches the meeting where decisions get made, and that meeting is rarely held inside our console. Pull it, get it pushed to you, or ask an assistant about it. Same data, same permissions.

REST API

Runs, per-prompt results, citations, competitors, experiments and the action queue — all readable with a workspace-scoped key you create and revoke yourself.

Enough to build your own dashboard, feed a warehouse, or wire visibility into an internal scorecard.

MCP server

Point Claude, Claude Code or any MCP client at the server and ask your own data questions in plain language — which prompts slipped, what is open in the queue, what changed since last run.

Fifteen tools: twelve read the measurements, three work the fix queue — all under your own token, scoped to what you can already do.

Push notifications

A summary posted to your Slack channel or webhook after every scheduled run, drift alerts when a tracked rate moves beyond its interval or a rival overtakes you, and an email digest on the cadence you choose.

Slack delivery is a webhook URL you paste once — no app to install, nothing to grant.

Everything that connects

All of it ships on every paid plan. There is no integrations tier: what separates the plans is credits and how many products you track, not which doors we unlock.

Integration	What it does
REST API + keys	Read runs, answers, citations, competitors, experiments, actions
MCP server	Query your measurement data from an assistant client
Google Search Console & GA4	Search demand and AI-referred sessions, synced daily next to your visibility runs
Slack & webhooks	Run summaries and drift alerts into a channel — paste an incoming-webhook URL, done
Email digest	The round-up of what moved, daily or weekly, only for periods you measured in
Looker Studio connector	Built and in final checks before its gallery listing — the API and CSV export feed any BI tool today
WordPress publishing	Generated page families pushed straight in as drafts — no plugin, just an application password
Drupal blocks	The same content as importable blocks, for Drupal sites
Static export	HTML, Markdown, JSON-LD and a generated llms.txt bundle
CSV and PDF export	Any view as a document, for sign-off outside the tool
OIDC single sign-on	Self-serve: issuer URL, client ID, secret, domain allowlist

Every row, every paid plan — see pricing for what does differ (credits and tracked products).

For agencies and multi-brand teams

A workspace per client, credits pooled across all of them, and a portfolio view that ranks every brand you manage on one screen.

Switch workspace without signing out
Role-based access, per workspace
Reports you can hand to a client under your own brand
One API key scope per workspace, revocable independently

What we ask of your stack

Nothing, to start. No tag, no script, no DNS record, no CMS connection. Measurement reads the public web the way an engine does, so a first run needs only a domain.

Connections exist to remove steps later — publishing without a copy-paste, alerting without a check-in — never as a prerequisite for the number.

API and MCP reference →

Setting up the two you install

The API is a key away and the digests are a checkbox. These two live outside the console, so here is the whole setup.

MCP server — your data inside an assistant

Point Claude Code, Claude Desktop, Cursor or any MCP client at it and ask in plain language. Twelve tools read the measurements; three work the fix queue.

claude mcp add mentionbeat \
  --env MENTIONBEAT_API_KEY=<your key> \
  -- npx -y @mentionbeat/mcp-server

The key comes from Settings → API keys and does not expire; revoking it cuts the integration off at once. It is traded for a short-lived token behind the scenes, so nothing permanent travels to the measurement API.

list_projects
get_project
list_runs
get_run_metrics
get_trends
get_citations
get_benchmark
get_hallucinations
get_experiments
list_actions
get_fix
check_ai_access
run_site_audit
mark_action_fixed
verify_actions

Everything runs under your own token, scoped to what you can already see and do. Marking an action fixed triggers an immediate re-check, and a finding that is still there goes back on the queue — an assistant cannot mark its own homework.

Looker Studio — the trend in the monthly report

One row per metric per run, with the interval bands intact, in the report you already send. The connector is built and in final checks before its gallery listing; until that lands, the REST API and CSV export feed Looker Studio through its native connectors.

Run date · Metric · Run ID · Change beyond noise · Value · CI low / CI high (95%) · Sample size (n) · Delta vs previous run

Once the gallery listing is live: open the connector, authorise it, and paste an API key from Settings → API keys.
Today: export any view as CSV, or pull /v1 endpoints into Looker Studio's Sheets or CSV connectors with a key from the same place.
Chart Value by Run date, broken down by Metric, with the CI fields as bands.

A missing interval stays empty rather than becoming a zero — a chart should never draw certainty we did not measure.

Questions about connecting

What can I do with the MCP server?

Point an MCP client such as Claude or Claude Code at it and ask your measurement data questions in plain language — which prompts you lost this week, what changed since the last run, what is open in the fix queue. It can also work the queue: run a site audit, mark an action fixed, re-verify. Marking something fixed triggers an immediate re-check, and a finding that is still there goes back on the queue — an assistant cannot mark its own homework. Everything runs under your own token, scoped to what you can already see and do. Setup is here.

Is the API available on every plan?

Yes — everything on this page ships on every paid plan. There is no integrations tier: plans differ in credits and how many products you track, not in which doors we unlock. Most tools in this category gate their API behind an enterprise contract; we'd rather you wire the data in on day one.

Which CMS can you publish to?

WordPress, directly. It needs no plugin — an application password and the built-in REST API are enough — and pages arrive as DRAFTS every time, because publishing to a live site is yours to do after you have read what we wrote. Drupal sites can take the same content as importable blocks. Everything else goes out as clean HTML, Markdown or a static bundle with the JSON-LD inline, which is a paste away from any editor. We would rather ship one connector that works than five that half-work.

Do you support single sign-on?

Yes — self-serve OIDC. You add your issuer URL, client ID and secret in workspace settings and configure it yourself; it does not require a sales conversation or an onboarding ticket.

Keep going

API & MCP docs

Endpoints, auth and install, before you sign up

Pricing

Which plan includes what

Platform overview

All eight surfaces in one place

Wire it into where you already work.

Start free, connect what you need later. The first run asks for a domain and nothing else.

Get started free Read the docs