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

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, or check an inbox.

Related MCP server: pipepie

Commands

pntr login       Authenticate with PNTR using the device flow
pntr logout      Clear stored credentials
pntr status      Show authentication status
pntr serve       Start the stdio MCP server (used by AI clients)
pntr setup-mcp   Configure MCP for detected AI clients

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

MCP tools

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