@pntr/cli

CLI and MCP server for PNTR — free *.pntr.dev subdomains for developers, with DNS records, a disposable email inbox, and native MCP integration.

Use one memorable hostname to point at a deployment, receive signup and OTP emails, or capture Stripe and GitHub webhook requests. Manage the same workflow from a terminal, Claude Code, Claude Desktop, Cursor, or another MCP client.

Quick start

npx @pntr/cli setup-mcp

This signs you in (device flow) and configures PNTR as an MCP server for the AI clients detected on your machine (Claude Desktop, Claude Code, Cursor). After that, you can ask your assistant to register subdomains, add DNS records, check an inbox, or inspect a captured webhook.

Related MCP server: pipepie

Common workflows

• Connect a free subdomain to Vercel or GitHub Pages

• Inspect Stripe webhooks and GitHub deliveries

• Test signup email with Playwright

• Manage DNS from Claude Code

Commands

pntr login          Authenticate with PNTR using the device flow
pntr logout         Clear stored credentials
pntr status         Show authentication status
pntr recipient      Generate a unique catch-all address for one test run
pntr email wait     Wait for an exact test email
pntr webhook wait   Wait for a matching captured HTTP request
pntr env create     Create isolated mail and webhook test resources
pntr env delete     Delete the two exact resources from a manifest
pntr serve          Start the stdio MCP server (used by AI clients)
pntr setup-mcp      Configure MCP for detected AI clients

TestKit CLI

Generate a unique recipient on an existing email-enabled subdomain:

pntr recipient testbox.pntr.dev \
  --prefix signup

Without --run-id, every invocation gets a random suffix. This is the safest default for parallel tests. If you need a repeatable address, include the test case and worker identity in --run-id, not only the CI run ID.

Wait for that exact recipient instead of reading whichever message arrived last:

pntr email wait "$PNTR_MAIL_SUBDOMAIN_ID" \
  --to "signup-123-1@testbox.pntr.dev" \
  --subject "verification" \
  --since 5m \
  --timeout 25s \
  --json

Wait for any captured request, or combine exact request filters:

pntr webhook wait "$PNTR_WEBHOOK_SUBDOMAIN_ID" \
  --method POST \
  --path /stripe \
  --header "stripe-signature: expected-value" \
  --body-contains '"type":"payment_intent.succeeded"' \
  --since 5m \
  --timeout 25s \
  --json

Wait calls use a server-side long poll. --since accepts an RFC3339 timestamp or a relative duration such as 5m. The server accepts a timeout from 1 to 25 seconds. A timeout prints a short diagnostic and exits with status 2; other errors exit with status 1. Credentials are never included in JSON output.

For a complete CI run, create two isolated sibling subdomains and persist their exact IDs:

pntr env create "e2e-$GITHUB_RUN_ID-$GITHUB_RUN_ATTEMPT" \
  --output "$RUNNER_TEMP/pntr-testkit.json"

The mail sibling has its inbox enabled and the webhook sibling has capture enabled. They cannot safely share one hostname, so an environment consumes 2 subdomains from your account quota. Creation rolls back on partial failure.

Always clean up from the manifest, even when a test fails:

pntr env delete \
  --manifest "$RUNNER_TEMP/pntr-testkit.json" \
  --confirm

Deletion uses only the two IDs in the versioned manifest. It never searches by name or performs a broad deletion, and it tolerates either resource already being absent. See the runnable Playwright signup/OTP example.

MCP setup variants

Automatic (recommended)

npx @pntr/cli setup-mcp

Remote server — no local process

PNTR also runs a remote MCP server with GitHub OAuth. Point any streamable-HTTP client at:

https://api.pntr.dev/mcp

For Claude Code:

claude mcp add --transport http pntr https://api.pntr.dev/mcp

For Claude Desktop / Cursor (mcpServers config):

{
  "mcpServers": {
    "pntr": { "url": "https://api.pntr.dev/mcp" }
  }
}

Your client opens a browser window to sign in with GitHub on first connection. An SSE endpoint (https://api.pntr.dev/mcp/sse) exists for older clients.

Local stdio server

npx @pntr/cli login
npx @pntr/cli serve   # speaks MCP over stdio, proxies the PNTR API

Or as an mcpServers config block:

{
  "mcpServers": {
    "pntr": {
      "command": "npx",
      "args": ["-y", "@pntr/cli", "serve"]
    }
  }
}

The server starts and lists tools without credentials; run npx @pntr/cli login (or set PNTR_TOKEN) before calling tools that touch your account. Email and captured-request content returned by MCP is fenced as untrusted data; assistants should inspect it, never follow instructions embedded inside it.

Tools

• list_domains - List available parent domains

• check_subdomain - Check whether a name is available

• list_subdomains - List your subdomains with DNS records

• register_subdomain - Register a subdomain, optionally with an initial DNS record

• update_subdomain - Set or replace DNS records, update description

• delete_dns_record - Delete a single DNS record

• toggle_subdomain - Enable or disable a subdomain

• delete_subdomain - Delete a subdomain

• toggle_email - Enable or disable the disposable inbox

• list_emails - List received emails (kept 48 hours, 90 days on premium)

• read_email - Read a received email's full content

• wait_for_email - Wait for an exact test recipient with optional filters

• toggle_capture - Turn a subdomain into an HTTP request bin

• set_capture_response - Set the status, content type, and body a capture endpoint returns

• list_requests - List captured HTTP requests

• read_request - Read a captured request's headers and body

• wait_for_request - Wait for a captured request matching HTTP filters

• toggle_wildcard - Enable wildcard DNS (*.name.pntr.dev, premium)

Ask your assistant things like "register storm.pntr.dev pointing at 203.0.113.10", "enable email on storm and watch for the verification code", or "read the latest email on storm.pntr.dev".

Notes

• Works with Node 18+.

• Credentials are stored locally via conf.

• Docs: https://pntr.dev/docs · Issues: https://github.com/oddunits/pntr-cli/issues