SendLayer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SENDLAYER_API_KEY | Yes | Your SendLayer API key (required) | |
| SENDER_EMAIL_ADDRESS | No | Your sender email address from a verified domain (optional) |
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-emailC | Send an email using SendLayer |
| get-eventsC | Retrieve events with optional filters |
| list-webhooksB | List registered webhooks |
| create-webhookD | Create a webhook |
| delete-webhookC | Delete a webhook by ID |
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: create-webhook, delete-webhook, and list-webhooks handle webhook lifecycle management, get-events retrieves event data, and send-email performs email sending. An agent can easily distinguish between these functions without confusion.
All tool names follow a consistent verb_noun pattern with kebab-case (e.g., create-webhook, delete-webhook, get-events, list-webhooks, send-email). This uniformity makes the tool set predictable and easy to understand.
With 5 tools, this server is well-scoped for its purpose of handling SendLayer webhooks, events, and email sending. Each tool earns its place, providing essential operations without being overly sparse or bloated.
The tool set covers core operations for webhooks (create, delete, list) and email sending, with get-events for monitoring. A minor gap exists in webhook management (e.g., no update-webhook tool), but agents can work around this by deleting and recreating webhooks as needed.