{
  "markdown": "# warp-mcp\n\nMCP server for the [Ringer WARP platform](https://warp.ringer.tel) — SIP trunking, phone numbers, porting, messaging/10DLC, billing, and CDR analytics.\n\nGives AI agents (Claude, Cursor, Copilot, Codex, ChatGPT) full access to the WARP Customer API: 135 tools covering trunk provisioning, number search and ordering, port-in lifecycle, 10DLC brand/campaign registration, SMS sending, invoices, and call-detail analytics.\n\n## Quick Start\n\n```bash\n# Recommended: global install — the setup wizard runs automatically\nnpm install -g warp-mcp\n\n# Or run the wizard explicitly / without installing\nnpx -y warp-mcp setup\n```\n\nThe wizard validates your API key, stores it in `~/.warp-mcp/config.json`, and registers the server with every MCP client it detects (Claude Code, Claude Desktop, Cursor, Codex, GitHub Copilot, ChatGPT Desktop).\n\nYou need a WARP API key (`rk_...`) — mint one in the [WARP portal](https://app.warp.ringer.tel) under **Settings → API Keys**.\n\n## One-command installs\n\n**Claude Code**\n\n```bash\nclaude mcp add -s user warp -e WARP_API_TOKEN=rk_your_key -- npx -y warp-mcp\n```\n\n**Cursor** — [click to install](cursor://anysphere.cursor-deeplink/mcp/install?name=warp&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIndhcnAtbWNwIl0sImVudiI6eyJXQVJQX0FQSV9UT0tFTiI6IllPVVJfV0FSUF9BUElfS0VZIn19) (then replace `YOUR_WARP_API_KEY`)\n\n**Manual (any MCP client)**\n\n```json\n{\n  \"mcpServers\": {\n    \"warp\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"warp-mcp\"],\n      \"env\": { \"WARP_API_TOKEN\": \"rk_your_key\" }\n    }\n  }\n}\n```\n\nSee [INSTALL.md](INSTALL.md) for per-client walkthroughs, troubleshooting, and uninstall steps.\n\n## Hosted endpoint\n\nNo local install needed — connect straight to `https://mcp.warp.ringer.tel/` (Streamable HTTP).\n\n**Desktop connectors (claude.ai, ChatGPT):** add a custom connector with that URL and\nsign in with your WARP account when prompted — the hosted endpoint authenticates via\nOAuth 2.1 and grants your customer-scoped permissions (excluding admin surfaces, Buzz,\nand API-key management — those stay in the portal).\n\n**Developer / CLI clients:** authenticate with a bearer `rk_` key instead:\n\n```bash\nclaude mcp add --transport http warp https://mcp.warp.ringer.tel/ \\\n  --header \"Authorization: Bearer $WARP_API_KEY\"\n```\n\n```json\n{\n  \"mcpServers\": {\n    \"warp\": {\n      \"type\": \"http\",\n      \"url\": \"https://mcp.warp.ringer.tel/\",\n      \"headers\": { \"Authorization\": \"Bearer rk_your_key_here\" }\n    }\n  }\n}\n```\n\nKeys are minted in the [WARP portal](https://app.warp.ringer.tel) under **Settings → API Keys**.\n\n## Tools\n\n| Prefix | Group | Tools | What it does |\n|---|---|---:|---|\n| `trunk_` | SIP Trunks | 24 | Trunk CRUD, SIP credentials, endpoints, IP ACLs, registrations |\n| `port_` | Porting | 33 | Port-in requests end to end: draft → validate → submit → activate, documents, TIN compliance |\n| `msg_` | Messaging | 33 | Send SMS, message history, 10DLC brands/campaigns, number enrollment, TCR reference data |\n| `num_` | Numbers | 15 | Search, order, release DIDs; per-TN voice/SMS config; port-out PINs |\n| `team_` | Team | 9 | Members and RBAC roles |\n| `bill_` | Billing | 5 | Balance, ledger, invoices (JSON + HTML) |\n| `cdr_` | Analytics | 5 | Call detail records, statistics, trends, CSV export |\n| `acct_` / `net_` / `key_` | Account | 10 | Capacity, utilization, scopes, WARP network IPs, API-key audit |\n| `warp_status` | Diagnostics | 1 | Config + connectivity check |\n\nThe server also ships a `warp-guide` prompt (and server instructions) with deep WARP domain knowledge — workflows, concepts, and common mistakes.\n\n## Environment variables\n\n| Variable | Default | Purpose |\n|---|---|---|\n| `WARP_API_TOKEN` | — | API key (`rk_...`). Overrides `~/.warp-mcp/config.json` |\n| `WARP_API_BASE_URL` | `https://api.warp.ringer.tel` | API base URL override |\n| `WARP_REQUEST_TIMEOUT_MS` | `30000` | Per-request timeout |\n\nToken resolution order: env var → `~/.warp-mcp/config.json` → unauthenticated (tools return guidance to run setup).\n\n## Development\n\n```bash\nnpm ci --ignore-scripts\nnpm run build   # tsc → dist/\nnpm test        # vitest (in-memory MCP transport)\nnpm run dev     # tsx src/index.ts\n```\n\nReleases are published from CI: `npm version patch|minor|major`, push with `--follow-tags`, create a GitHub release — the workflow publishes to npm (OIDC trusted publishing with provenance) and to the [MCP Registry](https://registry.modelcontextprotocol.io) (`io.github.ringer/warp`). Do not run `npm publish` locally after the initial release.\n\n## License\n\nMIT © [Ringer](https://ringer.tel)\n",
  "bytes": 4569,
  "sha": "fa1577891eeaa5f7cbdde05343b5f98d1d38434f949434d663f1e25d4ee22472",
  "repo_slug": "ringer/warp-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_ringer_warp_b0525b82/readme"
}