Connect an AI Client (MCP)
Connect Claude or another MCP-capable client to your Noise data: ask questions in plain language and manage campaigns with confirmation.
Noise exposes your brand's data over MCP (Model Context Protocol), so an AI assistant like Claude can answer questions about your campaigns directly, "how did last week compare to the week before?", and even manage campaigns and playbooks for you, with a preview and confirmation before anything changes.
The server URL to add to your client:
https://reporting.getnoise.com/mcp
Connecting Claude
- In Claude, open Settings → Connectors, add a custom connector, and paste the MCP URL above. Other MCP-capable clients work the same way: add a remote MCP server by URL.
- When prompted to sign in, use the email you use for the Noise portal. Your assistant is linked to your brands automatically, and you are done.
- Signed in with a different email? Ask the assistant for your reporting data anyway. It will reply with a connection code starting with
org_. Paste that code on the Integrations page (Settings → Integrations, or Resources → Reporting API on the classic dashboard) and click Connect.
Managing linked clients
The Integrations page lists every AI client connected to your brand and which teammate connected it. Anything to know:
- Every teammate can connect their own client. Links are additive and per-person.
- One client, several brands. If you work across multiple Noise brands, the same AI client can be linked to each of them; the assistant will ask which brand to query.
- Remove anytime. Removing a client on the Integrations page revokes its access within about a minute.
- New tools appear on reconnect. If we ship new capabilities, remove and re-add the connector in your AI client to pick them up.
What the assistant can see and do
Reading: daily performance (spend, views, posts, creators, CPM, installs), campaign and playbook details, and the change audit log. The same numbers, computed the same way, as your dashboard and the Reporting API; see Understanding Your Metrics.
Managing: the assistant can also pause or activate campaigns, adjust budgets and daily targets, update rates, and create or edit playbooks, including full slide content, captions, hashtags, and slide images. Three guardrails apply to every change:
- Preview first: the assistant shows you what will change and asks for confirmation before applying anything.
- Sensible limits: changes are bounded (for example budget and CPM caps), and write operations are rate limited.
- Attribution: every change is attributed to the teammate whose connection made it, and shows up in your audit log like any dashboard change.
The assistant only ever sees the brands it is explicitly linked to, and access is scoped to your organization's own data.
Prefer raw API access?
If you want to pull numbers into your own tools rather than chat with them, use the Reporting API. The MCP server and the API expose the same reporting data.