thatmgmt-mcp

An MCP (Model Context Protocol) server that wraps the ThatMgmt domain API. An AI agent in Cursor, Claude Code, or Replit can check availability, get name suggestions, lock a price quote, and prepare a registration, all without touching a dashboard.

Base API: https://api.thatmgmt.com Spec: https://thatmgmt.com/openapi.json (47 routes) Machine docs: https://thatmgmt.com/llms-full.txt

Try it with zero signup (no API key)

The public reads need no key and no account. Run the published package with zero install: npx -y @thatmgmt/mcp. Or clone and run:

git clone https://github.com/thingscorp/thatmgmt-mcp.git thatmgmt-mcp
cd thatmgmt-mcp
npm install
node src/index.js

Then in your MCP client, call tmgmt_capabilities to see the public surface, domains_check_availability to check a name, and domains_get_quote for the locked price: wholesale plus the itemized 1% platform cut, printed plainly. Example quote for a 1-year .com: $12.99 wholesale + $0.13 cut = $13.12 total.

Setup with an API key (tenant tools)

Prereqs: Node 18+.

git clone https://github.com/thingscorp/thatmgmt-mcp.git thatmgmt-mcp
cd thatmgmt-mcp
npm install
export TMGMT_API_KEY="your-thatmgmt-api-key"

The key is only needed for tenant tools: name suggestions, portfolio views, the dry-run planner, and prepare-registration. Everything else works without it.

Add to your MCP client config (Claude Code / Cursor):

{
  "mcpServers": {
    "thatmgmt": {
      "command": "node",
      "args": ["/path/to/thatmgmt-mcp/src/index.js"],
      "env": { "TMGMT_API_KEY": "your-thatmgmt-api-key" }
    }
  }
}

Verify:

npm test

Optional: TMGMT_BASE_URL overrides the API base (default https://api.thatmgmt.com). TMGMT_TIMEOUT_MS overrides the per-request timeout in milliseconds (default 30000). Transient failures (network errors, timeouts, 429s, retryable 5xx) are retried once on side-effect-free calls; the server never retries anything that could move money.

The two-step purchase flow

Spend-effect actions never execute blindly. The intended flow, written into every tool description so agents show the human the price first:

1. Quote. Call domains_get_quote. It returns the locked price: wholesaleCents, the itemized 1% cut (platformCutCents, platformCutBasisPoints), and totalCents. No key needed. Show this to the human.
2. Plan. Call domains_prepare_registration (needs TMGMT_API_KEY). It returns the safety-checked plan. It never executes anything.

Pricing: no subscription. A flat 1% cut applies to spend-effect actions only. Checkout options (crypto via Privy, or card/bank fallback) are arranged outside this server.

Important: what this server cannot do

The ThatMgmt API exposes no execute endpoints. Purchase, renewal, transfer, and DNS changes are never executed by the API; the API returns validated plans and preflights instead. This server therefore cannot register, renew, or transfer a domain, and it will never claim it did.

src/approval.js holds the approval gate that future execute tools will use: quote id passed back plus an explicit approved: true flag, or the call is refused. The gate is implemented and tested now so the safety design is ready the day execute routes exist.

Current release: 0.2.1 (read-only public tools plus validated plans). Execute tools are planned for the 0.3.0 release.

Tools

Public tools never send an Authorization header and never ask for a key. Tenant tools return 401 without a key; the server tells you to set TMGMT_API_KEY. The key is sent as a Bearer token and is never logged.

Agent skill

skills/thatmgmt/SKILL.md is the agent skill for this server: when to use it, the tool list, and the two-step purchase flow. Point your agent at it for the fastest start.

Development

npm test   # 47 tests, mocked HTTP, no live calls

Registry

server.json is the manifest for the official MCP registry (io.github.Thingscorp/thatmgmt-mcp). Releases are automated: pushing a version tag (e.g. v0.2.1) triggers the Publish to npm workflow (npm publish via the NPM_TOKEN secret) and the Publish to MCP Registry** workflow (validates server.json, publishes via GitHub OIDC).

Release flow: bump version in package.json (keep the mcpName field — io.github.Thingscorp/thatmgmt-mcp), push to main, then create the tag/release. The tag must match package.json; the registry validates the published npm metadata, so ship a new version for new fields.