MCP server
Use Purple Engage from your own AI assistant over MCP
Read your Engage data and draft work from an MCP-compatible AI assistant or script. A scoped key can read, draft and ask for approval. No scope can send: a person approves inside Engage every send an assistant drafts.
What is the Purple Engage MCP server?
MCP, the Model Context Protocol, is an open standard that lets an AI assistant use another app's tools. The Purple Engage MCP server is remote and hosted by Purple. It offers 14 read tools, four ready-made prompts and four resources (reference material the assistant can load: a campaign report, your business context, an idea card and what has worked for your account), so an assistant can read your contacts, segments, campaigns and results and stage work in Engage.
- A remote MCP server, hosted by Purple
- Works with any MCP client that can send an API key as a bearer token (the key passed with each request), such as developer tools and scripts
How do I connect an AI assistant to Engage?
With an API key. Give the key to any tool that can send it as a bearer token, such as a script or a developer tool. The key carries only the scopes you choose and acts as the person who created it.
- Connect with an API key from any tool that can send a bearer token
- Keys last at most 90 days and act as the person who made them, re-checked on every call
Can an outside AI assistant send messages to my guests?
No. A key can hold up to three scopes: read, draft and ask for approval. No scope can send, and an automated test proves that a key holding every scope cannot. When an assistant reaches a tool that would contact a guest, the answer is "approval required", and a person approves inside Engage.
- Read: contacts, segments, campaigns and reports, journeys, ideas, venues, business knowledge, outcomes and learnings
- Draft: stage work in Engage for a person to review
- No scope that can send
- Ask for approval: a person grants it inside Engage, never a tool
What built-in prompts come with the server?
Four: plan a win-back, review the last campaign, weekly review, and draft from an opportunity. Each gives your assistant a ready-made starting point, so you do not have to write the instructions yourself. Anything a prompt drafts still waits for approval inside Engage before it can reach a guest.
- Plan a win-back
- Review the last campaign
- Weekly review
- Draft from an opportunity
What can a connected assistant see?
Whatever the key's owner can see in Engage, including guest contact details. Choose the person who makes the key with that in mind, and connect only assistants your data protection policy allows.
- Reads what the key's owner can read, including contact names, emails and phone numbers, 50 per request
- Connect only assistants your data protection policy allows
- 300 requests a minute per key, with every write audited
How is the MCP server different from the Engage AI marketing team?
The built-in AI marketing team works inside Engage: it raises ideas every night, stages plans in your own editors and brings each send to you as an approval card. The MCP server lets an assistant you already use read your Engage data and draft work. An outside assistant can read and draft but never send.
Questions
How long does an API key last?
90 days at most. After that the key expires and you create a new one. Each key acts as the person who made it, and that person's access is re-checked on every call.
How is the MCP server different from the public API?
The public API is for your own systems: 31 paths and 14 scopes to read and write contacts, tags, events and consent, at up to 600 requests a minute per key. The MCP server is for AI assistants: read tools, ready-made prompts and resources, three scopes and no way to send, at up to 300 requests a minute per key.
Start free with Purple Engage
The free plan is listed at 500 credits a month, with unlimited* contacts and no card.