Mint an MCP key
Create a key in Settings → MCP and copy it once.
Connect your client
Paste the endpoint + key into Claude, Cursor, or any MCP client.
Scopes & roles
Constrain a key to specific brands, platforms, and read vs write.
Audit log
See exactly what every key did, per key and org-wide.
The endpoint
How it fits together
- Connect once, in the cockpit. OAuth your platforms (Meta, Amazon, Google, LinkedIn, TikTok, Shopify) under Settings → Integrations. The MCP server acts on those same connections — it never asks your AI client for platform credentials.
- Mint a scoped key. In Settings → MCP, create a key bounded to the brands, platforms, and access level you want that client to have.
- Ask in natural language. “Audit my Ayurpet Meta account.” “Show approval-pending actions.” “Approve the scale on campaign 9234, reject the rest.” The server translates the sentence into the audit / approval / rollback operations Mesh Pilot runs internally.
- Same guardrails, same Inbox. Write operations still land as proposals in your Inbox (unless an autonomy threshold lets them auto-run), still respect spend/channel guardrails, and are always reversible.
Why scoped keys matter
A key is a capability ceiling, not just an auth token. You can hand an outside consultant a key that reads one brand’s Amazon Ads and nothing else — no write, no other brands, no other platforms — with an expiry date, a daily call cap, and a full activity log. Revoke it in one click and see everything it ever did.Read about scopes & roles
The full capability model.