All guides

MCP guide

Connect Cursor to PNTR's MCP DNS server

Cursor supports remote MCP servers and OAuth. Adding PNTR's hosted endpoint makes its subdomain, DNS, email, and request-capture tools available to Cursor without running a local server.

Explore PNTR's mcp dns server

.cursor/mcp.json

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

Setup

  1. 1

    Choose project or global scope

    Use .cursor/mcp.json inside one repository for project-only access, or ~/.cursor/mcp.json when you want PNTR tools available in every Cursor project.

  2. 2

    Add the hosted PNTR server

    Merge the JSON below into the file's existing mcpServers object. Preserve any other configured servers instead of replacing the whole file.

  3. 3

    Reload Cursor and authenticate

    Open Cursor's MCP settings or Agent tools and connect PNTR. Cursor should open the browser-based GitHub authorization flow for the remote server.

  4. 4

    Verify with a read-only request

    Ask Cursor to list your PNTR subdomains and DNS records. Confirm the returned account and hostname before asking it to make a change.

  5. 5

    Review writes before approval

    For record updates, capture changes, or deletion, read the exact target and action Cursor proposes. Deleting a subdomain and disabling capture can remove stored data.

Before you ship

The URL-only configuration uses OAuth and avoids putting a long-lived API token in mcp.json. If the browser flow is unavailable in your Cursor version, PNTR's dashboard provides a manual token configuration under MCP setup.

Primary documentation