inbox-to-action-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TELEGRAM_CHAT_ID | No | Optional: Telegram chat id | |
| TODOIST_API_TOKEN | No | Optional: push extracted tasks to Todoist | |
| TELEGRAM_BOT_TOKEN | No | Optional: Telegram bot token for run summaries |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_emailsA | Fetch unread emails (JSON list). Use mock=True for the fixture demo. Returns a JSON array of {id, sender, subject, body, thread_id, received}. Reason over these yourself: classify each, summarize long ones, extract tasks and draft replies for action_needed items, then call the IO tools. |
| save_gmail_draftC | Save a reply as a Gmail DRAFT (never sends). Returns the draft id. |
| append_tasksA | Append tasks to tasks.md. Each item: {text, deadline?}. |
| write_reportB | Write the final triage report markdown to disk. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: fetching emails, appending tasks, saving drafts, and writing reports. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern in snake_case (append_tasks, fetch_emails, save_gmail_draft, write_report), making it easy to predict their function.
With 4 tools, the server is well-scoped for its purpose of email triage and task extraction. Each tool serves a necessary function without being excessive or insufficient.
The tool set covers the core workflow of fetching, drafting, and recording tasks/reports. Minor gaps exist (e.g., no tool to mark emails as read or delete tasks), but these are acceptable for a demo/triage system.