Cakemail API MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| cakemail_healthA | Check if Cakemail MCP server is operational. Returns: Health status information including server version and endpoint count |
| cakemail_list_endpointsB | List all available Cakemail API endpoints. |
| cakemail_get_endpointA | Get detailed specification for a specific Cakemail API endpoint. |
| cakemail_get_authA | Get Cakemail API authentication documentation. Returns: Authentication requirements and configuration details, or error response if spec cannot be loaded |
| cakemail_call_apiD | Execute a Cakemail API call. |
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: health check, endpoint listing, endpoint details, auth documentation, and API execution. No overlap or ambiguity.
All tools follow a consistent 'cakemail_verb_noun' pattern (e.g., cakemail_health, cakemail_list_endpoints), making them predictable and easy to understand.
With only 5 tools, the server is well-scoped for its role as a wrapper around the Cakemail API. Each tool provides essential functionality without unnecessary bloat.
The server includes health checks, endpoint discovery, auth info, and a generic API call tool, covering the core needs. However, it lacks dedicated CRUD tools for specific resources, relying on the generic call_api to fill gaps.