MCP · Model Context Protocol

Run WARP from your AI assistant

warp-mcp gives Claude, Cursor, Copilot, Codex, and ChatGPT full access to the WARP Customer API — 135 tools covering trunk provisioning, number search and ordering, the port-in lifecycle, 10DLC registration, SMS sending, invoices, and call-detail analytics. It runs locally over stdio, authenticated with your own scoped API key.

Run it from npm, or connect to the hosted endpoint at mcp.warp.ringer.tel — no local install required.

Hosted endpoint

No local install, no Node.js version to manage — point any Streamable HTTP-capable MCP client at https://mcp.warp.ringer.tel/.

Desktop connectors (claude.ai, ChatGPT)

Add a custom connector with the URL above, then sign in with your WARP account when prompted — the hosted endpoint authenticates via OAuth 2.1 and grants your customer-scoped permissions (excluding admin surfaces, Buzz, and API-key management — those stay in the portal).

Developer clients (Claude Code, scripts, CI)

Authenticate with a bearer rk_ key instead:

shell

claude mcp add --transport http warp https://mcp.warp.ringer.tel/ \
  --header "Authorization: Bearer $WARP_API_KEY"

mcp config (JSON)

{
  "mcpServers": {
    "warp": {
      "type": "http",
      "url": "https://mcp.warp.ringer.tel/",
      "headers": { "Authorization": "Bearer rk_your_key_here" }
    }
  }
}

Keys are minted in the WARP portal under Settings → API Keys.

Install locally (npm)

Requires Node.js ≥ 20.

terminal

$npm install -g warp-mcp
# The setup wizard runs automatically on global install:
✓Validates your API key against the live API
✓Saves it to ~/.warp-mcp/config.json
✓Registers the server with the MCP clients it detects
# Re-run anytime:
$warp-mcp setup

Your API key

You need a WARP API key (rk_...) — mint one in the WARP portal under Settings → API Keys. Test keys start with rk_test_. Resolution order: WARP_API_TOKEN env var → ~/.warp-mcp/config.json. Keys can only be created in the portal — rotate or revoke compromised keys there immediately.

Per-client setup

The setup wizard registers detected clients automatically — these are the manual equivalents.

Claude Code

One command; also installable as a Claude Code plugin (prompts for your key securely).

shell

$claude mcp add -s user warp -e WARP_API_TOKEN=rk_your_key -- npx -y warp-mcp

Claude Desktop

Add to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/).

claude_desktop_config.json

{
  "mcpServers": {
    "warp": {
      "command": "npx",
      "args": ["-y", "warp-mcp"],
      "env": { "WARP_API_TOKEN": "rk_your_key" }
    }
  }
}

Cursor

Edit ~/.cursor/mcp.json with the same JSON block (a one-click deeplink install is in the package README).

~/.cursor/mcp.json

{
  "mcpServers": {
    "warp": {
      "command": "npx",
      "args": ["-y", "warp-mcp"],
      "env": { "WARP_API_TOKEN": "rk_your_key" }
    }
  }
}

Codex (CLI + Desktop)

Codex Desktop shares ~/.codex/config.toml with the CLI, so this covers both.

shell

$codex mcp add warp --env WARP_API_TOKEN=rk_your_key -- npx -y warp-mcp

GitHub Copilot (VS Code)

Add the server under "github.copilot.chat.mcp.servers" in VS Code settings.json.

settings.json

{
  "mcpServers": {
    "warp": {
      "command": "npx",
      "args": ["-y", "warp-mcp"],
      "env": { "WARP_API_TOKEN": "rk_your_key" }
    }
  }
}

ChatGPT Desktop

Settings → Developer Mode → Add MCP server: command npx, args -y warp-mcp, env WARP_API_TOKEN.

Tool catalog

135 tools, grouped by prefix. The server also ships a warp-guide prompt with WARP domain knowledge — workflows, concepts, and common mistakes.

Prefix	Group	Tools	What it does
trunk_	SIP Trunks	24	Trunk CRUD, SIP credentials, endpoints, IP ACLs, registrations
port_	Porting	33	Port-in end to end: draft → validate → submit → activate, documents, TIN compliance
msg_	Messaging	33	Send SMS, message history, 10DLC brands/campaigns, number enrollment
num_	Numbers	15	Search, order, release DIDs; per-TN voice/SMS config; port-out PINs
team_	Team	9	Members and RBAC roles
bill_	Billing	5	Balance, ledger, invoices (JSON + HTML)
cdr_	Analytics	5	Call detail records, statistics, trends, CSV export
acct_ / net_ / key_	Account	10	Capacity, utilization, scopes, WARP network IPs, API-key audit
warp_status	Diagnostics	1	Config + connectivity check

Verify the install

Ask your agent to run the warp_status tool — it reports the server version, whether a key is configured, and whether the API accepts it. Or from a terminal:

shell

$npx -y @modelcontextprotocol/inspector --cli npx -y warp-mcp --method tools/list

The MCP tools call the same REST API documented in the API reference — same scopes, same envelope, same per-customer isolation.