Agentic Gmail triage: classify, summarize, extract tasks, draft replies. Never sends.
MCPpedia last refreshed this data
io.github.tarunlnmiit/inbox-to-action is an MCP server that agentic Gmail triage: classify, summarize, extract tasks, draft replies. Never sends. Its tool list has not been published yet over stdio and http, requires no API key, and scores 57/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-tarunlnmiit-inbox-to-action": {
"args": [
"inbox-to-action"
],
"command": "uvx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Published on PyPI and listed on the Official MCP Registry (io.github.tarunlnmiit/inbox-to-action), Glama (deployable release, Quality A), and Smithery (MCPB bundle). Registry manifests (server.json, glama.json) ship in the repo.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx 'inbox-to-action' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked inbox-to-action against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in communication / writing
Asynchronous coordination layer for AI coding agents: identities, inboxes, searchable threads, and advisory file leases over FastMCP + Git + SQLite
MCP server for document format conversion using pandoc.
Programmable email inbox for AI agents — JMAP, PoW auth, stdio MCP server.
The markdown workspace your AI can read, search, and suggest edits in — every change signed.
MCP Security Weekly
Get CVE alerts and security updates for io.github.tarunlnmiit/inbox-to-action and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Published on PyPI and listed on the
Official MCP Registry (io.github.tarunlnmiit/inbox-to-action),
Glama (deployable release, Quality A),
and Smithery (MCPB bundle).
Registry manifests (server.json, glama.json) ship in the repo.
One command. Your inbox triaged, summarized, drafted, and turned into tasks — in a single agentic pass.
pip install inbox-to-action # or: pipx install inbox-to-action
uvx inbox-to-action run --mock # zero-install trial (uv)
pip install 'inbox-to-action[mcp]' # + MCP server for Claude Code
docker run --rm ghcr.io/tarunlnmiit/inbox-to-action # MCP server (stdio)
Try it with zero setup: inbox-to-action run --mock (bundled sample inbox).
📖 Full documentation → docs/ — install · providers · Gmail OAuth · multi-account · integrations · MCP & Skill · config · troubleshooting · testing checklist. Quick version: SETUP.md.
Most people process their inbox with four separate tools: an email client to read, a task manager to capture to-dos, a calendar to block time, and (increasingly) an AI summarizer to make sense of long threads. Every message gets handled four times.
inbox-to-action collapses all four into one agentic pass. Run one command and get
a unified triage report, drafted replies saved to Gmail, and extracted tasks — without
ever leaving the terminal, and without ever sending an email automatically.
This tool cannot send email. It requests only the Gmail readonly + compose
scopes; there is no send scope and no send API call anywhere in the codebase
(enforced by a test). Replies are saved as Gmail drafts for you to review and send.
Email bodies flow into the LLM prompt, so a hostile email could try to steer its own classification or a drafted reply (prompt injection). Because every draft is saved for human review and nothing is ever sent automatically, the worst case is a draft you choose not to send. See SECURITY.md.
inbox-to-action reads your email. Where your email content goes for classification
depends on the LLM provider you pick — and the default (openrouter) is a cloud
provider, so an out-of-the-box run sends your subjects + bodies to a third party.
PROVIDER= | Email content goes to | Key |
|---|---|---|
| `ol |