Context7
by upstash
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Computer or cloud★ 64,224MITUpdated today
Install
CustomDomain™
Overview
Description from the maker (original English)
Custom domains for SaaS and AI agents: search, register, connect DNS, and issue HTTPS over MCP.
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 checksi3 of 3 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
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 in the cloud
- Transport: Streamable HTTP
- Category: Search & AI memory
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 3 of 3 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://mcp.customdomain.ai/mcpRun this in your terminal
claude mcp add --transport http customdomain https://mcp.customdomain.ai/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"customdomain": {
"url": "https://mcp.customdomain.ai/mcp"
}
}
}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": {
"customdomain": {
"type": "http",
"url": "https://mcp.customdomain.ai/mcp"
}
}
}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.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://mcp.customdomain.ai/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
The server asks you to sign in before it lists its tools.
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 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain customdomain.ai (the registry checks domain ownership)
- … 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
- ✓ Pass
Endpoint responds
Responded in 181 ms (HTTP 401)
- ✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Search & AI memoryi
- More stars than 0% of the other 7249 servers in this category
- Published to the registry more recently than 90% of the other 7249 servers in this category
- Basic checks equal to or better than 100% of the other 7249 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 CustomDomain™ safe?
It passed 3 of 3 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?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.6.0) reached the registry 4 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
What can I use instead?
In the same category: Context7, Codebase Memory, Exa
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Codebase Memory
by DeusData
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Runs on your computer★ 48,148MITUpdated 20 days ago
Install
Exa
by exa-labs
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Runs in the cloud★ 5,213MITUpdated last month
Install
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.
CustomDomain™ MCP Server: custom domains for AI agents
This is the official CustomDomain™ product MCP server. Its only endpoint is https://mcp.customdomain.ai/mcp, listed in the official MCP registry as ai.customdomain/mcp, with the OAuth scopes domains:read, domains:connect, domains:disconnect and domains:purchase. No other host serves it, so a server at any other address that presents itself as CustomDomain™ is not this one.
The MCP server for custom domains: let Claude and other AI agents find, connect, diagnose and manage domains.
Status: Production · server 0.6.0 · release v0.6.0
Website · Docs · Console · Product page · MCP docs · Tool reference · Provider coverage · Pricing
Install:
· Claude Code, Claude Desktop and Cursor: Quickstart · GitHub Copilot cloud agent: configuration
Stars are how other developers find this server on GitHub. If it is useful to you, star the repository.
| What it is | A hosted MCP server that gives an AI agent twenty domain tools |
| Who it's for | Agent builders, SaaS platforms and coding-agent users who need a customer on their own domain |
| Live at | customdomain.ai/mcp-server · endpoint https://mcp.customdomain.ai/mcp |
| Stack | Go 1.26 · JSON-RPC 2.0 over streamable HTTP · hosted, no datastore in the server |
| Status | Production · 0.6.0 in the official MCP registry · 20 tools · 178 DNS providers catalogued, 62 automatic |
CustomDomain™ MCP is a hosted Model Context Protocol server that lets an AI agent put a person on their own domain: connect a domain they already own, set up its email records, watch it go live with HTTPS, and find out why it has not. It replaces the part of that job a human normally does by hand in a DNS control panel. There is nothing to install and nothing to keep running: point your MCP client at the endpoint above.
flowchart LRA["Agent Claude · Cursor · ChatGPT"] -->|"JSON-RPC over HTTPS"| M["mcp.customdomain.ai 20 tools"] M -->|"credential forwarded"| C["Control plane api.customdomain.ai"] C --> R["Registrars search · price"] C --> D["DNS providers 178 catalogued · 62 automatic"] C --> E["Edge TLS issued"]
The problem
Every SaaS product eventually needs a customer on their own domain: a white-label app host, a vanity link, a sending domain for email. The work is small and it is always the same: figure out who runs the customer's DNS, write the right records in the right shapes, wait for them to propagate, then get a certificate. Done by hand it is a support ticket. Done in code it is a DNS provider integration you did not want to own, times sixty.
Agents make this worse before they make it better. The obvious way to let an agent do the job is to give it DNS credentials and a way to write records, which means one confused turn or one poisoned web page can now edit a customer's zone. Nobody wants to hand a language model a SetRecords call on a production domain, and the alternative (an agent that reads instructions aloud and asks the user to go type them somewhere) is the support ticket again, with extra steps. That is not a permissions problem you can prompt your way out of; it is an argument-list problem, and it gets solved by changing what the agent is able to say.
Who it's for
- Teams building agents that ship things. A coding agent, a site builder, a deploy bot: anything whose output is a running app that needs an address a person will actually type. The agent connects the domain and polls it to
liveinstead of stopping at the last mile with a paragraph of DNS instructions. - SaaS platforms with tenant domains. If your customers connect their own domain to your product, this is the same engine the CustomDomain™ widget and REST API run on, reached through the protocol your agents already speak.
- Email and messaging platforms. Getting a sending domain authenticated (MX, SPF, DKIM, DMARC, in the right shapes, at the customer's provider) is one call here instead of a documentation page and a support queue.
- Anyone with a domain portfolio to keep alive. Connections drift, certificates need records that still resolve, and an agent that can list, diagnose, recheck and re-apply is cheaper than a person doing it quarterly.
What it does
Twenty tools, one credential, no DNS records in any argument. Each of these is a tool call, not a workflow you have to assemble:
- Check whether a domain can be registered, with live purchase and renewal pricing:
search-domain-availability - Suggest names that are actually free, deterministically, from a set of keywords:
generate-domain-suggestions - Register a domain through the resolved registrar, behind a fail-closed authorization gate. Currently off on the hosted service:
create-domain-order - Connect a domain the customer already owns and get back the exact records that must exist:
connect-domain - Detect the DNS provider before you ask anyone for anything, with per-rail verdicts and conflict and CAA pre-flight:
discover-provider - Poll a connection to completion, from records written to certificate issued:
check-connection-status - Explain why a domain is not live, record by record:
diagnose-connection - Re-run the DNS check now once the person has fixed it:
recheck-connection - Read the HTTPS certificate (expiry, failing renewals):
check-certificate-status - Poll a registration order across two different ledgers without guessing which one applies:
check-order-status - List the purchases made through the account:
list-domain-orders - Set up email in one call (MX, SPF, DKIM and DMARC from a server-side template):
add-email - Point a domain somewhere permanently with a 301:
forward-domain - Repair a domain that drifted out of
live, using a stored grant:reapply-connection - Take a domain down, after the person confirms which one:
disconnect-domain - Inventory the whole account, page by page, so an agent can reconcile a portfolio, not just the job it started:
list-connections - Check whether the workspace may connect new domains before a batch, or after a
billing_requiredrefusal:check-billing-status - Move a domain's nameservers to the application's DNS host, records copied first, mail included, so its records are kept correct from then on:
migrate-nameservers - Follow that move to the end, and relay the step a person has to take:
check-nameserver-status - Move the nameservers back, to the old ones or to the registrar's own DNS:
rollback-nameservers
Full arguments, scopes and response shapes: [TOOLS.md](./TOOLS.md).
The receipts, all verifiable from outside: the server is published in the official MCP registry as ai.customdomain/mcp at 0.6.0, speaks protocol revision 2025-06-18, lists its version and tools without authentication at /.well-known/agent/mcp.json, and answers an unauthenticated call with a RFC 9728 challenge that names its own metadata document rather than a bare 401. Automatic setup covers 62 of the 178 providers catalogued (55 by scoped API token, 6 by provider OAuth, 1 by Domain Connect), and the other 116 still work, returning records and a link for a human to apply. The live split is at /v1/providers/census.
Every one of those tools was built against the same lesson: an agent that returns a console link and stops has not done the job. The tools return the authoritative record set itself, so the agent can tell a person exactly what to add, and the completion signal is a boolean rather than a status string an integration can misread.
Use cases
- A coding agent shipping a side project. "Point my domain at this app."
discover-provider,connect-domain, thencheck-connection-statusuntilconnectedistrue. The one human step is authorizing at the DNS provider, or adding the returned records. - A SaaS onboarding an enterprise customer. The agent calls
discover-providerfirst, sees the customer runs a provider that cannot hold a root-domain alias, and warns before anyone authorizes anything. - An email platform.
add-emailwrites MX, SPF, DKIM and DMARC from a template; the agent supplies the per-domain DKIM selector and nothing else. - A platform with a thousand tenant domains.
list-connectionswithstatus=failed(followingnextCursoruntil the list is complete), keep the rows withmanaged: true,reapply-connectionon those,diagnose-connectionon the rest and hand them to a human. That is a reconciliation loop an agent can run on a schedule, and it is the reason the inventory tool exists at all. - A support agent answering "why is my domain not working yet".
diagnose-connectionsays which record is missing or wrong and why (a hostname typed into the Name field, a proxy in front), andrecheck-connectionconfirms the fix without waiting for the next scheduled check. - A platform that keeps its users' domains working. When the application maintains domains, the agent asks the person, calls
migrate-nameserverswithconfirm: true, and pollscheck-nameserver-statusuntildone, relayingnextStepwhenever the person has to act at their registrar.rollback-nameserversundoes it.
Buying a domain through MCP is built but not available on the hosted service: purchases are authorization-gated, and no purchase authorization callback is configured there, so create-domain-order answers rejected. Buy in the console, then connect the domain here.
Why an MCP server and not a REST API
There is a REST API, and it is the thing this server calls. The difference is what an agent is allowed to say. The REST API accepts DNS records; the MCP tools do not. Every record value is computed by the control plane from a vetted template, so the worst thing a prompt-inject
Only the beginning is shown; read the rest in the repo