@instantreply/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| INSTANTREPLY_API_KEY | No | Skips zero-key setup entirely. Optional; if not set, the server starts with zero-key setup tools. | |
| INSTANTREPLY_API_URL | No | Point at a different environment | https://api.instantreply.co |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_connection_guideA | Get how to connect each channel (Instagram, WhatsApp, Messenger, Telegram, Shopify, calendars): where the user clicks, what Meta requires first, and how long it really takes. Call this before advising anyone which channel to set up — Instagram works same-day, WhatsApp needs 2-6 weeks of Meta Business Verification. |
| list_conversationsA | List inbox conversations. Filter by status (active/closed/pending), platform (instagram/whatsapp/messenger), or assignee. |
| get_conversationA | Get a single conversation by ID, including customer details and last message. |
| list_messagesB | List messages in a conversation. Returns most recent first. |
| send_messageB | Send a reply message in a conversation. Use for responding to customers across Instagram, WhatsApp, or Messenger. |
| assign_conversationB | Assign or unassign a conversation to a team member. Pass null to unassign. |
| close_conversationC | Close an active conversation. |
| list_contactsC | List contacts (leads) in the workspace. Filter by platform. |
| get_contactC | Get a single contact by ID. |
| update_contactC | Update a contact name or lead stage. |
| list_channelsA | List connected social channels (Instagram, WhatsApp, Messenger pages). |
| get_analytics_summaryB | Get inbox analytics: message volume, response times, AI usage, conversion stats. |
| get_usageB | Get API usage stats for the current workspace: request counts, error rates, top endpoints. |
| list_templatesA | List WhatsApp templates with status, category, language, components, and optional usage stats. Use this before recommending sends or cleanup. |
| get_templateA | Get one stored WhatsApp template by InstantReply template ID. |
| validate_template_draftA | Validate a plain-language WhatsApp template objective before creating it. Returns policy risk, likely category, issues, and UTILITY coaching. |
| validate_templateA | Validate a stored WhatsApp template against Meta submission rules before submitting or rewriting. |
| submit_templateC | Create and submit a WhatsApp template to Meta from a flat developer-friendly shape. Ask for confirmation before use. |
| submit_stored_templateA | Submit an existing stored template draft to Meta for approval. Ask for confirmation before use. |
| delete_templateA | Delete a WhatsApp template from Meta and remove the local registry row. Destructive: only use after explicit user confirmation. |
| send_whatsapp_templateA | Trigger a WhatsApp journey/template send by trigger_name or journey_id. Use only for consented or transactional sends and ask before sending. |
| trigger_journeyB | Enroll one phone number in a WhatsApp journey by trigger_name or journey_id. Returns enrollment_id for status polling. |
| validate_journey_triggerA | Dry-run a journey trigger request. Use before send_whatsapp_template or trigger_journey to catch phone, journey, duplicate, and metadata errors. |
| check_journey_statusB | Check delivery status and failure explanation for a journey enrollment. |
| list_journey_historyC | List recent WhatsApp journey enrollments and delivery states. |
| trigger_journey_batchA | Bulk-enroll up to 100 recipients into a WhatsApp journey. Ask for explicit confirmation and validate a sample first. |
| get_developer_capabilitiesA | Show which API/MCP capabilities are allowed by the current API key scopes and plan tier. |
| get_developer_onboardingB | Get the developer onboarding checklist for the current workspace. |
| get_developer_limitsA | Get API rate limits, API key quota, and webhook endpoint quota for the current key plan tier. |
| recommend_planA | Recommend the right InstantReply plan from what you learn about the business in conversation — channels they want, expected monthly message volume, team size, and whether they need API/webhook access. Returns a recommendation with plain-language reasons, a cheaper alternative when one still fits, and a warning if WhatsApp needs Meta Business Verification. Use this before telling a user what to sign up for. |
| explain_delivery_failureA | Explain a Meta/WhatsApp delivery or template error code in plain English with next steps. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| draft_reply | Draft a reply to a customer message in your brand voice |
| summarize_conversation | Summarize a conversation for a quick handoff or review |
| find_urgent_unanswered | Identify urgent or unanswered messages that need immediate attention |
| weekly_inbox_digest | Generate a weekly performance digest from analytics data |
| suggest_macros | Suggest canned response macros based on recent conversation patterns |
| escalation_note | Write an internal escalation note for a difficult conversation |
| audit_template_cost | Audit WhatsApp templates for category, approval state, and cheaper UTILITY-safe alternatives |
| utility_rewrite_loop | Plan a safe rewrite-submit-poll loop for templates that should legitimately be UTILITY |
| journey_recommendation | Recommend WhatsApp journeys, trigger names, templates, and status checks for a business workflow |
| image_to_whatsapp_template_brief | Turn a provided image, campaign asset, or product screenshot into compliant WhatsApp template ideas |
| debug_last_failure | Explain the most recent WhatsApp delivery/template failure and recommend the next action |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 31 tools
Most tools target a distinct resource+action, and descriptions carefully differentiate near-neighbors (single vs batch journeys, draft vs stored template validation). However, pairs like submit_template vs submit_stored_template and send_whatsapp_template vs trigger_journey have fuzzy boundaries that could cause misselection.
Nearly every tool follows a predictable snake_case verb_noun pattern (get_/list_/send_/trigger_/validate_/submit_/delete_). The few outliers (recommend_plan, explain_delivery_failure, check_journey_status) still conform to verb-first naming, so there is no convention mixing.
31 tools is on the heavy side and pushes past the comfortable range, with several closely related variants (two validators, two submitters, single vs batch journey triggers). The genuinely broad domain (conversations, contacts, templates, journeys, analytics, developer tooling) partially justifies the count, but some consolidation is possible.
The surface covers full lifecycle for templates and journeys, plus conversation handling, analytics, and developer onboarding/limits/capabilities. Minor gaps exist—no contact creation/deletion and no channel connect/disconnect—but agents can work around these.