MNotify MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MNOTIFY_API_KEY | Yes | Your MNotify API key |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| send_quick_bulk_smsA | Send SMS to explicit phone numbers. Parameters
Returns
|
| send_bulk_group_smsB | Send an SMS to all contacts in one or more groups. Provide |
| update_scheduled_smsB | Update a scheduled SMS campaign. Supply |
| sms_delivery_reportC | Get the delivery report for a specific SMS campaign by its ID. |
| specific_sms_delivery_reportB | Get the delivery status for a specific message within a campaign by |
| periodic_sms_delivery_reportB | Get delivery reports for campaigns within a date range (YYYY-MM-DD). |
| add_contactB | Add a contact to a group. Requires |
| update_contactB | Update a contact by |
| delete_contactA | Delete a contact by |
| get_contact_detailsB | Fetch contact details by |
| get_contact_listC | List contacts (first page as returned by the API). |
| get_group_contactsB | List contacts in a given group by |
| add_groupC | Create a new contact group with |
| update_groupA | Rename a contact group by |
| delete_groupB | Delete a contact group by |
| get_group_detailsC | Fetch details for a group by |
| get_group_listA | List all groups. |
| get_template_listC | List message templates. |
| get_message_templateB | Fetch a message template by |
| add_message_templateC | Create a message template with |
| update_message_templateA | Update a template by |
| delete_message_templateC | Delete a message template by |
| register_sender_idC | Register a sender ID (≤ 11 chars) with a |
| check_sender_idC | Check the status of a registered sender ID. |
| check_sms_balanceA | Get your current SMS balance and wallet summary. |
| get_context_snapshotA | Return a compact snapshot of known entities (names → IDs) gathered so far. |
| resolve_group_nameA | Resolve a group name (case-insensitive, substring) to known IDs from this session. This uses the MCP server's in-memory cache populated by prior tool calls. |
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 27 tools
Most tools have clearly distinct purposes (contacts, groups, templates, sender IDs, sending, reports). The three delivery report tools could be confused but descriptions specify different filters. Overall minimal ambiguity.
Predominantly verb_noun pattern (add_contact, delete_group, get_contact_details). Some variation: get_contact_list vs get_group_list vs get_template_list; get_context_snapshot and resolve_group_name are outliers but not chaotic.
27 tools is on the high side but justified by CRUD operations for contacts, groups, templates, plus sending and delivery reports. Slightly over the ideal range but not excessive.
Covers core SMS management: contacts, groups, templates, sender IDs, sending, scheduling, delivery reports. Minor omissions like campaign listing or deletion, but no critical dead ends.