Infobip MCP Server

### 1. Basic Configuration This is a minimal, usable configuration for the Infobip MCP Server, assuming you have a local MCP binary/script called `infobip-mcp` on your PATH and a single API key. ```json { "Infobip MCP Server": { "command": "infobip-mcp", "args": [], "env": { "INFOBIP_API_KEY": "ibp_your_api_key_here", "INFOBIP_BASE_URL": "https://your-tenant.api.infobip.com" }, "disabled": false, "autoStart": true, "category": "Communication" } } ``` **Explanation (not part of JSON):** - `"Infobip MCP Server"`: The name Claude will show for this MCP server. - `"command"`: The executable or script that runs the Infobip MCP server. Adjust if your binary has a different name or path (e.g., `/usr/local/bin/infobip-mcp`). - `"args"`: Empty for the basic setup; the MCP server will use defaults. - `"env.INFOBIP_API_KEY"`: Your Infobip API key. Replace with a real key or use a secret manager and reference it here. - `"env.INFOBIP_BASE_URL"`: Your Infobip base URL/tenant endpoint. - `"disabled": false`: Ensures the server is active. - `"autoStart": true`: Claude Code will start this MCP server automatically when needed. - `"category": "Communication"`: Groups this server under a communication/messaging category in the UI. --- ### 2. Advanced Configuration This configuration shows a more complete setup: explicit logging, timeouts, environment separation, and custom arguments. It assumes the MCP server supports these common patterns. ```json { "Infobip MCP Server": { "command": "/usr/local/bin/infobip-mcp", "args": [ "--log-level=info", "--max-concurrent-requests=10", "--timeout-ms=15000", "--enable-webhook-tools" ], "env": { "INFOBIP_API_KEY": "ibp_prod_api_key_here", "INFOBIP_BASE_URL": "https://your-tenant.api.infobip.com", "INFOBIP_SENDER_ID": "MyBrand", "INFOBIP_DEFAULT_CHANNEL": "SMS", "INFOBIP_REGION": "EU", "INFOBIP_WEBHOOK_SECRET": "replace_with_strong_secret", "NODE_ENV": "production" }, "disabled": false, "autoStart": true, "category": "Communication", "restartOnExit": true, "metadata": { "description": "Infobip MCP Server with advanced options for messaging, voice, and webhook tools.", "tags": [ "infobip", "sms", "voice", "whatsapp", "notifications", "webhooks" ] } } } ``` **Explanation (not part of JSON):** - `"command"`: Absolute path to the MCP binary for reliability. - `"args"`: - `--log-level=info`: Enables structured logs at info level (adjust to `debug` for troubleshooting). - `--max-concurrent-requests=10`: Concurrency limit to protect Infobip and local resources. - `--timeout-ms=15000`: 15-second timeout per request. - `--enable-webhook-tools`: Hypothetical flag to expose webhook-related tools (delivery reports, inbound messages) to Claude. - `"env"`: - `INFOBIP_API_KEY`: Production API key. - `INFOBIP_BASE_URL`: Production Infobip endpoint. - `INFOBIP_SENDER_ID`: Default sender name/number for outbound messages. - `INFOBIP_DEFAULT_CHANNEL`: Default channel if the tool doesn’t specify one (`SMS`, `WHATSAPP`, etc.). - `INFOBIP_REGION`: Region hint for routing, logging, or multi-region setups. - `INFOBIP_WEBHOOK_SECRET`: Used to validate incoming webhook signatures if the MCP exposes webhook utilities. - `NODE_ENV`: Conventional environment flag for logging/behavior. - `"restartOnExit": true`: If the MCP process crashes or exits, Claude will restart it. - `"metadata.description"` and `"metadata.tags"`: Help organize and understand what this MCP server does in a multi-server environment. --- ### 3. Use Case Specific Configuration – Customer Support Notifications (Production) This configuration is tailored for a production customer-support setup, focusing on WhatsApp and SMS notifications triggered from support workflows (e.g., ticket updates, SLA alerts). ```json { "Infobip MCP Server - Support Notifications": { "command": "/opt/mcp/infobip-mcp", "args": [ "--log-level=warn", "--max-concurrent-requests=5", "--timeout-ms=20000", "--profile=support-notifications", "--restrict-tools=send_message,check_delivery_status,list_templates" ], "env": { "INFOBIP_API_KEY": "ibp_support_prod_api_key", "INFOBIP_BASE_URL": "https://support-tenant.api.infobip.com", "INFOBIP_SENDER_ID": "SupportDesk", "INFOBIP_DEFAULT_CHANNEL": "WHATSAPP", "INFOBIP_FALLBACK_CHANNEL": "SMS", "INFOBIP_REGION": "EU", "INFOBIP_TEMPLATE_NAMESPACE": "support_notifications", "INFOBIP_ALLOW_INTERNATIONAL": "false", "INFOBIP_RATE_LIMIT_PER_MINUTE": "60", "NODE_ENV": "production" }, "disabled": false, "autoStart": true, "category": "Communication", "restartOnExit": true, "metadata": { "description": "Infobip MCP Server dedicated to customer support notifications via WhatsApp and SMS.", "tags": [ "infobip", "support", "notifications", "whatsapp", "sms", "production" ], "useCase": "Customer support ticket updates, SLA alerts, and customer notifications." } } } ``` **Explanation (not part of JSON):** - Name: `"Infobip MCP Server - Support Notifications"` clearly indicates this is a specialized instance. - `"args"`: - `--log-level=warn`: Quieter logs for production; only warnings and errors. - `--max-concurrent-requests=5`: Conservative concurrency to avoid over-notifying or hitting rate limits. - `--timeout-ms=20000`: Slightly higher timeout for busy production APIs. - `--profile=support-notifications`: Hypothetical profile enabling support-specific defaults/features. - `--restrict-tools=send_message,check_delivery_status,list_templates`: Limits which tools Claude can call to avoid accidental misuse (e.g., no bulk-campaign tools). - `"env"`: - `INFOBIP_API_KEY` / `INFOBIP_BASE_URL`: Dedicated tenant/key for support traffic. - `INFOBIP_SENDER_ID`: Branded sender for support communications. - `INFOBIP_DEFAULT_CHANNEL`: Primary channel is WhatsApp (better for rich, conversational support). - `INFOBIP_FALLBACK_CHANNEL`: If WhatsApp is unavailable or user is not opted-in, fall back to SMS. - `INFOBIP_TEMPLATE_NAMESPACE`: Namespace for pre-approved support templates (ticket opened, ticket updated, etc.). - `INFOBIP_ALLOW_INTERNATIONAL`: `"false"` to prevent sending to non-domestic numbers (compliance/cost control). - `INFOBIP_RATE_LIMIT_PER_MINUTE`: Soft limit for the MCP to throttle itself before hitting provider limits. - `NODE_ENV`: Production environment. - `"restartOnExit": true`: Ensures continuous availability for critical support notifications. - `"metadata.useCase"`: Documents that this instance is strictly for customer support workflows, helpful in teams or multi-MCP setups.