MarmunkDevelopers
Tool access

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.

01

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.

Add to CursorAdd to VS Code

In Cursor you can also run:

/add-plugin marmunk

Manual MCP entry:

{
  "mcpServers": {
    "marmunk": {
      "url": "https://api.marmunk.com/mcp"
    }
  }
}
Signup is the OAuth loop. If you do not have a Marmunk account yet, Connect opens create-account, then consent, then returns to the IDE. Agents cannot create accounts through a tool.
02

Hosted connection

https://api.marmunk.com/mcp

Use this URL directly in an OAuth-capable MCP client. Marmunk opens a browser for sign-in and explicit scope consent. Read access is selected by default; management and sending require separate approval.

03

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.
04

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.