pntr-cli
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_domainsA | List all available domains for subdomain registration |
| check_subdomainB | Check if a subdomain name is available for registration |
| list_subdomainsA | List all your registered subdomains with their DNS records |
| register_subdomainB | Register a new subdomain, optionally with an initial DNS record |
| update_subdomain | Set a DNS record on an existing subdomain (replaces an existing record of the same type) or update its description |
| toggle_email | Enable or disable the email inbox for a subdomain. When enabled, any address @subdomain receives mail (kept 48 hours, 90 days on premium). |
| toggle_subdomain | Enable or disable a subdomain. Disabling removes its DNS records so it stops resolving (config is kept); enabling re-creates them. Only enabled subdomains count toward your tier limit. |
| list_emails | List received emails for a subdomain (newest first) |
| read_email | Read a received email's full content, including the body |
| toggle_captureA | Enable or disable HTTP request capture for a subdomain. When enabled, the hostname terminates at pntr and every inbound HTTP request is logged (view with list_requests/read_request). Enabling requires the subdomain to have no A/AAAA/CNAME records. |
| list_requestsA | List captured HTTP requests for a subdomain, newest first (requires capture to be enabled) |
| read_request | Read a captured HTTP request's full detail, including headers and body |
| toggle_wildcard | Enable or disable wildcard DNS (*.name.pntr.dev) for a subdomain. Premium feature; enabling requires an existing A, AAAA, or CNAME record to mirror. |
| delete_dns_recordA | Delete a single DNS record from a subdomain. Identify it by record_id (shown in list_subdomains) or by record_type when the subdomain has exactly one record of that type. |
| delete_subdomain | Delete a subdomain and all of its DNS records |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct action and resource: domains, subdomain availability, registered subdomains, registration, capture toggling, captured requests, and DNS record deletion. There is no meaningful overlap between any two tools.
All tool names follow a consistent snake_case verb_noun pattern such as list_domains, register_subdomain, toggle_capture, and delete_dns_record. The naming is predictable and easy to infer.
Seven tools is well within the ideal range for a focused subdomain management and HTTP capture server. Each tool provides clear value and the set is not bloated or too thin.
The core workflow of listing domains, checking availability, registering subdomains, toggling capture, and viewing requests is covered. However, there are notable gaps: read_request is referenced but missing, and there is no way to add DNS records after registration or delete a subdomain entirely.