Warp

io.github.RingerPublished by GitHub account Ringerv1.1.0Updated Oct 24, 2026

SIP trunking, numbers, porting, messaging, billing, and CDR analytics on the Ringer WARP platform

VerifiedSTDIODesktop onlyCommunication & CollaborationData & AnalyticsBusiness & Commerce

Overview

AI-generated overview

Lets an assistant manage Ringer WARP telecom services: SIP trunks, phone numbers, porting, SMS/10DLC, billing, and call-detail analytics.

What you can do
Wraps the WARP Customer API in roughly 135 tools grouped by prefix: trunk_ for SIP trunk CRUD, credentials, endpoints, IP ACLs and registrations; port_ for port-in requests from draft to activation, documents and TIN compliance; msg_ for sending SMS, message history and 10DLC brand/campaign registration; num_ for searching, ordering and releasing DIDs and port-out PINs; team_ for members and RBAC; bill_ for balance, ledger and invoices; cdr_ for call detail records, statistics, trends and CSV export; acct_/net_/key_ for capacity, scopes, network IPs and API-key audit; plus warp_status diagnostics. It also ships a warp-guide prompt with WARP domain knowledge.
When to use it
Use it when an assistant needs to operate or inspect Ringer WARP telecom accounts: provisioning or changing SIP trunks, buying or releasing numbers, driving port-in workflows, registering 10DLC brands and campaigns, sending SMS, or reviewing invoices and call-detail analytics.
Requirements
A local Node.js runtime for the npm package warp-mcp (stdio), or the hosted Streamable HTTP endpoint. Authentication needs a WARP API key (rk_...) supplied as WARP_API_TOKEN, or OAuth 2.1 sign-in for the hosted endpoint. Optional overrides: WARP_API_BASE_URL and WARP_REQUEST_TIMEOUT_MS. Network access to the WARP API. Desktop clients only.
Before you install
The API key WARP_API_TOKEN is a secret granting account-level access; the wizard stores it in ~/.warp-mcp/config.json. Many tools write or change live telecom resources — trunk and endpoint configuration, number orders and releases, port-in submissions, SMS sends, 10DLC registrations — and some may incur charges or affect service. The hosted endpoint excludes admin surfaces, Buzz and API-key management. Review actions before letting an assistant execute them.

Installation

In SourceWeft

  1. Open Warp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

warp-mcp

MCP server for the Ringer WARP platform — SIP trunking, phone numbers, porting, messaging/10DLC, billing, and CDR analytics.

Gives 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.

Quick Start

bash
# Recommended: global install — the setup wizard runs automaticallynpm install -g warp-mcp
# Or run the wizard explicitly / without installingnpx -y warp-mcp setup

The 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).

You need a WARP API key (rk_...) — mint one in the WARP portal under Settings → API Keys.

One-command installs

Claude Code

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

Cursor — click to install (then replace YOUR_WARP_API_KEY)

Manual (any MCP client)

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

See INSTALL.md for per-client walkthroughs, troubleshooting, and uninstall steps.

Hosted endpoint

No local install needed — connect straight to https://mcp.warp.ringer.tel/ (Streamable HTTP).

Desktop connectors (claude.ai, ChatGPT): add a custom connector with that URL and 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 / CLI clients: authenticate with a bearer rk_ key instead:

bash
claude mcp add --transport http warp https://mcp.warp.ringer.tel/ \  --header "Authorization: Bearer $WARP_API_KEY"
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.

Tools

PrefixGroupToolsWhat it does
trunk_SIP Trunks24Trunk CRUD, SIP credentials, endpoints, IP ACLs, registrations
port_Porting33Port-in requests end to end: draft → validate → submit → activate, documents, TIN compliance
msg_Messaging33Send SMS, message history, 10DLC brands/campaigns, number enrollment, TCR reference data
num_Numbers15Search, order, release DIDs; per-TN voice/SMS config; port-out PINs
team_Team9Members and RBAC roles
bill_Billing5Balance, ledger, invoices (JSON + HTML)
cdr_Analytics5Call detail records, statistics, trends, CSV export
acct_ / net_ / key_Account10Capacity, utilization, scopes, WARP network IPs, API-key audit
warp_statusDiagnostics1Config + connectivity check

The server also ships a warp-guide prompt (and server instructions) with deep WARP domain knowledge — workflows, concepts, and common mistakes.

Environment variables

VariableDefaultPurpose
WARP_API_TOKEN—API key (rk_...). Overrides ~/.warp-mcp/config.json
WARP_API_BASE_URLhttps://api.warp.ringer.telAPI base URL override
WARP_REQUEST_TIMEOUT_MS30000Per-request timeout

Token resolution order: env var → ~/.warp-mcp/config.json → unauthenticated (tools return guidance to run setup).

Development

bash
npm ci --ignore-scriptsnpm run build   # tsc → dist/npm test        # vitest (in-memory MCP transport)npm run dev     # tsx src/index.ts

Releases 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 (io.github.ringer/warp). Do not run npm publish locally after the initial release.

License

MIT © Ringer

Source: README.md at commit 0053959

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts