Cursor / VS Code / hosted MCP

Install Marmunk. Sign up in the browser.

One plugin for Cursor, one badge for VS Code. The agent talks to Marmunk's hosted MCP. You create the account when Cursor asks — no API key in config, no VSIX, no cold outreach.

Add to Cursor Add to VS Code

Account creation is open. External sending is still manually approved.

Cursor command palette

/add-plugin marmunk

Then choose Connect when Marmunk appears under Tools & MCP.

01 / One loop

Signup is the OAuth consent, not a tool.

Cursor opens Marmunk in your browser. Continue with Google, then Approve — that creates a test-only account, names the organization from your email, and accepts Terms. Read access is on by default. Enable email.send only if the agent should queue mail. Production sending stays off; 10 emails a day until you add a card.

01InstallPlugin or MCP URL

02ConnectBrowser OAuth

03ConsentRead, then send

04SendDurable msg_*

05TraceQueued is not delivered

02 / Ask the agent

Drop a prompt. Stay inside the envelope.

Connect Marmunk. I'll continue with Google in the browser.

Add receipts.example.com as a sending domain and show me the DNS records.

Queue a test receipt to the address I specify. Use a stable idempotency key.

Trace msg_… and tell me whether it is queued, held, or delivered.

Scaffold a TypeScript send for order receipts using @marmunk/sdk.

03 / Manual MCP

Same URL. No secrets in the file.

Prefer a raw MCP entry? Point Cursor or Copilot at https://api.marmunk.com/mcp. Browserless runtimes still use an expiring Agent credential from the dashboard — those credentials cannot create accounts or submit sending applications.

{
  "mcpServers": {
    "marmunk": {
      "url": "https://api.marmunk.com/mcp"
    }
  }
}

Let the agent operate the same plane you do.

Install, sign up when Cursor asks, then request sending approval for production.

Add to Cursor Create account