The Delivrie MCP server gives agents the same API you use: send, schedule, verify domains, read logs. That is powerful, so it is worth setting up carefully.
Give each agent its own key
Create a separate API key for every agent or tool. If something goes wrong, you can delete one key without breaking the rest of your stack.
Use sending-access keys
An agent that only needs to send email should get a sending-access key, ideally limited to one domain. It can send and schedule, but it cannot read your contacts, change domains or create more keys.
Drafts before broadcasts
create_broadcast only makes a draft. Sending to a whole segment needs send_broadcast and a full-access key, so a human can review before anything goes out.
Watch the limits
Agents share your plan’s allowance. A spending cap in Billing stops a runaway loop from running up overage. Set it up in a minute with the MCP guide.
