Works where your agent works.
Molted is the same product over MCP, a CLI and a REST API, so Claude Code, Cursor, Codex or your own code can run the inbox.
MCP, hosted for you.
Point any MCP client at the hosted endpoint with your API key. Your agent gets tools like send_email, dry_run, read_inbox, reply and handoff_thread, and each one says what it returns.
$ claude mcp add --transport http molted \ https://mcp.molted.email/mcp \ --header \ "Authorization: Bearer mm_live_…"A CLI that answers in JSON.
molted covers sending, threads, rules, suppressions, webhooks and events, and prints JSON your agent can read. A dry run of any send shows the verdict before anything goes out.
$ npm install -g @molted/cli$ molted auth login$ molted send --dry-run \ --to priya@acme.com \ --subject "Renewal" \ --body "Hi Priya"REST underneath.
Every CLI command and MCP tool is an HTTP call with a Bearer key. Two skill files describe the API and the CLI in a form your agent can read before its first call.
Authorization: Bearer mm_live_… · /skill.md · /cli-skill.md
Bring the agent you already use.
Clients that speak MCP use the hosted endpoint. Anything that can run a shell can use the CLI, and everything else can call the API.
Claude Code · Cursor · Codex · MCP · CLI · REST
Hand it to your agent.
It sets up its own inbox. You decide how much it does on its own.