What it does
Free domains under makes.fyi or agentdomains.co for the sites and APIs AI agents build.
- Connects 电脑或云端
- Account or key Cloud: Works without a key · add Authorization if you have one (often raises limits) · Local: Needs AGENTDOMAINS_API_KEY
- Category 开发者工具
可搭配使用
教 AI 做这类工作的 Skill,可与本项一起使用
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
graphify
Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
为什么排在这里
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 7/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 8/8 | 上次检查时云端端点有响应 |
| 使用分 | 27/100 |
质量: 基础检查通过 4/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
安装
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 AgentDomains。按照 https://mcp.popnx.com/i/tashfeenahmed-agentdomains-mcp.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 4/5 项检查 · 你的提问会经过开发者的服务器(mcp.agentdomains.co) · ✓ 命令已检查 2026年11月14日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
打开 Claude 的 Connectors 页面
CustomizeConnectors
点击“Add” → “Custom” → “Web”,填写这 2 项
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Name · 名称AgentDomainsRemote MCP server URL · 地址https://mcp.agentdomains.co在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
在聊天中开启
+ConnectorsAgentDomains
试一试
用 AgentDomains 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 AgentDomains,或回答中出现 AgentDomains 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
在网页版 ChatGPT 打开添加 MCP 的页面
Plugins+Add custom MCP server
填写名称和地址
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Name · 名称AgentDomainsConnection · 地址https://mcp.agentdomains.co在聊天中选择 AgentDomains
开启新聊天,输入前先从插件列表中选择 AgentDomains
试一试
用 AgentDomains 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 AgentDomains,或回答中出现 AgentDomains 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
打开终端
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
粘贴这条命令并按 Enter
claude mcp add --transport http --scope user agentdomains https://mcp.agentdomains.co在 Claude Code 中输入 /mcp
应能看到 AgentDomains 在列表中并显示已连接
试一试
用 AgentDomains 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 AgentDomains,或回答中出现 AgentDomains 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
在 Cursor 中以 Agent 模式打开 AI 聊天
试一试
用 AgentDomains 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 AgentDomains,或回答中出现 AgentDomains 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
在 VS Code 中以 Agent 模式打开 AI 聊天
试一试
用 AgentDomains 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 AgentDomains,或回答中出现 AgentDomains 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://mcp.agentdomains.coJSON 设置在下方“开发者专用”中
开发者专用:终端命令和 JSON 设置
通过网页连接
Claude Code
claude mcp add --transport http --scope user agentdomains https://mcp.agentdomains.coCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"agentdomains": {
"url": "https://mcp.agentdomains.co"
}
}
}VS Code (mcp.json)
{
"servers": {
"agentdomains": {
"type": "http",
"url": "https://mcp.agentdomains.co"
}
}
}安装在电脑上
Claude Code
claude mcp add --scope user agentdomains --env AGENTDOMAINS_API_KEY=your-value -- npx -y agentdomains-mcpClaude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"agentdomains": {
"command": "npx",
"args": [
"-y",
"agentdomains-mcp"
],
"env": {
"AGENTDOMAINS_API_KEY": "your-value"
}
}
}
}Cursor (~/.cursor/mcp.json)
{
"mcpServers": {
"agentdomains": {
"command": "npx",
"args": [
"-y",
"agentdomains-mcp"
],
"env": {
"AGENTDOMAINS_API_KEY": "your-value"
}
}
}
}VS Code (mcp.json)
{
"servers": {
"agentdomains": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"agentdomains-mcp"
],
"env": {
"AGENTDOMAINS_API_KEY": "your-value"
}
}
}
}需要你填写的值
AGENTDOMAINS_API_KEY机密 必填 env您的 AgentDomains API 密钥(adom_…)。仅在管理账户的调用中需要;check_availability 无需该密钥即可使用查看英文原文
Your AgentDomains API key (adom_…). Only needed for calls that manage an account; check_availability works without one.- Bearer . 仅用于管理账户的工具;check_availability 无需此项即可使用。
查看英文原文
Bearer . Only needed for tools that manage an account; check_availability works without it.
说明为自动翻译,变量名保持原样;不确定时请查看原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
一览
哪些应用可以使用它
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它能做什么
工具名称和描述与服务器在 2026年11月18日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
check_availabilityCheck whether a subdomain label is free before claiming it. Requires no API key. Returns { label, domain, fqdn, available, reason } where reason is 'available', 'taken', or 'invalid' (with a 'detail' explaining why the label is not usable).
signupCreate a new AgentDomains account and get an API key. Requires no existing key. IMPORTANT: the returned api_key is shown ONCE and is never retrievable again: you must store it immediately (save it to ~/.agentdomains/config.json or set AGENTDOMAINS_API_KEY) or the account is lost.
whoamiShow the current account: id, state, attached email and whether it is verified, domains used, and which domains are available to claim under. When quotas are disabled the response omits 'quota' and says unlimited:true; 'max_subdomains' is the separate hard cap on how many names o
attach_emailAttach an email address to the account and send it a verification link. A human must click that link within 30 days or the provisional account and its domains are deleted. Use this right after signup.
claim_domainRegister a subdomain (label.makes.fyi or label.agentdomains.co) on this account, optionally creating its first DNS record in the same call. An email is required the first time an account registers a name: pass 'email' here or call attach_email first; the name is reaped if that em
list_domainsList every subdomain on this account, with each one's DNS records and whether it is forwarding, proxying, or delegated to external nameservers.
get_domainShow one subdomain in full: its fqdn, DNS records, forward or proxy configuration, and delegation state.
get_visitsVisitor stats for a name that has a forward or proxy (plain DNS records are not seen). Pro accounts get daily requests and page views plus top countries; free accounts get the period total and an 'upgrade' offer. 'days' is 1 to 90 (default 30).
delete_domainDESTRUCTIVE AND IRREVERSIBLE: permanently delete a subdomain and every DNS record, forward, and proxy attached to it. The hostname stops resolving immediately and the label is released for anyone else to claim. There is no undo and no recovery. Only call this when the user has ex
add_dns_recordAdd a DNS record to a subdomain you already own. Use type A or AAAA to point at an IP address, CNAME to point at another hostname, or TXT for verification strings. Adding a record does not replace existing ones; use delete_record to remove a single one. Refused with a 409 while t
delete_recordDESTRUCTIVE: permanently remove ONE DNS record from a subdomain, keeping the name and every other record. Use this to undo a single record — a wrong IP, a spent ACME challenge — instead of delete_domain, which takes the whole name. The record_id is the 'id' field shown by get_dom
add_acme_challengePublish a Let's Encrypt DNS-01 challenge: creates a TXT record at _acme-challenge. . with the token your ACME client printed. Use this to get a certificate without exposing port 80 (for example for a wildcard cert, or a host behind NAT). DNS propagates within seconds, then tell y
set_forwardForward (HTTP-redirect) a subdomain to another URL. Claims the label first if you do not own it yet, in which case an email may be required exactly as for claim_domain. Defaults to a 302 temporary redirect that preserves the request path and query. HTTPS at the edge is handled fo
remove_forwardStop forwarding a subdomain. The name itself stays registered on the account; only the redirect is removed.
set_proxyServe a backend at this subdomain through the AgentDomains edge, which terminates TLS with its own certificate — this is how you get working HTTPS on an origin that has no certificate of its own (a bare IP-less PaaS host, a tunnel, an internal box). Unlike a forward, the URL stay
remove_proxyStop reverse-proxying a subdomain, so the edge no longer serves the backend or terminates TLS for it. The name stays registered on the account.
delegate_nameserversDelegate the subdomain to your own nameservers, handing you full control of it and everything beneath it (your own records, MX, deeper sub-domains). AgentDomains stops answering for the name, so its existing records, forwards, and proxies no longer apply. Supply at least two name
delete_accountDESTRUCTIVE AND IRREVERSIBLE, AND THE LARGEST ONE HERE: delete the whole AgentDomains account and invalidate its API key, which cannot be recovered or reissued — every later tool call fails with a 401 until a new signup. Without force it REFUSES while the account still holds name
upgrade_to_proGet a Stripe checkout link for AgentDomains Pro: names kept after the 30-day free trial for as long as you pay, 100 names instead of 10, visitor stats, names never removed for being unused, and priority support, for $10/year (interval 'year', the better deal) or $1/month. Use thi
manage_billingGet a Stripe billing-portal link for a Pro account: update the card, see invoices, switch between monthly and yearly, or cancel. A human must open it. Cancelling keeps Pro to the end of the paid period and never deletes a name. Answers 409 if the account has never subscribed (use
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 tashfeenahmed 验证,该账户拥有此仓库
- ✓ 通过
仍在维护
代码最后更新于5天前
- ! 注意
有许可证
GitHub 无法识别许可证类型;请打开文件自行查看
- ✓ 通过
端点有响应
在 95 毫秒内响应(HTTP 200)
- – 不适用
使用 OAuth 登录
无需登录
- ✓ 通过
工具描述中没有隐藏指令
已读取 20 个工具描述,未发现针对 AI 的隐藏指令
云端地址最近 4 次检查中有 4 次响应 · 最近一次 95 ms · 检查于 2026年11月18日
已公开的漏洞(OSV.dev)
OSV.dev 中没有 agentdomains-mcp@0.1.4 的记录
只检查这个版本的包本身,不包括所有依赖 · 检查于 2026年11月15日
作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/tashfeenahmed-agentdomains-mcp)讨论
提问、分享技巧或报告无法使用。按“有帮助”数量排序。
用户评价
还没有评价
与“开发者工具”中的其他服务器比较i
- 星标数多于此分类中其他 6136 个服务器的 81%
- 发布到注册中心的时间比此分类中其他 6136 个服务器的 88% 更新
- 基础检查结果等于或优于此分类中其他 6136 个服务器的 50%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
AgentDomains 安全吗?
它在 5 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
你需要填写:AGENTDOMAINS_API_KEY
它在我的电脑上运行还是在云端?
两种方式都可以:安装在你的电脑上,或者连接云端版本。
它还在维护吗?
GitHub 仓库最后更新于5天前,最新版本(0.1.4)于5天前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
有什么可以替代它?
同一分类中有:GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
功能相近的其他选择
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| 本项 AgentDomains | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| 运行位置 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 |
| 需要密钥 | 是 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 是 | 否 | 否 |
| 基础检查 | 4/5 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| 许可证 | NOASSERTION | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
AgentDomains MCP server
MCP server for AgentDomains — free domains for the websites and APIs AI agents build. It gives any MCP-speaking agent a real hostname under makes.fyi or agentdomains.co, with DNS records, HTTPS, URL forwarding, and reverse proxying.
Two ways to run it: locally over stdio via npx, or against the hosted remote endpoint at https://mcp.agentdomains.co.
The buttons add the hosted server with no key. Ask your agent to call signup, then it passes the returned key as the api_key argument on later calls (or add an Authorization: Bearer header to the config).
Install (stdio)
No install step — npx fetches it on demand:
AGENTDOMAINS_API_KEY=adom_… npx -y agentdomains-mcp
Claude Code
claude mcp add agentdomains --env AGENTDOMAINS_API_KEY=adom_… -- npx -y agentdomains-mcp
Claude Desktop and other config-file clients
Add to claude_desktop_config.json (or your client's equivalent):
{
"mcpServers": { "agentdomains": { "command": "npx", "args": ["-y", "agentdomains-mcp"], "env": { "AGENTDOMAINS_API_KEY": "adom_…" } } } }
Remote endpoint
https://mcp.agentdomains.co
Streamable HTTP; send JSON-RPC over POST with your key in the Authorization header:
curl -s https://mcp.agentdomains.co \
-H 'Authorization: Bearer adom_…' \ -H 'Content-Type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
In Claude Code: claude mcp add --transport http agentdomains https://mcp.agentdomains.co --header "Authorization: Bearer adom_…"
No key yet? Connect without the header, call signup, and pass the returned key as the api_key argument on every other tool call. The header wins when both are present.
Configuration
| Variable | Purpose |
|---|---|
AGENTDOMAINS_API_KEY | Your API key (adom_…). Falls back to api_key in ~/.agentdomains/config.json. |
AGENTDOMAINS_API_URL | Override the API base URL. Defaults to https://api.agentdomains.co. |
If you already use the Go CLI, its ~/.agentdomains/config.json is picked up automatically and no env var is needed.
No key yet? Call the signup tool — it needs no credentials and returns one. The key is shown once and is never retrievable, so store it immediately. Accounts are provisional: attach an email with attach_email and confirm it within 30 days or the account and its domains are deleted.
The API key is never logged, printed, or included in any tool output.
Tools
| Tool | Endpoint | Description |
|---|---|---|
check_availability | GET /v1/available | Is a label free? No key required. |
signup | POST /v1/signup | Create an account, get an API key (shown once). No key required. |
whoami | GET /v1/whoami | Account state, email, quota, usage. |
attach_email | POST /v1/account/email | Attach an email and send its verification link. |
claim_domain | POST /v1/subdomains | Register label.domain, optionally with a first record. |
list_domains | GET /v1/subdomains | List every name on the account. |
get_domain | GET /v1/subdomains/{label} | One name, its records, forward/proxy state. |
delete_domain | DELETE /v1/subdomains/{label} | Destructive — permanently delete a name and its records. |
add_dns_record | POST /v1/subdomains/{label}/records | Add an A, AAAA, CNAME, or TXT record. |
delete_record | DELETE /v1/subdomains/{label}/records/{id} | Destructive — remove one record, keeping the name. Ids come from get_domain. |
add_acme_challenge | POST /v1/subdomains/{label}/records | TXT at _acme-challenge for Let's Encrypt DNS-01. |
set_forward | PUT /v1/subdomains/{label}/forward | Redirect the name to a URL; replaces the address records on it. |
remove_forward | DELETE /v1/subdomains/{label}/forward | Stop forwarding. |
set_proxy | PUT /v1/subdomains/{label}/proxy | Serve a backend through the edge, with TLS terminated for you; replaces the address records on it. |
remove_proxy | DELETE /v1/subdomains/{label}/proxy | Stop proxying. |
delegate_nameservers | PUT /v1/subdomains/{label}/ns | Delegate the name to your own nameservers. |
delete_account | DELETE /v1/account[?force=true] | Destructive — close the account and kill its key; refuses while names are held unless force. |
upgrade_to_pro | POST /v1/billing/checkout | A Stripe checkout link for Pro (100 names, $5/month or $48/year). Charges nothing; a human opens the link and pays. |
manage_billing | POST /v1/billing/portal | A Stripe billing-portal link for a Pro account (card, invoices, interval, cancel). |
Every label-scoped tool takes an optional domain (makes.fyi, the default, or agentdomains.co).
Setting a forward or a proxy takes the hostname over. The A/AAAA/CNAME records on the label itself are deleted in the same call and handed back as replaced_records, so tell the user what moved. Sub-label records (www.myapp.makes.fyi) and TXT records are left alone, and if the forward fails to come up the replaced records are restored with new ids.
A claim and its first record stand or fall together. If claim_domain is given a record it cannot create, nothing is claimed — fix the record and call again. Re-claiming a name the account already holds answers 409 with owned:true, which means carry on.
On HTTPS
"Get me SSL" is not one operation here. Two honest paths:
- `set_proxy` — the edge terminates TLS with its own certificate and proxies to your backend. Nothing to install on the origin.
- `add_acme_challenge` — publishes the DNS-01 TXT record so your own ACME client can issue a Let's Encrypt certificate (needed for wildcards or hosts with no public port 80). A plain public web server can just use HTTP-01 and needs no DNS record at all.
Compatibility
Any MCP client works. Verified shapes for the common ones:
- Claude Code —
claude mcp add(stdio or--transport http), as above. - Claude Desktop —
mcpServersblock inclaude_desktop_config.json. - OpenAI Agents SDK —
MCPServerStdio(params={"command": "npx", "args": ["-y", "agentdomains-mcp"]}), orMCPServerStreamableHttpagainst the remote URL. - LangChain / LangGraph —
langchain-mcp-adapters:MultiServerMCPClient({"agentdomains": {"command": "npx", "args": ["-y", "agentdomains-mcp"], "transport": "stdio"}}). - CrewAI —
MCPServerAdapterwith the same stdio parameters. - Anything else — point your client at
npx -y agentdomains-mcpover stdio, or athttps://mcp.agentdomains.coover Streamable HTTP.
Development
npm install
npm run build # tsc -> dist/ npm run smoke # boots dist/index.js, runs initialize + tools/list over stdio
Requires Node 18+. The only runtime dependency is @modelcontextprotocol/sdk.
Related
- CLI (Go) — the
agentdomainscommand - Agent skill — Claude Code plugin
- Docs · HTTP API
License
FSL-1.1-Apache-2.0 — see LICENSE. Same terms as the CLI.
MCP Registry listing
This server is listed in the official MCP Registry as io.github.tashfeenahmed/agentdomains-mcp — the index PulseMCP, Glama and other agent-tool directories read from. The metadata is server.json in this repo.
Publishing is manual (GitHub Actions is not running on this account). On each npm release, bump version in server.json and its packages[0].version to match package.json, publish to npm first, then:
# once: install the publisher (macOS/Linux)
curl -L "https://github.com/modelcontextprotocol/registry/releases/latest/download/mcp-publisher_$(uname -s | tr '[:upper:]' '[:lower:]')_$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz" | tar xz mcp-publisher
./mcp-publisher login github # device-code flow as the tashfeenahmed GitHub account ./mcp-publisher publish # uploads server.json curl -s "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.tashfeenahmed/agentdomains-mcp"
The registry checks that the npm package's mcpName matches name in server.json, so the npm version named in server.json must already be published.
docs/publish-mcp-registry.yml is an optional GitHub Actions workflow that does the same on a v* tag via GitHub OIDC. It only runs if moved to .github/workflows/ and Actions is available on the account.