Connect
1
Issue a token
Open the app’s MCP page and issue a token. The page shows the server
URL to use. Turn on edit flows only if this client should be able to
create and change flows.A token acts as you, limited to this one app. It can never see
more than you can, and it stops working if you leave the workspace.
2
Add it to your client
The server speaks Streamable HTTP, with the token as a bearer token. For
Claude Code:Most other clients take the same URL and header in their MCP settings.
Read tools
Available on every token.Write tools
Only on a token issued with edit flows, and only if you’re an owner or admin.
Describe a campaign in plain language and let your agent write it as flows.
Every flow goes through the same checks as one built in the dashboard, plus
one more: every event it names must already have been recorded for your app,
so an agent can’t invent an event name that never fires.
What it never exposes
Ingest keys, your APNs key, raw device tokens and your database credentials are never returned by any tool. Your ingest key (pna_...) does not work here,
and only an MCP token (pnm_...) does.