Custom Domain API

io.github.siretov0.11.1更新於 Oct 10, 2026

Register a SaaS app's customer hostnames, show their DNS records and checks, recheck or delete them.

已驗證STDIO僅桌面Cloud & InfrastructureDeveloper Tools

概覽

AI 產生的概覽

讓助理透過 Custom Domain API 註冊、查看、重新檢查並刪除客戶的自訂主機名稱。

功能
包裝 Custom Domain API，讓助理能為某個工作區註冊客戶的主機名稱，並取回要交付的 DNS 記錄。它可以取得單一網域的狀態、記錄與四項檢查結果，依工作區或狀態分頁列出網域，並把 DNS 記錄整理成附逐條說明的文字。它也支援在修正 DNS 後重新檢查網域、刪除主機名稱，以及列出不含密鑰的 webhook 訂閱。
適用情境
適用於 SaaS 應用讓客戶把自己的主機名稱指向該服務的情境：讓助理完成主機名稱上線、向客戶說明 DNS 記錄，或排查網域為何尚未生效。它偏向客服與上線流程，而非一般 DNS 管理。
執行需求
以 stdio 在本機執行，透過 uvx 或 pip 安裝，因此需要 Python 與該套件。必須設定兩個環境變數：CUSTOM_DOMAIN_API_URL（https 邊緣位址）與 CUSTOM_DOMAIN_API_KEY（以 cd_ 開頭的應用程式 API 金鑰）。僅支援桌面版 MCP 用戶端，沒有網頁版。
安裝前請注意
伺服器持有應用程式 API 金鑰（CUSTOM_DOMAIN_API_KEY），因此具備該應用程式後端的能力，但不能執行營運方操作。delete_domain 會停止提供該主機名稱並將其刪除，被標示為破壞性操作；伺服器要求助理先複述主機名稱，且只在你明確要求刪除該網域時才呼叫。不提供 webhook 建立與輪換，因為回應中帶有簽章密鑰。主機名稱、工作區參照、中介資料與檢查訊息來自客戶與 DNS，應視為資料而非指令。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Custom Domain API，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

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, 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

bash
uvx custom-domain-mcp        # or: pip install custom-domain-mcp

It reads two settings from the environment:

SettingValue
CUSTOM_DOMAIN_API_URLyour edge, such as https://edge.example.net (https only; plain http just for localhost)
CUSTOM_DOMAIN_API_KEYan application API key (cd_…)

Claude Code:

bash
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):

json
{  "mcpServers": {    "custom-domain": {      "command": "uvx",      "args": ["custom-domain-mcp"],      "env": {        "CUSTOM_DOMAIN_API_URL": "https://edge.example.net",        "CUSTOM_DOMAIN_API_KEY": "cd_..."      }    }  }}

Tools

ToolDoes
create_domainRegister a customer's hostname for a workspace; returns its DNS records. Safe to retry.
get_domainA domain with its status, records and the four checks.
list_domainsDomains, filtered by workspace or status, paged.
dns_instructionsThe records as text for the customer, with help for each.
recheck_domainRun the checks again after a DNS fix (once a minute per domain).
delete_domainStop serving a hostname and delete it (marked destructive).
list_webhooksWebhook 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.

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. 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).

來源：mcp-server/README.md，提交 0434ba1

工具

0
工具後設資料尚未被收錄。

版本歷史

1
  1. v0.11.1最新Oct 10, 2026