Cursor's agent can use the MCP server to send and track messages on your account while you build. Cursor is the client used in BroadNet's own MCP demo: the agent connects, lists the messaging tools, and sends a WhatsApp message from a plain-language request. Cursor's documentation is the reference for its configuration format: Model Context Protocol in Cursor.
| Setting | Value |
|---|---|
| Server URL | https://mcp.broadnet.me/mcp |
| Transport | Streamable HTTP |
| Authentication | Authorization: Bearer <token> header |
| Token | A temporary key from Integrations → MCP Integration in the admin portal, or a permanent key from your account admin |
1. Get a key#
In the admin portal open Integrations → MCP Integration and choose Get temporary key. The page also offers a ready-made client configuration to copy. Use a temporary key while you try things out; a permanent key for a production agent comes from your account admin or master account.
2. Add the server#
Cursor reads MCP servers from two files:
| File | Scope |
|---|---|
.cursor/mcp.json in a project |
That project only. Good for a team, as long as the token is not in the file. |
~/.cursor/mcp.json in your home directory |
Every project you open. |
Add the server under mcpServers. Cursor resolves ${env:NAME} in the url and headers fields, so the token can stay in an environment variable:
.cursor/mcp.json
{
"mcpServers": {
"omnichannels": {
"url": "https://mcp.broadnet.me/mcp",
"headers": {
"Authorization": "Bearer ${env:BROADNET_TOKEN}"
}
}
}
}Set BROADNET_TOKEN in the environment Cursor starts from (for example your shell profile), then restart Cursor. If you paste the ready-made configuration from the portal instead, it contains the key itself: keep that file out of version control.
3. Review the tools#
Open Cursor's MCP settings. Once connected, the server lists its tools, and you can switch each one on or off. Switch off everything the agent does not need: an agent that only answers delivery questions does not need send tools, and none of your agents need account or onboarding tools.
Cursor asks for approval before it runs an MCP tool by default, and shows the tool's arguments before you approve. Keep approval on for every tool that sends: each send is a real, billed message.
4. Ask in plain language#
In the agent chat, for example:
- "Send a WhatsApp message to 971500000000 saying the order has shipped." (The agent picks the WhatsApp send tool and shows you the call to approve.)
- "List my approved WhatsApp templates in Arabic."
- "Check the delivery report for the last message I sent."
For writing integration code rather than sending, give the agent the OpenAPI spec so it uses the exact request fields.
Troubleshooting#
| Symptom | What to check |
|---|---|
| The server shows an error or no tools | Open the Output panel and choose MCP Logs. An authorization error means the header is missing or the key is wrong or expired. |
${env:BROADNET_TOKEN} is empty |
Cursor was started from an environment where the variable is not set. Set it and restart Cursor. |
| A field in the configuration is not recognised | Configuration formats change between Cursor versions. Compare with Cursor's MCP documentation. |
| A tool call returns an API error | The tool acts with your account's permissions, sender IDs and balance. See Errors and limits. |
Next steps#
- MCP server: endpoint, keys and safe-use rules for every client.
- Use the MCP server with Claude Code.
- Use the MCP server with n8n.
Ready to send your first message?
Request test credentials. An engineer sets up your account, and test sends go to your own verified numbers.
Request test access