MailPace MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MAILPACE_API_TOKEN | Yes | Your MailPace domain API token |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send-emailD | – |
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 1 tool
With only one tool, there is no possibility of confusion or overlap between tools, making disambiguation perfect. The single tool 'send-email' has a clear and distinct purpose without any ambiguity.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against for patterns. The name 'send-email' follows a verb-noun structure and stands alone without deviation.
A single tool for an email server is too minimal for the apparent scope, as email management typically involves more operations like listing, deleting, or managing templates. This feels thin and incomplete for the domain.
The tool surface is severely incomplete for an email server, covering only sending emails with no support for other essential operations like retrieving sent emails, managing contacts, or handling attachments. This will cause significant agent failures in email-related workflows.