Free developer subdomains with DNS, catch-all email, and webhook capture, managed via MCP.
Most team communication work still happens through a UI a human drives. Pntr MCP server moves it into the conversation instead. Free developer subdomains with DNS, catch-all email, and webhook capture, managed via MCP.
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.
The server publishes 14 tools. What each one is for:
list_domains — List available parent domainscheck_subdomain — Check whether a name is availablelist_subdomains — List your subdomains with DNS recordsregister_subdomain — Register a subdomain, optionally with an initial DNS recordupdate_subdomain — Set or replace DNS records, update descriptiondelete_dns_record — Delete a single DNS recordtoggle_subdomain — Enable or disable a subdomaindelete_subdomain — Delete a subdomaintoggle_email — Enable or disable the disposable inboxlist_emails — List received emails (kept 48 hours, 90 days on premium)read_email — Read a received email's full contentwait_for_email — Wait for an exact test recipient with optional filtersThe server ships on npm as @pntr/cli, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Configuration is passed through the environment: PNTR_MAIL_SUBDOMAIN_ID, PNTR_WEBHOOK_SUBDOMAIN_ID, GITHUB_RUN_ID, PNTR_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
This sits in the team communication group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Pntr's toolset — list_domains, check_subdomain, list_subdomains and 11 more — is a fair guide to whether it matches your workflow. It is maintained by dev.pntr; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| 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 |
{
"mcpServers": {
"pntr": { "url": "https://api.pntr.dev/mcp" }
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PNTR_MAIL_SUBDOMAIN_ID | Configuration value read at startup. | Optional |
| PNTR_WEBHOOK_SUBDOMAIN_ID | Configuration value read at startup. | Optional |
| GITHUB_RUN_ID | Configuration value read at startup. | Optional |
| PNTR_TOKEN | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.