agentinbox

Connect any agentto email

If your agent can run a shell command or connect to an MCP server, it can have its own email address.

npx @agentinbox/cli setup email

A shell script waiting for an emailed approval before it continues
fig. 01 — any-agent on email[ any-agent → asks → you ]

Autonomous, butnever unsupervised

Two ways in, and one inbox behind both.

Works from a shell

Scripts, cron jobs and CI steps call the CLI and read the exit code.

Works over MCP

Any client that supports remote MCP with OAuth sign-in connects to https://mcp.agentinbox.md.

Skills for coding agents

Agents that read Agent Skills learn when to reach you and how to read the answer.

Connect your agentin four steps

Set up with the CLI, then ask from code, or connect over MCP instead.

$ npm i -g @agentinbox/cli

Try theseprompts

  • “Ask me by email before the nightly job deletes old records.”

    The job waits for your Approve. A Deny stops it.

  • “Email me which region to deploy to, with the options as choices.”

    You pick one, and your agent gets its id.

  • “Email me if the backup fails.”

    A tell message, sent only when it matters.

What elseit can do

Everything your agent gets on Email.

Questions,
answers

How does my script know the answer?

From the exit code: 0 approved or answered, 10 denied, 11 the wait ran out with the question still open, 12 expired, 1 an error. Add --json for the full result.

Can I use it in CI?

Yes. Connect the CI job with a one-time code from agentinbox.md, or give it the INBOX_SECRET_KEY environment variable.

Which agents read the skills?

Any agent that follows the Agent Skills format, including Claude Code, Codex, OpenCode, Cursor, GitHub Copilot, Gemini CLI, Hermes and OpenClaw. Install them with npx skills add agentinboxhq/skills.

Give your agentan email address.Today

Free for 100 conversations a month. No credit card required.

npx @agentinbox/cli setup email

An agent completes customer conversations and receives a reply.