Integrate a remote MCP server with an MCP Client

MCP (opens in a new tab) is an open protocol that standardizes how applications provide context to AI models​. The Infobip MCP server (opens in a new tab) allows LLMs to use Infobip CPaaS Platform tools.

This tutorial will show you how to integrate an Infobip MCP server with an MCP Client, like Cursor (opens in a new tab) or Claude desktop (opens in a new tab) to use it with Infobip APIs.

Prerequisites

• Node.js v 18 upwards.
• Infobip account (opens in a new tab). If you do not have one create a free trial account (opens in a new tab).
• An MCP Client, e.g. Cursor or Claude Desktop.

Cursor MCP Integration

Skip this section if integrating with Claude Desktop (see the section below).

1. Open Cursor and navigate to Cursor Settings.
2. On the left-hand side, click MCP.
3. Click the +Add new global MCP server button.
4. Populate the mcp.json connection to a remote MCP server with the Infobip MCP server settings (see section below).
5. Make sure that MCP server is enabled and you see list of tools
6. Use Chat to initiate Infobip APIs.

Claude Desktop MCP Integration

1. Open Claude Desktop and navigate to Settings.
2. Use the Developer tab to click the Edit config button. This will show you the location of the claude_desktop_config.json file in your file system. You'll use the file to add the Infobip MCP server settings.
3. Access the claude_desktop_config.json file and populate with the connection settings to the Infobip MCP server (see section below).
4. Restart Claude desktop.
5. Use Chat to initiate Infobip APIs.

Infobip MCP Server settings

Each Infobip API endpoint is served as a separate MCP server to narrow down the context for the AI agent in use. As such, you need to add each endpoint aka server separately.

To configure an MCP server:

1. Choose an authentication method, API Key or OAuth and which server you want to connect to. For the list of all supported MCP endpoints, check out the Infobip MCP documentation (opens in a new tab).

   Integration example with an API key

   Key points:

   • You can access and edit your API key from your Infobip account (opens in a new tab).
   • Your API key must include the correct scope depending on the MCP server you want to integrate. For example, if you want to use the SMS MCP server, your API Key needs the sms:message:send scope. Find out more about scopes in API Authorization.
   json

   {
     "mcpServers": {
       "ib-viber": {
         "command": "npx",
         "args": [
           "mcp-remote",
           "https://mcp.infobip.com/viber",
           "--header",
           "Authorization: App ${INFOBIP_API_KEY}"
         ],
         "env": {
           "INFOBIP_API_KEY": "<Your Infobip API Key here>"
         }
       }
     }
   }

   Integration example with OAuth

   Key points:

   • Your MCP client must support OAuth 2.1 authentication and dynamic OAuth authorization server metadata discovery (opens in a new tab).
   • For MCP clients that don't support automatic scopes_supported discovery, you must manually configure scopes available to view: {mcp-server-url}/.well-known/oauth-authorization-server
   REQUEST SAMPLES

   without scopeswith scopes

   {
     "mcpServers": {
       "infobip-sms": {
         "command": "npx",
         "args": [
           "mcp-remote",
           "https://mcp.infobip.com/sms"
         ]
       }
     }
   }

2. Restart your MCP client.

Additional resources

• Infobip MCP docs (opens in a new tab)
• Infobip MCP GitHub repo (opens in a new tab)
• mcp-remote docs (opens in a new tab)