Guide · 5 min read

The Model Context Protocol (MCP) lets AI assistants use tools. The SwarmSMS Agency plan includes an MCP server, so you can ask an assistant things like “how did last week’s campaigns perform?” or “text Sam that his order has shipped”.

Step 1: Enable it and create a key

In WordPress open SwarmSMS → MCP, tick Enable the MCP server and create a key. Choose read-only if you only want the assistant to look at stats, or full access if it may send messages and create campaigns. The key is shown once — treat it like a password.

Step 2: Add it to your tool

The MCP tab shows ready-made commands filled with your site’s address and key. For example:

Claude Code

claude mcp add --transport http swarmsms https://your-site.com/wp-json/wpsg/v1/mcp \
  --header "Authorization: Bearer YOUR_KEY"

OpenAI Codex (config.toml)

[mcp_servers.swarmsms]
url = "https://your-site.com/wp-json/wpsg/v1/mcp"
bearer_token_env_var = "SWARMSMS_API_KEY"

Cursor, VS Code and Claude Desktop snippets are on the same tab. If your host strips the Authorization header, send the key as X-API-Key instead.

What the assistant can do

• Account summary: messages today, delivery rates, queue, phones online
• Send SMS (full-access keys), list and read messages
• Device stats per phone
• Search contacts; add a contact (only with consent) or unsubscribe one
• List campaigns, read stats, create a campaign (as a draft unless you say start), pause, resume or stop

One-time login codes are never exposed to AI tools, and sending still obeys opt-outs, sending rules and each phone’s daily limit.

Try these prompts

• “Give me an account summary and tell me if any phone looks unhealthy.”
• “Compare delivery rates for the last 30 days per phone.”
• “Create a draft two-step campaign for the VIP list: an offer now and a reminder three days later.”

Safety tips

Start with a read-only key. Review any campaign before you start it. Revoke keys you no longer use under API & Webhooks.