Servidor MCP
AgentDomains
io.github.tashfeenahmed/agentdomains-mcp
Qué hace este MCP
Registers and manages subdomains, DNS records, redirects, reverse proxies, delegation and related account billing.
Capacidades
Herramientas
19
herramientas
add_acme_challenge
Publish a Let's Encrypt DNS-01 challenge: creates a TXT record at _acme-challenge.<label>.<domain> 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 your ACME client to continue. For a normal public web server, HTTP-01 validation needs no DNS record at all.
Esquema de entrada
{'type': 'object', 'required': ['label', 'value'], 'properties': {'label': {'type': 'string', 'description': "The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi)."}, 'value': {'type': 'string', 'description': 'The challenge token from your ACME client, published verbatim as the TXT value.'}, 'domain': {'type': 'string', 'description': "Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default."}}}
add_dns_record
Add 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 the label carries a forward or a proxy (they own the hostname) — call remove_forward or remove_proxy first, or add the record on a sub-label via 'host', which is a different hostname and unaffected.
Esquema de entrada
{'type': 'object', 'required': ['label', 'type', 'content'], 'properties': {'host': {'type': 'string', 'description': "Optional extra sub-label under the name (e.g. 'www' creates www.myapp.makes.fyi). Omit for the name itself."}, 'type': {'type': 'string', 'description': 'Record type: A, AAAA, CNAME, or TXT.'}, 'label': {'type': 'string', 'description': "The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi)."}, 'domain': {'type': 'string', 'description': "Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default."}, 'content': {'type': 'string', 'description': 'Record value: an IP for A/AAAA, a hostname for CNAME, the string for TXT.'}}}
attach_email
Attach 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.
Esquema de entrada
{'type': 'object', 'required': ['email'], 'properties': {'email': {'type': 'string', 'description': 'The email address to attach and send the verification link to.'}}}
check_availability
Check 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).
Esquema de entrada
{'type': 'object', 'required': ['label'], 'properties': {'label': {'type': 'string', 'description': "The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi)."}, 'domain': {'type': 'string', 'description': "Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default."}}}
claim_domain
Register 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 email is not confirmed within 30 days. Returns the fqdn and, when a record was requested, the created record. The claim and its first record succeed or fail together: if the record is malformed (400) or the provider refuses it (503) the label is NOT claimed, so fix the record and call again. Re-claiming a name this account already holds answers 409 with owned:true — that means carry on using it, not pick another label.
Esquema de entrada
{'type': 'object', 'required': ['label'], 'properties': {'host': {'type': 'string', 'description': "Optional extra sub-label for the record (e.g. 'www' gives www.myapp.makes.fyi)."}, 'type': {'type': 'string', 'description': 'Optional DNS record to create immediately: A, AAAA, CNAME, or TXT.'}, 'email': {'type': 'string', 'description': "Required on the account's first registration if no email is attached yet. Sends a confirmation link."}, 'label': {'type': 'string', 'description': "The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi)."}, 'domain': {'type': 'string', 'description': "Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default."}, 'content': {'type': 'string', 'description': 'Value for that record (an IP for A/AAAA, a hostname for CNAME, text for TXT).'}}}
delegate_nameservers
Delegate 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 nameservers.
Esquema de entrada
{'type': 'object', 'required': ['label', 'nameservers'], 'properties': {'label': {'type': 'string', 'description': "The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi)."}, 'domain': {'type': 'string', 'description': "Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default."}, 'nameservers': {'type': 'array', 'items': {'type': 'string'}, 'description': "Your nameserver hostnames, e.g. ['ns1.yourdns.com', 'ns2.yourdns.com']. At least two."}}}
delete_account
DESTRUCTIVE 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 names, answering 409 with the list of them; that refusal is a safety net, so show the list to the user and get an explicit yes before retrying. With force:true those names are deleted too: they stop resolving at once and are released for anyone else to claim. Only ever call this when the user has asked to close the account itself — never as cleanup after a task, and never to 'start fresh' on your own initiative.
Esquema de entrada
{'type': 'object', 'properties': {'force': {'type': 'boolean', 'description': 'Delete the names the account still holds along with it. Without this the call is refused while any name remains, which is the intended default.'}}}
delete_domain
DESTRUCTIVE 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 explicitly asked for this specific name to be deleted.
Esquema de entrada
{'type': 'object', 'required': ['label'], 'properties': {'label': {'type': 'string', 'description': "The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi)."}, 'domain': {'type': 'string', 'description': "Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default."}}}
delete_record
DESTRUCTIVE: 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_domain (and returned by claim_domain and add_dns_record); it is not the record's name or content. The hostname stops resolving through that record immediately and there is no undo.
Esquema de entrada
{'type': 'object', 'required': ['label', 'record_id'], 'properties': {'label': {'type': 'string', 'description': "The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi)."}, 'domain': {'type': 'string', 'description': "Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default."}, 'record_id': {'type': 'string', 'description': "The record's 'id' as reported by get_domain — not its name, type, or content."}}}
get_domain
Show one subdomain in full: its fqdn, DNS records, forward or proxy configuration, and delegation state.
Esquema de entrada
{'type': 'object', 'required': ['label'], 'properties': {'label': {'type': 'string', 'description': "The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi)."}, 'domain': {'type': 'string', 'description': "Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default."}}}
list_domains
List every subdomain on this account, with each one's DNS records and whether it is forwarding, proxying, or delegated to external nameservers.
Esquema de entrada
{'type': 'object', 'properties': {}}
manage_billing
Get 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 upgrade_to_pro).
Esquema de entrada
{'type': 'object', 'properties': {}}
remove_forward
Stop forwarding a subdomain. The name itself stays registered on the account; only the redirect is removed.
Esquema de entrada
{'type': 'object', 'required': ['label'], 'properties': {'label': {'type': 'string', 'description': "The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi)."}, 'domain': {'type': 'string', 'description': "Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default."}}}
remove_proxy
Stop reverse-proxying a subdomain, so the edge no longer serves the backend or terminates TLS for it. The name stays registered on the account.
Esquema de entrada
{'type': 'object', 'required': ['label'], 'properties': {'label': {'type': 'string', 'description': "The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi)."}, 'domain': {'type': 'string', 'description': "Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default."}}}
set_forward
Forward (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 for you. A forward TAKES OVER the hostname: any A/AAAA/CNAME record on the label itself is deleted as part of this call and returned in 'replaced_records' — report those to the user, since the name no longer points where it did. Records on a sub-label (www.myapp.makes.fyi) and TXT records are untouched. If the forward fails to come up the replaced records are restored, with new ids.
Esquema de entrada
{'type': 'object', 'required': ['label', 'target'], 'properties': {'cloak': {'type': 'boolean', 'description': 'Keep the AgentDomains hostname in the address bar and load the target inside a frame. Discouraged — breaks many sites.'}, 'email': {'type': 'string', 'description': 'Email, if this call also claims a new name on an account without one.'}, 'label': {'type': 'string', 'description': "The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi)."}, 'domain': {'type': 'string', 'description': "Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default."}, 'target': {'type': 'string', 'description': 'Destination URL, including scheme (e.g. https://example.com/docs).'}, 'permanent': {'type': 'boolean', 'description': 'Use a 301 permanent redirect instead of the default 302 temporary one.'}, 'preserve_path': {'type': 'boolean', 'description': 'Append the incoming path and query to the target. Defaults to true; set false to always land on the target root.'}}}
set_proxy
Serve 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 stays on your domain and the response is proxied, not redirected. Claims the label first if needed. Like a forward, a proxy TAKES OVER the hostname: A/AAAA/CNAME records on the label itself are deleted and returned in 'replaced_records', while sub-label and TXT records are untouched. A proxy and a forward are mutually exclusive on one label. Caveat: apps that hardcode their own hostname (OAuth callbacks especially) may need your new hostname registered on their side.
Esquema de entrada
{'type': 'object', 'required': ['label', 'origin'], 'properties': {'email': {'type': 'string', 'description': 'Email, if this call also claims a new name on an account without one.'}, 'label': {'type': 'string', 'description': "The subdomain label, without the domain suffix (e.g. 'myapp' for myapp.makes.fyi)."}, 'domain': {'type': 'string', 'description': "Which domain to act under: 'makes.fyi' (the default) or 'agentdomains.co'. The same label can exist under each, so pass this whenever you are not using the default."}, 'origin': {'type': 'string', 'description': 'Backend hostname to proxy to, without a scheme (e.g. myapp.fly.dev). Must be a hostname, not an IP.'}}}
signup
Create 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. The account is provisional: attach and confirm an email within 30 days (see the attach_email tool) or it is deleted along with its domains. This endpoint is rate-limited per IP address.
Esquema de entrada
{'type': 'object', 'properties': {}}
upgrade_to_pro
Get a Stripe checkout link for AgentDomains Pro: 100 names instead of the free 10, names never released for being unreachable, and priority email support, for $5/month (or $48/year with interval 'year'). Use this when a claim is refused because the account is at its name limit and the user wants more. It only returns a link and never charges anything: a human must open the URL and pay. Show them the url and say what Pro costs; do not open it or pay on their behalf. If the account is already Pro the answer has kind:'portal' and a link to manage the subscription instead. Answers 404 'billing is not enabled' on a server that does not sell Pro.
Esquema de entrada
{'type': 'object', 'properties': {'interval': {'enum': ['month', 'year'], 'type': 'string', 'description': "Billing interval: 'month' ($5, the default) or 'year' ($48)."}}}
whoami
Show 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 one account may hold at once (10 on the free plan, 100 on Pro). 'plan' is 'free' or 'pro'; when Pro is on sale a free account also gets an 'upgrade' hint (see upgrade_to_pro).
Esquema de entrada
{'type': 'object', 'properties': {}}
Historial
Cambios recientes en herramientas
Añadido
manage_billing
2 de October de 2026 a las 02:40
Añadido
upgrade_to_pro
2 de October de 2026 a las 02:40
Añadido
delete_account
2 de October de 2026 a las 02:40
Añadido
delegate_nameservers
2 de October de 2026 a las 02:40
Añadido
remove_proxy
2 de October de 2026 a las 02:40
Añadido
set_proxy
2 de October de 2026 a las 02:40
Añadido
remove_forward
2 de October de 2026 a las 02:40
Añadido
set_forward
2 de October de 2026 a las 02:40
Añadido
add_acme_challenge
2 de October de 2026 a las 02:40
Añadido
delete_record
2 de October de 2026 a las 02:40
Añadido
add_dns_record
2 de October de 2026 a las 02:40
Añadido
delete_domain
2 de October de 2026 a las 02:40
Añadido
get_domain
2 de October de 2026 a las 02:40
Añadido
list_domains
2 de October de 2026 a las 02:40
Añadido
claim_domain
2 de October de 2026 a las 02:40
Añadido
attach_email
2 de October de 2026 a las 02:40
Añadido
whoami
2 de October de 2026 a las 02:40
Añadido
signup
2 de October de 2026 a las 02:40
Añadido
check_availability
2 de October de 2026 a las 02:40
Descubrir
Servidores MCP similares
shiply
now.shiply/shiply
Publishes and manages web applications with SQL databases, serverless functions, domains, email tests, client intake, contracts, …
Fine Structure
ai.finestructure/fine-structure
Builds and hosts full-stack applications from prompts and supports agent communication through WhatsApp and email.
mcp
cloud.redu/mcp
Provisions and manages cloud instances, networks, storage, databases, backups, VPNs, application deployments, and autocoding-agen…
EchoRelay
dev.echorelay/management
Manages a hosted API relay runtime, including projects, endpoints, credentials, publishing, keys, delivery logs, and dead-letter …
Supero
io.github.supero-platform/supero
Builds, validates, publishes, tests, and deploys multi-tenant applications with schemas, CRUD operations, external data connector…
Replicate
io.github.pipeworx-io/replicate
Provides access to Replicate models, versions, collections, hardware, predictions, and deployments for running and managing hoste…
Relin
io.github.earonesty/relin
Configures webhook sources and destinations, monitors delivery health, investigates failures, manages retries, and replays events.
Scalix Cloud
world.scalix/cloud
Provides managed databases, SQL tools, container builds, persistent Linux machines, domains, scheduled functions, storage, and pr…