Connect AI agents to BroadNet with MCP.

What the MCP server is

The Model Context Protocol (MCP) is an open standard that lets AI assistants discover and call external tools. The BroadNet MCP server is a remote MCP server: your client connects to it over HTTPS, lists the tools it offers, and calls them on your behalf.

The tools map to the same BroadNet API documented in the API reference and the OpenAPI spec — sending messages, working with WhatsApp templates, reading delivery reports. The agent acts with the permissions of the token you give it, exactly as your own code would.

Two MCP servers: knowledge and messaging

BroadNet runs two MCP servers. The messaging server described on this page acts on your account. The knowledge server is public: an agent can ask it about BroadNet's coverage, sender-ID rules, published list prices, regulations and company facts without a login.

Try the knowledge server from a terminal: the initialize handshake, then a tool call.

curl -X POST https://www.broadnet.me/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize",
       "params":{"protocolVersion":"2025-06-18","capabilities":{},
                 "clientInfo":{"name":"curl","version":"1.0"}}}'

curl -X POST https://www.broadnet.me/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "MCP-Protocol-Version: 2025-06-18" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call",
       "params":{"name":"sender_id_rules","arguments":{"country":"ae"}}}'

Endpoint and authentication

There is one endpoint for every account: https://mcp.broadnet.me/mcp. Every request must carry your BroadNet token in an Authorization header.

You get the token from your BroadNet account. In the demo it is generated in the BroadAdmin portal under Integrations → MCP Integration with “Get temporary key”; the portal notes that a permanent key is issued by your account admin or master account.

A request without the header is refused at the protocol level — this is the server's actual reply to an unauthenticated initialize call:

event: message
data: {"jsonrpc":"2.0","id":1,"error":{"code":-32001,
  "message":"Authorization bearer token is required. Connect with an
  'Authorization: Bearer <BroadNet token>' header."}}

Connect an MCP client

Most MCP clients take a JSON configuration with the server URL and request headers. A typical entry looks like this:

{
  "mcpServers": {
    "broadnet": {
      "type": "http",
      "url": "https://mcp.broadnet.me/mcp",
      "headers": {
        "Authorization": "Bearer ${BROADNET_TOKEN}"
      }
    }
  }
}

To test the connection without a client, send the MCP initialize request yourself:

curl -X POST https://mcp.broadnet.me/mcp \
  -H "Authorization: Bearer $BROADNET_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize",
       "params":{"protocolVersion":"2025-06-18","capabilities":{},
                 "clientInfo":{"name":"curl","version":"1.0"}}}'

What the demo shows

The product team's recording walks through the whole flow in five steps, using Cursor as the MCP client:

1. 1
   Sign in

   Log in to the BroadAdmin portal with your BroadNet account.

2. 2
   Get a key and the configuration

   Open Integrations → MCP Integration, generate a temporary key and copy the ready-made client configuration.

3. 3
   Add the server to the client

   In the MCP client, add a new MCP server and paste the configuration into mcp.json — URL https://mcp.broadnet.me/mcp with the Bearer header.

4. 4
   Review the tools

   The client connects and lists the BroadNet tools, each of which can be switched on or off.

5. 5
   Ask in plain language

   The user asks the agent to send a WhatsApp message to a number. The agent picks the WhatsApp send tool, the API answers HTTP 200 with the message accepted, and the message arrives in WhatsApp from the business account.

In the recording the client reports 380 BroadNet tools, among them send_message, post_sms_send, post_whatsapp_message_send, get_whatsapp_template_list, post_whatsapp_template_send, post_rcs_message_send, post_telegram_message_send, post_instagram_message_send, post_messenger_message_send, post_push_message_send and get_report_delivery. The exact list depends on the server version and your account.

A narrated version of the same recording adds an overview card: one MCP endpoint, the same copy-and-paste steps for every agent.

Security notes

• The token is a send credential

  Anyone holding it can send messages from your account. Store it like a password, never in a shared or committed file.

• Prefer temporary keys for experiments

  Use a temporary key while you try things out, and ask your account admin for a permanent key only for a production agent.

• Enable only the tools you need

  MCP clients let you switch individual tools off. An agent that only sends SMS doesn't need template, onboarding or account tools.

• Keep a human in the loop

  Agents act on natural-language instructions. Have the client ask for confirmation before tools that send messages, especially to many recipients.

• Revoke a leaked token

  If a token is exposed, contact your account admin or BroadNet support to revoke it and issue a new one.

Related

Questions