@theyahia/sendpulse-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SENDPULSE_ID | Yes | Your SendPulse client ID | |
| SENDPULSE_SECRET | Yes | Your SendPulse client secret |
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 |
|---|---|
| get_mailing_listsA | Списки рассылки SendPulse: ID, название, количество подписчиков. |
| send_emailC | Создать и отправить email-кампанию по списку рассылки. |
| list_campaignsA | Список email-кампаний с пагинацией. |
| get_campaign_statisticsB | Статистика кампании: отправлено, открыто, кликов, open rate, click rate. |
| list_templatesA | Список email-шаблонов (свои или системные SendPulse). |
| get_templateA | Получить детали email-шаблона по ID. |
| smtp_send_emailB | Отправить транзакционное email через SMTP сервис SendPulse. |
| smtp_list_emailsC | Список отправленных SMTP-писем с пагинацией. |
| list_push_websitesB | Список сайтов с push-подпиской. |
| get_push_statisticsC | Статистика push-уведомлений для сайта. |
| create_push_taskC | Создать push-уведомление для сайта. |
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 11 tools
Each tool targets a distinct functionality: campaigns, templates, SMTP, push notifications, and mailing lists. There is no overlap; agents can clearly distinguish between sending a campaign vs a transactional email, or listing templates vs campaigns.
Most tools follow a verb_noun snake_case pattern (list_campaigns, create_push_task). However, get_mailing_lists uses 'get' for a list operation where 'list' would be more consistent, causing a slight inconsistency.
With 11 tools covering campaign management, templates, SMTP, push, and mailing lists, the count is well-scoped for a marketing automation server. Each tool serves a clear purpose without redundancy.
Core operations for email and push campaigns are present, but missing update/delete operations for campaigns, templates, and mailing lists. The surface covers essential workflows but leaves minor gaps for full lifecycle management.