Can AI agents automate Infobip?

Infobip is automatable today through first-party remote MCP servers and its REST APIs. This record is the Infobip CPaaS platform as exposed at https://mcp.infobip.com/{mcp-tool}, including SMS, WhatsApp, RCS, Viber, Voice, 2FA, push (Mobile App Messaging), People customer data, documentation search, and Provisioning MCP. It is not Twilio, Telnyx, or Vonage. Hosted MCP servers use streamable HTTP (SSE via /sse) and authenticate with Authorization: App {API_KEY} or OAuth 2.1 with authorization-server metadata discovery. Documented execute servers include mcp.infobip.com/sms, /whatsapp, /rcs, /viber, /voice, /2fa, /mobile-app-messaging, /people, and /search. Provisioning MCP at https://mcp.infobip.com/provision is early access (join via mcp@infobip.com); it is not general-availability coverage for sender registration or number purchase. REST calls use a tenant-specific base URL of the form {subdomain}.api.infobip.com and JSON. The documented recommended REST auth is an API key in Authorization: App {key}; the same authentication page also documents OAuth 2.0 client-credentials Bearer tokens. Official auto-generated API clients cover Java, C#, PHP, Go, and Python. Product webhooks POST delivery, inbound, and related events. iPaaS connector catalogs were not opened. An official Infobip CLI was not established. Computer-use viability is unassessed. API and MCP each score 8. MCP is the best path because it is the vendor agent interface with named per-channel execute tools; API is the documented production HTTP surface with OpenAPI and official SDKs.

Best path today: mcp · Overall automatability: 8/10