Manage web3 domains with AI, one request at a time.
Freename's MCP server plugs an AI assistant into domain management. Type what you want, and the assistant can search, buy and renew ICANN and Web3 domains, deploy websites, and edit DNS and Web3 records. A TLD now moves at the pace of a chat.
One request. Three changes on .yourbrand.
IllustrationYour treasury team asks a connected assistant for a payment name, a wallet record and a holding page.
Create pay.yourbrand, point it to our treasury wallet 0x4e1b…a9c3 and publish a short holding page on it. Check with me before anything is bought or goes live.
Understood. Three steps, and I will stop for your go-ahead before the purchase and before the page is deployed. First, a search.
pay.yourbrandUnder .yourbrandAvailablepay.yourbrand is available. Shall I register it now?
Yes, go ahead.
pay.yourbrandConfirmed by youDone0x4e1b…a9c3UpdatedThe name now points to the treasury wallet. Here is the holding page draft. Deploy it?
Deploy.
pay.yourbrandDeployedAll three steps are complete. Test a small transfer to pay.yourbrand from a wallet that supports Freename names before you share it with customers.
- Every step above is available to whoever holds a TLD.
- The confirmations happened because the person asked for them.
- Nothing in the flow checks who the name sounds like.
Illustration. .yourbrand stands for your own TLD, the address is a placeholder, and real assistants word things differently.
The Freename MCP in four moves
Add the server
An account holder links the Freename MCP server to Claude, Codex, Cursor or Kimi.
State the outcome
Register, renew, repoint, publish. The assistant maps plain words to the matching action.
Gate the costly steps
Purchases, record edits and deployments wait for an explicit yes, and only a short named list may give it.
Verify outside the chat
Look up the record, open the site, send a small test payment.
What it changes, depending on your seat
For brands and legal teams
Exposure
Whoever holds the TLD matching your trademark can run the transcript above today, with their own wallet in it, and no conventional ICANN-based watch will flag it. Start by learning whether the TLD exists through a free Trademark Name Check, then consider quiet recovery or Namespace watch. Counsel keeps the legal questions.
For holders
Value
A TLD that a buyer's teams could run from assistants they already use is easy to picture in production, which shortens the case for buying it. Begin with a private valuation; every mandate is quoted privately.
For operators
Build
Issue and maintain member names without building an admin panel first. More names in use means more fee share for the holder, which Freename currently caps at half of each registration. Model it with the Subname Revenue Calculator or see how we work with operators.
Limits. The server acts only on request. It does not watch your names, set permissions inside your company, put names into the ICANN DNS, or guarantee the assistant understood you. Anything beyond Freename's listed tasks, confirm with Freename first.
Set access rules with usProof
- Freename MCP: compatible assistants and the tasks it covers.
- Name your wallet: linking an address to a name.
- Freename help center: registration fee share and no TLD renewal fees.
Questions about the Freename MCP
What is MCP, and what does Freename's server do?
MCP, the Model Context Protocol, is a common way to connect an AI assistant to an outside service so it can take actions there. Freename's server exposes domain search, purchase and renewal, website deployment, and DNS and Web3 record management.
Which AI assistants work with it?
Freename lists Claude, Codex, Cursor and Kimi. Check the current list before choosing one for your team.
Does a TLD need renewing if we run it from an assistant?
No. Freename charges no renewal fees for TLDs. The renewal action applies to domains that carry one, such as ICANN domains.
Should our whole team have access?
Rarely. Searching and drafting can be broad. Purchases, record edits and deployments belong with a few named people, a confirmation rule and a saved conversation for each change.