Pushpad MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PUSHPAD_TOKEN | Yes | Your Pushpad API token for authentication |
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": true
} |
| resources | {
"subscribe": true,
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| notifications_listA | To list the latest notifications for your project,
send a GET request to Only the notifications created in the last 35 days are available. The response body will be an array containing objects each representing a notification. |
| notifications_createC | To send a web push notification,
send a POST request to |
| notifications_getA | To get a notification and its stats,
send a GET request to Only the notifications created in the last 35 days are available. |
| notifications_cancelB | To cancel a scheduled notification,
send a DELETE request to |
| subscriptions_listA | To list all subscriptions in your project,
send a GET request to The response body will be an array containing objects each representing a subscription. |
| subscriptions_createA | To create a new subscription,
send a POST request to A subscription will be created using the provided information. The response body will contain a JSON object with the attributes of your new subscription. This operation is mainly intended to import subscriptions from another service into Pushpad. This is not the standard way to collect subscriptions: usually you collect them using the JavaScript SDK. |
| subscriptions_getA | To show information about an individual subscription,
send a GET request to |
| subscriptions_deleteA | To delete a subscription,
send a DELETE request to The subscription will be permanently deleted. A successful request will receive a 204 status code with no body in response. |
| subscriptions_updateB | To update a subscription,
send a PATCH request to The subscription will be updated using the provided information. The response body will contain a JSON object with the attributes of your subscription. |
| projects_listA | To list all projects in your account, send a GET request to The response body will be an array containing objects each representing a project. |
| projects_createA | To create a new project, send a POST request to A project will be created using the provided information. The response body will contain a JSON object with the attributes of your new project. |
| projects_getA | To show information about an individual project, send a GET request
to |
| projects_deleteA | To delete a project, send a DELETE request to The project will be deleted asynchronously. The actual processing of the request is performed later. A successful request will receive a 202 status code with no body in response. |
| projects_updateC | To update a project, send a PATCH request to The project will be updated using the provided information. The response body will contain a JSON object with the attributes of your project. |
| senders_listB | To list all senders in your account, send a GET request to The response body will be an array containing objects each representing a sender. |
| senders_createC | To create a new sender, send a POST request to A sender will be created using the provided information. The response body will contain a JSON object with the attributes of your new sender. |
| senders_getC | To show information about an individual sender, send a GET request
to |
| senders_deleteA | To delete a sender, send a DELETE request to The sender will be permanently deleted. You cannot delete a sender if it has associated projects. A successful request will receive a 204 status code with no body in response. |
| senders_updateC | To update a sender, send a PATCH request to The sender will be updated using the provided information. The response body will contain a JSON object with the attributes of your sender. |
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 19 tools
Each tool targets a distinct resource-action pair (notifications, subscriptions, projects, senders) with clear CRUD operations. There is no overlap or ambiguity between the tools.
All tool names follow a consistent plural_noun_verb pattern (e.g., notifications_get, subscriptions_create, projects_delete), making the API surface predictable and easily navigable.
With 19 tools covering four distinct resources (notifications, subscriptions, projects, senders), the count is appropriate for a comprehensive push notification service. Each tool has a clear purpose, and the set is neither bloated nor thin.
All four resources have full CRUD operations (create, get, update, delete, list) with the exception of notifications which also includes cancel. No obvious gaps exist for managing a push notification service.