--- title: "Cursor + OmniChannels.ai: send and track messages while you build" description: "Add the OmniChannels.ai MCP server to Cursor with .cursor/mcp.json so its agent can send WhatsApp, SMS and RCS test messages and read delivery reports." canonical: "https://omnichannels.ai/integrations/cursor/" language: "en" updated: "2026-10-10" publisher: "BroadNet Technologies" brand: "OmniChannels.ai" --- # Cursor + OmniChannels.ai: send and track messages while you build Canonical: https://omnichannels.ai/integrations/cursor/ Language: en Publisher: OmniChannels.ai by BroadNet Technologies **In short:** Cursor connects to OmniChannels.ai through our remote MCP server at https://mcp.broadnet.me/mcp. Add it to .cursor/mcp.json with your token in an Authorization header read from an environment variable. Cursor's agent can then send WhatsApp, SMS and RCS messages, list approved templates and read delivery reports, asking for approval before each tool call. No extension is needed. Connect via MCP · Connect via API & webhooks ## What you can do ### Send test messages while coding Check a message flow end to end without leaving the editor, sending only to your verified numbers. > Try asking: "Send a WhatsApp message to 971500000000 saying the order has shipped." ### Look up template names and variables The agent lists approved WhatsApp templates so the code you write uses the exact names and parameters. > Try asking: "List my approved WhatsApp templates in Arabic and show the variables each one expects." ### Debug delivery problems Read the delivery report for a message your code just sent and see why it failed. > Try asking: "Check the delivery report for the last message I sent and explain any failure." ### Write integration code from the spec Give the agent our OpenAPI spec so the REST calls it writes use the exact fields, including multipart sends. > Try asking: "Using the OpenAPI spec, write a TypeScript function that sends a bulk SMS campaign." ## How it connects OmniChannels.ai runs a remote MCP server over Streamable HTTP. Cursor reads MCP servers from .cursor/mcp.json in a project or ~/.cursor/mcp.json for every project, and resolves ${env:NAME} in the url and headers fields, so the token can stay in an environment variable instead of the file. Once connected, Cursor lists the server's tools in its MCP settings, where you can switch each one on or off. Cursor asks for approval before running an MCP tool by default and shows the arguments first. Keep approval on for every tool that sends, since each send is a real, billed message. - Endpoint: https://mcp.broadnet.me/mcp (Streamable HTTP) - Header: Authorization: Bearer ${env:BROADNET_TOKEN} - Config: .cursor/mcp.json (project) or ~/.cursor/mcp.json (global) - Troubleshoot in the Output panel under MCP Logs ## Set it up 1. **Request API access:** Request test access and receive an API token. Test sends go only to your own verified numbers. 2. **Get an MCP key:** In the admin portal open Integrations, then MCP Integration, and choose Get temporary key. (Guide: https://omnichannels.ai/developers/mcp/) 3. **Add the server to mcp.json:** Add an omnichannels entry under mcpServers with our URL and an Authorization header that reads ${env:BROADNET_TOKEN}. (Guide: https://omnichannels.ai/developers/mcp-cursor/) 4. **Set the variable and restart:** Set BROADNET_TOKEN in the environment Cursor starts from, such as your shell profile, then restart Cursor. 5. **Review the tools:** In Cursor's MCP settings, switch off every tool the agent does not need and keep approval on for send tools. 6. **Send a first message:** Ask the agent to send a test message to your verified number, approve the call, then check the delivery report. ## Example workflow Cursor agent (A request in the agent chat) → OmniChannels.ai MCP server (Tool runs after you approve the call) → Your test phone (WhatsApp, SMS or RCS message delivered) → Delivery report (The agent reads the status back with a read tool) ## Questions ### Is there an official OmniChannels.ai extension for Cursor? No. Cursor connects through its standard MCP support, using our public MCP endpoint and your API token in .cursor/mcp.json. Nothing needs to be installed. ### Can I commit .cursor/mcp.json to my repository? Yes, if the token is read from an environment variable with ${env:BROADNET_TOKEN}. The ready-made configuration from the portal contains the key itself, so keep that version out of version control. ### The server shows an error or no tools. What should I check? Open the Output panel and choose MCP Logs. An authorization error means the header is missing or the key is wrong or expired. An empty variable means Cursor was started without BROADNET_TOKEN set. ### Which channels can the agent send on? The tools cover sending on each channel enabled on your account, for example SMS, WhatsApp, RCS, Telegram, Messenger, Instagram and push. The exact tool list depends on the server version and your account. ## Developer guides - https://omnichannels.ai/developers/mcp-cursor/ - https://omnichannels.ai/developers/mcp/ - https://omnichannels.ai/developers/openapi/ - https://omnichannels.ai/developers/errors-and-limits/ ## Vendor documentation - [Model Context Protocol in Cursor](https://cursor.com/docs/context/mcp) - [Model Context Protocol — introduction](https://modelcontextprotocol.io/introduction) ## Related integrations - https://omnichannels.ai/integrations/claude-code/ - https://omnichannels.ai/integrations/vs-code/ - https://omnichannels.ai/integrations/claude/ - https://omnichannels.ai/integrations/langchain/ Cursor is a trademark of its owner. OmniChannels.ai is not affiliated with or endorsed by Cursor; this page describes a connection built with Cursor's own MCP, HTTP or webhook features. Updated: 2026-10-10