About this integration
Agentic Gmail triage: classify, summarize, extract tasks, draft replies. Never sends.
- Transport
- stdio
- Authentication
- oauth
- Initial setup
- user-authorization
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.2.11
- Package
- inbox-to-action
- Last compatibility test
- Not independently tested
Connect your agent
inbox-to-actionEmail content and generated local reports are sensitive. The README says the tool cannot send email, but it can create Gmail drafts and may transmit content to a configured LLM provider. No account or provider was accessed.
Capabilities: email retrieval, email triage support, Gmail draft creation, task extraction, triage report writing
Connected profiles
Additional details
io.github.tarunlnmiit/inbox-to-action
Source ↗ · Checked 2026-09-170.2.11
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17inbox-to-action
Source ↗ · Checked 2026-09-200.2.11
Source ↗ · Checked 2026-09-20The documented stdio MCP module exposes IO-only tools while the host performs classification and drafting; Gmail drafts require prior cached authorization and are never automatically sent.
Source ↗ · Checked 2026-09-20Real Gmail access requires one-time OAuth consent with readonly and compose scopes; provider keys vary outside the keyless host-driven MCP path.
Source ↗ · Checked 2026-09-20After installing the mcp extra, the documented client command runs python -m inbox_to_action.mcp_server over stdio.
Source ↗ · Checked 2026-09-20Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-20