Connect your AI assistant to Oppizi

Oppizi plugs straight into your AI assistant through an MCP server (Model Context Protocol). Connect Claude, Cursor, ChatGPT, or any MCP-capable tool with a single browser sign-in — no API keys to copy — then create campaigns, pull performance, and check pricing just by asking.

Server URL

https://developer-api.oppizi.com/client/mcp

What you can do

Create campaigns by conversation — the same self-serve flow as the Oppizi wizard, in chat: Direct Mail to your own list (ADM) or Every Door Direct Mail (EDDM). Pick the format, attach one of your designs, choose targeting, set a launch date. Nothing is charged and nothing sends automatically — every campaign stops at In Review for the Oppizi team to confirm.
Ask about performance — your results by week, city, creative and A/B: scans, reach, conversions, CVR, plus your own revenue & ROI. Status, schedule, coupons and creative too.
Know the cost up front — instant flyer-distribution & EDDM quotes, and a pre-submit estimate of the campaign you're assembling.
Track conversions — record signups and purchases back to Oppizi and read them alongside your campaign results.

How to connect

In your AI assistant, add a remote MCP server (sometimes called a connector or integration) with the URL above.
Your assistant opens a browser window on https://auth.oppizi.com — sign in with your Oppizi account (the same one you use for the platform).
Review and approve the requested access. That's it — your assistant can now query your campaigns.

What your assistant can access

Scope	Grants
`client:read`	Read your campaigns, performance & analytics, cost, designs, audiences, missions and conversions, and use the pricing calculators (always scoped to your own client workspace)
`client:track`	Send conversion tracking events on your behalf
`campaigns:create`	Build campaigns on your behalf — always on your own client, always stopping at In Review (never charged, never sent automatically). Enabled per account — ask Oppizi to switch it on.

You approve exactly the access you want at sign-in. Access tokens are short-lived (15 minutes) and refreshed automatically.

Client examples

Claude Code:

claude mcp add --transport http oppizi https://developer-api.oppizi.com/client/mcp

Claude.ai: Settings → Connectors → Add custom connector → paste the server URL.

Cursor: Settings → MCP → Add server → type Streamable HTTP, paste the server URL.

Try asking

"What would 5,000 postcards to my customer list cost?"
"Set up an EDDM campaign around my store using my Holiday postcard, launching next month — then submit it for review."
"How did my last mail campaign perform — scans, conversions and ROI by week?"
"Show me the campaigns I have in review and their launch dates."

Building campaigns over REST

If you are integrating a backend rather than an AI assistant, the same build flow is available as ordinary REST calls. The steps mirror the wizard, and each returns the updated draft:

Step	Call
Create a draft	`POST /client/campaigns`
Update it	`PATCH /client/campaigns/:id`
Targeting — cities	`POST /client/campaigns/:id/cities`
Targeting — areas	`POST /client/campaigns/:id/areas`
Demographics	`POST /client/campaigns/:id/demographics`
Attach a design	`POST /client/campaigns/:id/design`
Link an audience (ADM)	`POST /client/campaigns/:id/audience`
Details & launch date	`PATCH /client/campaigns/:id/details`
Submit for review	`POST /client/campaigns/:id/submit`
Abandon a draft	`POST /client/campaigns/:id/cancel`

GET /client/campaigns/:id/creation-status tells you what the draft still needs before it can be submitted.

Two things to know. These calls need an OAuth access token carrying campaigns:create — the same consent screen as above; a legacy client key will not work. And submit stops the campaign at In Review exactly like the assistant flow: it is not a print or fulfilment trigger, nothing is charged, and the Oppizi team confirms every campaign before it goes out.

Troubleshooting

Login loop / consent never appears — make sure third-party cookies are not blocked for oppizi.com, and that your Oppizi user belongs to a client workspace.
401 after connecting — your assistant should refresh the token automatically; if it doesn't, remove and re-add the connector.
REST instead of MCP? Everything above is also a plain REST API — reads and the full campaign build flow (create → targeting → design → submit). See the OpenAPI specification, and Building campaigns over REST below.