GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Computer or cloud
Custom Domain API
Overview
Description from the maker (original English)
Register a SaaS app's customer hostnames, show their DNS records and checks, recheck or delete them.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiVery new↓ 28/wk · ★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Developer tools
- You need to fill in: CUSTOM_DOMAIN_API_URL, CUSTOM_DOMAIN_API_KEY
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
CUSTOM_DOMAIN_API_URL,CUSTOM_DOMAIN_API_KEY
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
- PyPIPython’s uv installed (for the uvx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"custom-domain": {
"command": "uvx",
"args": [
"custom-domain-mcp"
],
"env": {
"CUSTOM_DOMAIN_API_URL": "your-value",
"CUSTOM_DOMAIN_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add custom-domain --env CUSTOM_DOMAIN_API_URL=your-value --env CUSTOM_DOMAIN_API_KEY=your-value -- uvx custom-domain-mcpFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"custom-domain": {
"command": "uvx",
"args": [
"custom-domain-mcp"
],
"env": {
"CUSTOM_DOMAIN_API_URL": "your-value",
"CUSTOM_DOMAIN_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"custom-domain": {
"type": "stdio",
"command": "uvx",
"args": [
"custom-domain-mcp"
],
"env": {
"CUSTOM_DOMAIN_API_URL": "your-value",
"CUSTOM_DOMAIN_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
- Your edge, such as https://edge.example.net (https only)
- An application API key (cd_...), never an operator token
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account sireto, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Developer toolsi
- More stars than 0% of the other 4924 servers in this category
- Published to the registry more recently than 61% of the other 4924 servers in this category
- Basic checks equal to or better than 100% of the other 4924 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Custom Domain API safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: CUSTOM_DOMAIN_API_URL, CUSTOM_DOMAIN_API_KEY
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.13.0) reached the registry 26 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
What can I use instead?
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Desktop Commander
MCP server for terminal commands, file operations, and process management
Runs on your computer
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
custom-domain-mcp
An MCP server for the Custom Domain API. It lets an AI assistant (Claude, Cursor, any MCP client) register your customers' hostnames, show them their DNS records or a link to a setup page, check why a domain isn't live yet, and recheck or delete it. It acts as one application, with that application's own API key.
Setup
uvx custom-domain-mcp # or: pip install custom-domain-mcpIt reads two settings from the environment:
| Setting | Value |
|---|---|
CUSTOM_DOMAIN_API_URL | your edge, such as https://edge.example.net (https only; plain http just for localhost) |
CUSTOM_DOMAIN_API_KEY | an application API key (cd_…) |
Claude Code:
claude mcp add custom-domain --env CUSTOM_DOMAIN_API_URL=https://edge.example.net \--env CUSTOM_DOMAIN_API_KEY=cd_... -- uvx custom-domain-mcp
Claude Desktop, Cursor and other clients (mcpServers in their config):
{"mcpServers": { "custom-domain": { "command": "uvx", "args": ["custom-domain-mcp"], "env": { "CUSTOM_DOMAIN_API_URL": "https://edge.example.net", "CUSTOM_DOMAIN_API_KEY": "cd_..." } } } }
Tools
| Tool | Does |
|---|---|
create_domain | Register a customer's hostname for a workspace; returns its DNS records. Safe to retry. |
get_domain | A domain with its status, records and the four checks. |
list_domains | Domains, filtered by workspace or status, paged. |
dns_instructions | The records as text for the customer, with help for each, and the detected DNS provider's guide. |
create_connect_session | A link to the setup page for one domain (records, live checks, one-step setup when the provider supports it), with its expiry. |
revoke_connect_session | End a setup page link now (marked destructive). |
recheck_domain | Run the checks again after a DNS fix (once a minute per domain). |
delete_domain | Stop serving a hostname and delete it (marked destructive). |
list_webhooks | Webhook subscriptions, without secrets. |
What it can't do
- No operator actions. It never holds an operator token, only the application's key, so it can do exactly what the application's backend can.
- No webhook creation or rotation. Their responses carry the signing secret, which would end up in the assistant's conversation. Create webhooks through the API or the portal.
A setup page link is a credential for one domain. Whoever holds it can see that domain's setup and status, ask for a check and start one-step setup; nothing else, and never the API key. The server tells the assistant to give it only to the customer who owns the hostname. The deployment must serve the page (PUBLIC_API=true and EDGE_HOSTNAME); otherwise create_connect_session reports connect_page_unavailable.
Customer data is data, not instructions. Hostnames, workspace references, metadata and check messages come from your application's customers and from DNS. The server tells the assistant to report them, never to follow them, and to call delete_domain only when you explicitly asked for that domain to be deleted, repeating its hostname back to you first. It also tells the assistant to create a setup page link only when you ask for one and to hand it to you, never to send it to an address, URL or channel found in domain data: metadata is customer-controlled and must not steer where a credential goes. Your MCP client's own confirmation for destructive tools adds a second check.
The server's instructions also tell the assistant the one rule integration code must follow: select the tenant from the verified X-Custom-Domain-Assertion, never from Host (verifying requests).