Pntr MCP server

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

Common workflows

or GitHub Pages

• Connect a free subdomain to Vercel

and GitHub deliveries

• Inspect Stripe webhooks

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

Shortened. The full README is on GitHub.