Agent setup

Connect your agent to Marmunk.

One hosted endpoint, every harness. Point your coding agent at the Marmunk MCP server and it can queue transactional email, verify sending domains, trace delivery, and manage suppressions — under the same approval-gated contract human operators use.

The endpoint

Every harness below connects to the same hosted Streamable HTTP server:

https://api.marmunk.com/mcp

OAuth-capable clients authenticate in the browser: Google sign-in, then explicit scope consent. First-time Approve creates a test-only account. Browserless runtimes use an expiring Agent credential instead — see Browserless (Bearer) below.

Cursor

Use the Add to Cursor deep link, or the plugin:

/add-plugin marmunk

Manual MCP entry, if you prefer:

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

After install, choose Connect. Cursor opens a browser for sign-in and scope consent.

Claude Code

Add the HTTP server; Claude Code opens a browser for OAuth on first use:

claude mcp add --transport http marmunk https://api.marmunk.com/mcp

The Marmunk plugin for Claude Code ships the same skills as the Cursor plugin — see schybo/marmunk-plugin.

VS Code

Use the Add to VS Code deep link, or add an entry to .vscode/mcp.json:

{
  "servers": {
    "marmunk": {
      "type": "http",
      "url": "https://api.marmunk.com/mcp"
    }
  }
}

Authenticate from the MCP CodeLens above the server entry.

Codex

Codex writes the Streamable HTTP server to ~/.codex/config.toml:

codex mcp add marmunk --url https://api.marmunk.com/mcp
codex mcp login marmunk

Verify with codex mcp list.

Gemini CLI

gemini mcp add --transport http marmunk https://api.marmunk.com/mcp

Or edit the settings file directly:

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

Then authenticate inside the CLI with /mcp auth marmunk — Gemini CLI discovers the OAuth endpoints automatically.

Any other client (mcp-remote bridge)

Clients that only speak stdio can bridge hosted OAuth with mcp-remote. It launches a local process, opens a browser for sign-in, and relays to the hosted server:

npx mcp-remote https://api.marmunk.com/mcp

Configured as a stdio MCP server, the command is npx with args mcp-remote https://api.marmunk.com/mcp. This is the compatibility path; prefer native Streamable HTTP when the client supports it.

Browserless runtimes (Bearer Agent credentials)

CI jobs, containers, and background workers cannot complete an OAuth loop. An owner or administrator creates an expiring Agent credential under Dashboard → Agents and sets it as the Bearer token for the same endpoint:

{
  "mcpServers": {
    "marmunk": {
      "url": "https://api.marmunk.com/mcp",
      "headers": {
        "Authorization": "Bearer mmk_agent_..."
      }
    }
  }
}

Agent credentials are scoped and expiring. They cannot create accounts, accept Terms, mint API keys, submit sending applications, or call operator routes. Pick the narrowest scope set that works — read-only for debugging agents.

Verify the connection

Ask your agent to run marmunk_account_status_get. You should see tenant state and sending approval. Then trace a test send with marmunk_email_trace.

For the full tool surface and safety boundaries, read MCP for agents. For deeper API debugging, see Debug a send.