Provisioning MCP

EARLY ACCESS

Provisioning MCP is an MCP server for sender registration and number setup workflows.

Before an AI agent can send messages, the right resources must be in place: a registered sender name, a purchased phone number, or a configured channel sender. Provisioning MCP puts that setup process directly into an agent workflow.

IMPORTANT

Provisioning MCP is available in early access. To join the program, contact mcp@infobip.com.

Core capabilities

Provisioning MCP supports three core capabilities:

Requirement lookup
Understand what a workflow needs before starting, including required steps, mandatory data fields, and documentation for a given channel and country.

Provisioning execution
Run the workflow steps in sequence. The agent collects required data, submits each step, and handles corrections if a step is rejected.

Status checks
Review submission status and identify the current state of any active provisioning workflow.

There are three ways to set up resources on Infobip:

Web interface: Navigate the Infobip portal manually to register senders, purchase numbers, and configure channels.
APIs: Integrate Infobip provisioning APIs directly into your systems.
Provisioning MCP: Let an AI agent handle setup for you. The agent collects the required information, applies the right rules for the target channel and market, and submits the provisioning request in a single conversation.

What it can do

With Provisioning MCP, you do not need to learn per-country registration rules or navigate multi-step workflows manually. The agent:

Identifies the right workflow for any supported channel and country combination
Collects only the data required at each step
Tracks progress across Infobip, carriers, and regulators in real time
Resumes interrupted workflows without losing progress
Handles rejected steps by collecting corrections and resubmitting

During early access, you also get:

Access to Provisioning MCP without any charges
Direct line to the Infobip product and engineering team
Influence on the general availability roadmap

How the provisioning workflow works

The agent orchestrates the full provisioning flow, selecting the right steps, gathering the required data, and adapting to the target channel and market without integration logic on your side.

User requests registration
The user asks the agent to register a sender or purchase a number for a specific channel and country.

Agent fetches the registration plan
The agent retrieves the registration requirements for the target channel and country, including required steps and data fields.

Agent collects data and submits
The agent collects the required information from the user and submits the registration request. If a workflow requires documents, the server provides a URL where you can upload them.

Registration is processed
The request is submitted across Infobip, carriers, and regulators. The agent tracks progress across all systems.

Agent handles corrections if needed
If a step is rejected, the agent collects the missing data or correction from the user and resubmits.

You can check registration status and progress at any point during the workflow.

When requirements change (for example, new markets, new carrier rules, new regulations) Infobip updates the provisioning logic. Your integration stays the same.

Supported channels and markets

Availability is limited to selected markets in EMEA and North America.

Channel	Supported actions	Notes
SMS	SMS alphanumeric sender registration	Supported in United States, Canada, France, United Kingdom, Spain, Poland, Norway, Italy, Sweden, Netherlands, Ireland, Switzerland, Portugal, Germany, Croatia, Australia, New Zealand
10DLC	Brand registration, campaign registration	United States only
VLN (virtual long number)	VLN registration	Buys a recommended VLN. Stock selection is not available.
RCS	RCS sender registration	Supported in Austria, Brazil, Canada, Colombia, Czech Republic, Denmark, Dominican Republic, France, Germany, Greece, Guatemala, India, Indonesia, Italy, Mexico, Netherlands, Nigeria, Norway, Peru, Poland, Singapore, Slovakia, Spain, Sweden, Ukraine, United Kingdom, United States

Connect and authenticate

NOTE

The channel must already be provisioned on your account before you can register a sender, purchase a number, or set up other resources.

Provisioning MCP supports both API key and OAuth 2.1 authentication.

Endpoint: https://mcp.infobip.com/provision

To connect with an API key:

Create an API key in the API keys page and assign the mcp:provision scope.
Add the endpoint to your MCP client configuration with an Authorization header:

json
1{
2 "mcpServers": {
3 "provisioning": {
4 "type": "http",
5 "url": "https://mcp.infobip.com/provision",
6 "headers": {
7 "Authorization": "App <API_KEY>"
8 }
9 }
10 }
11}
Restart your MCP client.

To connect with OAuth 2.1:

Add the endpoint to your MCP client configuration without an Authorization header.
Restart your MCP client.
When prompted, sign in with your Infobip credentials and authorize the required scopes.

For step-by-step setup in your AI client, see Integrate a remote MCP server with an MCP client or, for Claude Desktop specifically, Integrate the Infobip MCP server with Claude Desktop.

Learn more

See the full guide on authentication methods, transport options, and configuration examples.

Related pages

Resources and numbers
How resources work and what types are available.

US sender registration
US-specific registration requirements for SMS.

Using Infobip MCP servers
Authentication, transport options, and available endpoints.

Integrate a remote MCP server with an MCP client
Step-by-step setup for any MCP-compatible client.

Integrate the Infobip MCP server with Claude Desktop
Claude Desktop-specific setup, including Connectors UI and JSON config.

Interested in Provisioning MCP?

Join the early access program to start automating channel registration with AI agents.

Was this page helpful?