Docs · Get started
Use it today over MCP
The APIs aren't live yet, but the engine behind them is. Connect your own AI app to a MagpieCRM workspace on Magpie Cloud over MCP, and it can search for people and companies, build lists and draft campaigns.
What you need
- A MagpieCRM workspace on Magpie Cloud, at
yourteam.magpiecrm.com. Plans start at £10$15 a month: see MagpieCRM's pricing. - A key for each AI app. In the workspace, open Settings, then Connect AI apps, and make one named after the app. It's shown once. One key per app means you can revoke one without touching the others.
- An AI app that speaks MCP over Streamable HTTP, such as Claude Code, Cursor or Codex CLI.
The endpoint
The server is called magpiecrm and lives at https://yourteam.magpiecrm.com/api/mcp, with your workspace's name in place of yourteam. Every request sends the key as Authorization: Bearer <key>. Settings, then Connect AI apps shows these snippets with your address and key filled in.
Connect your own AI app
Make a key in Settings, under Connect AI apps, then add MagpieCRM to your client. Your AI can then search prospects, build lists and draft campaigns, templates and surveys, as the copilot does.
claude mcp add --transport http magpiecrm https://yourteam.magpiecrm.com/api/mcp \
--header "Authorization: Bearer <your MCP key>"Setup for Claude Desktop and the OpenAI API, and the full list of tools, are in MagpieCRM's MCP docs.
What a key can reach
A key gives full access to the workspace's contacts and can run prospect searches. Data your AI reads is sent to that app's provider.
The tools
The tools are the ones MagpieCRM's built-in copilot uses. The ones that use the engine, and a few others:
| Tools | What they do |
|---|---|
searchPeople | Searches for people, as Prospect Search does in the app. Uses credits for each person it returns. Returns no emails. |
searchCompanies | Searches for companies, as Prospect Search's company tab does. Uses credits too. |
searchIndustries, getPersonas | Looks up industry names to search with, and your saved ideal-customer personas. |
getLists, createList, getContacts, addContacts | Reads and builds your lists and contacts. |
createCampaign, updateCampaign, getCampaignStats | Drafts campaigns, and reads how sent ones did. It can't send or schedule one. |
createSequence, enrollInSequence, setSequenceStatus | Writes sequences, adds people to them, and starts or pauses them. Adding people and starting a sequence lead to email being sent, so both are marked destructive. |
createProposal, shareProposal, sendProposal | Makes a proposal for a deal, gets its private link, or emails the link to people. `sendProposal` sends email, so it's marked destructive. |
createSurvey, createSavedTemplate and the design tools | Builds surveys and email designs, block by block, as drafts you can open in the app. |
Credits
searchPeople uses 1 prospect credit for each person it returns, from the workspace's monthly allowance. A credit costs £0.004$0.006. searchCompanies uses credits too. Both tools say so in their descriptions, and are marked as open-world, so your AI app knows they cost something.
Emails are found when you save people
searchPeople returns people, not email addresses, and the MCP server can't reveal an email or save prospects. You do that in the app: in Prospect Search, tick the people you want, choose Save to list, then Find emails & save. Each person's work email is found and checked with their company's mail server as they're saved.
Each verified email found uses 1 prospect credit. Once they're saved, your AI app can read them with getListContacts and use them in a campaign or sequence draft.
Sending needs you
- The MCP server can't send or schedule a campaign. You do that in the app.
enrollInSequence,setSequenceStatusandsendProposalare the tools that lead to email being sent. They're marked destructive, so AI apps that respect that ask you before running them.- Email goes out from your workspace's own sending domains, within its daily sending limits.
MCP and the APIs
MCP works on your MagpieCRM workspace and its data, with a key made there. The APIs are planned for your own product, with keys of their own: neither key will work in the other's place. See the Quickstart for how the APIs are planned to work.
Questions about the APIs? Email pele@magpiecrm.com.