Connect an AI Client (MCP)

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.

New to Noise? Set up your brand from your assistant

You do not need a Noise account to start. Add the server URL above to your assistant and sign in with the email you want on your Noise account. Then ask: "Help me get started on Noise."

Your assistant can explain how Noise works and why many creators beat a few, explain billing (you pay per 1,000 views, nothing upfront), define any Noise term, show you real creator posts in your niche, help you plan your first playbook, and create your brand on Noise when you are ready. It always previews what it is about to create and asks you to confirm. If it cannot help with something, it gives you your Noise rep's email.

Once your brand exists, sign in to the portal with the same email (Google sign-in or the email link). Your brand opens on its dashboard. You can finish the remaining setup in the portal, in your assistant, or a mix of both: the assistant can tell you what is left with one question, "what does my brand still need?"

Started in the portal instead? The onboarding screens offer Onboard with your agent at the top, and the step right after your brand is created asks whether you want to continue here or with your assistant.

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, create or edit playbooks, including full slide content, captions, hashtags, and slide images, and run approved posts as paid ads in your connected Meta or TikTok ad account. For ads, it lists your campaigns and ad sets first and asks where the ad should go. 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?