sentvia-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SENTVIA_API_KEY | Yes | Your SentVia API key (sv_live_…) from the dashboard. | |
| SENTVIA_BASE_URL | No | Base URL for the SentVia API. | https://api.sentvia.ai |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_inboxA | Create a new email inbox. Defaults to the managed mail.sentvia.ai domain. |
| list_inboxesA | List all inboxes for this tenant. |
| delete_inboxB | Delete an inbox. Mail to its address stops being accepted. |
| send_messageB | Send a new email from one of your inboxes. |
| reply_to_messageA | Reply to a message, staying in its thread (sets In-Reply-To/References automatically). |
| forward_messageA | Forward a message to new recipients in a fresh thread, quoting the original and re-attaching its files. |
| get_messageA | Fetch a single message by id, including body and attachment links. |
| search_messagesA | Search messages across the tenant. mode: keyword (default), semantic (by meaning), or hybrid. No query returns recent messages. |
| list_threadsA | List conversation threads, most recently active first. |
| get_threadB | Fetch a thread and all its messages in order. |
| create_draftA | Create a draft (optionally scheduled, optionally a reply). Does not send. |
| send_draftC | Send an existing draft immediately. |
| list_draftsA | List drafts for this tenant. |
| add_domainA | Add a custom sending domain. Returns the DNS records to add to your DNS; verification is automatic once they propagate. |
| get_domainB | Get a domain’s verification status and required DNS records. |
| create_webhookA | Register a webhook endpoint for delivery events. The signing secret is returned once on creation — store it. |
| list_webhooksA | List webhook endpoints (signing secrets omitted). |
| delete_webhookC | Delete a webhook endpoint. |
| add_address_ruleA | Add an allow or block rule for an email address or bare domain. Block rules are enforced on both send and receive. |
| list_address_rulesA | List allow/block rules for this tenant. |
| delete_address_ruleC | Delete an allow/block rule. |
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 21 tools
Each tool targets a distinct resource and action: webhooks, inboxes, address rules, domains, messages, threads, and drafts are all clearly separated. The send/reply/forward trio is differentiated by their descriptions, so there is no ambiguity in tool selection.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_inbox, list_drafts, delete_webhook). The occasional use of 'add' instead of 'create' (add_domain, add_address_rule) is a minor synonym variation, not a structural inconsistency.
With 21 tools, the server is slightly larger than the typical 3-15 range, but this is justified by the breadth of the email platform (inboxes, domains, messages, threads, drafts, webhooks, and rules). Every tool has a clear purpose, so the count feels appropriate rather than bloated.
The tool surface covers core CRUD for inboxes and webhooks, plus sending, searching, threads, and drafts. Minor gaps exist, such as no delete for drafts or domains, but these can be worked around (e.g., by recreating resources). No major lifecycle dead ends are present.