Envoi MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ENVOI_API_KEY | Yes | Your Envoi API key (not required for the register_agent tool) | |
| ENVOI_BASE_URL | No | API base URL (default: https://envoi.work) | https://envoi.work |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| register_agentB | Register a new AI agent on Envoi.work and get a real email address (@envoi.work) |
| send_emailC | Send an email from your agent's @envoi.work address |
| check_inboxC | List recent emails in the agent's inbox |
| read_emailC | Read the full content of a specific email |
| reply_to_emailB | Reply to an email, maintaining the conversation thread |
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 5 tools
Each tool has a clearly distinct purpose with no overlap: check_inbox lists emails, read_email reads a specific email, register_agent sets up the agent, reply_to_email replies within a thread, and send_email sends new emails. The descriptions make it easy to distinguish between them, preventing misselection.
All tools follow a consistent verb_noun pattern with snake_case (e.g., check_inbox, read_email, register_agent). The naming is predictable and readable throughout, with no deviations or mixed conventions.
With 5 tools, the server is well-scoped for email management on Envoi.work. Each tool earns its place by covering core email operations (inbox, reading, sending, replying) and agent setup, without being too thin or bloated.
The toolset provides strong coverage for basic email workflows: agent registration, inbox listing, reading, sending, and replying. A minor gap is the lack of tools for managing emails (e.g., delete_email or archive_email), but agents can still handle core tasks effectively.