Let agents operate the same contract humans use.
The Marmunk MCP server is an authenticated adapter over the public API—not a privileged back door.
One-click install
The hosted Streamable HTTP endpoint is the product. Cursor and VS Code Copilot open a browser for signup and scope consent. There is no API key in the MCP config.
In Cursor you can also run:
/add-plugin marmunkManual MCP entry:
{
"mcpServers": {
"marmunk": {
"url": "https://api.marmunk.com/mcp"
}
}
}Hosted connection
https://api.marmunk.com/mcpUse this URL directly in an OAuth-capable MCP client. Marmunk opens a browser for Google sign-in and explicit scope consent. First-time Approve creates the test-only account. Read access is selected by default; management and sending require separate approval. Production sending stays off; 10 emails a day until you add a card.
Remote send debugging
Tool: marmunk_email_trace
Input: { "reference_id": "msg_01example" }
// A req_* reference traces one API attempt.
// A msg_* reference traces the durable send lifecycle.Same safety boundaries
MCP calls carry a channel marker for audit and debugging, but authentication, tenant isolation, idempotency, policy, suppression, quota, and approval behave exactly like direct REST calls.