Timeweb Cloud domains MCP
timeweb-cloud-mcp-server
An MCP for the Timeweb Cloud API: domains, subdomains, DNS records, name servers and the full domain registration, renewal and transfer flow
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- timeweb_pay_domain_request charges real money from the account balance and sends the order to the registrar
- timeweb_update_name_servers fully overwrites a domain's name servers; a mistake can take the domain off its working servers
Install
Manual install
npm install && npm run buildBuild before connecting to an MCP client.
This is third-party code. Review the repository files before installing.
What it does
A TypeScript server provides tools for the domain side of the Timeweb Cloud API: listing and viewing a domain, attaching an already-registered domain to the account, checking registration availability, auto-renewal, subdomains, DNS records of types A, AAAA, MX, CNAME, TXT, SRV with create, update and delete, reading and fully overwriting name servers or resetting to Timeweb's defaults, a list of roughly 350 domain zones with prices and allowed purchase periods, domain admins (person, organization, sole proprietor), and the full registration, renewal or transfer cycle: creating an unpaid request, a separate payment from the account balance that charges money and sends the order to the registrar, and tracking the request's status. For .ru and .рф the period is limited to one to three years and WHOIS privacy is unavailable, which the zone list exposes.
Who it is for. For those who keep domains on Timeweb Cloud and want to manage DNS and domain registration from an agent.
Good fit when
- You want to manage DNS records and name servers for Timeweb Cloud domains from a chat with an agent
- You need to register, renew or transfer a domain, including paying from the account balance
- You want to check domain availability and zone pricing before buying
Not a fit when
- You need servers, databases or other Timeweb Cloud infrastructure: this server is only about domains and DNS
- You don't want the agent to have the technical ability to charge the account balance: timeweb_pay_domain_request does exactly that
- You work only with classic Timeweb hosting, not Timeweb Cloud: authorization here uses TIMEWEBCLOUD_TOKEN, a different API
Example request
Check whether example.ru is available, show the price and registration period, and create a request, but don't pay without my confirmationLimitations
The repository has no license. Domain registration is a paid two-step process: creating the request alone does not charge money, only timeweb_pay_domain_request does, and the README explicitly asks to confirm payment with the user. The request object carries no progress field; status has to be checked with a separate domain-list call via the domain_status and request_status fields.
How to disable. Remove the timeweb-cloud entry from your MCP client config and revoke the TIMEWEBCLOUD_TOKEN in the Timeweb Cloud panel.
MCP
- Transport
- stdio
- Authentication
- API key
| Environment variables | |
|---|---|
| TIMEWEBCLOUD_TOKEN required, secret | Token from the Timeweb Cloud panel, API & Integrations section |
Security check
- timeweb_pay_domain_request charges real money from the account balance and sends the order to the registrar
- timeweb_update_name_servers fully overwrites a domain's name servers; a mistake can take the domain off its working servers
README in short
The README groups tools by domains, subdomains, DNS, name servers, zones, admins and registration requests, lists Timeweb's default name servers, explains the two-step paid registration with an explicit request to confirm payment, .ru and .рф zone quirks around period and WHOIS privacy, the DNS record body format, and gives a step-by-step domain registration scenario from price check to status polling.
FAQ
Does creating a registration request charge money right away?
No, timeweb_create_domain_request only creates an unpaid request; the separate timeweb_pay_domain_request call is what charges money.
How do I know if a domain from a request is registered yet?
Via timeweb_list_domains: domain_status moves from no_paid to paid, and request_status from registration_request to null.
Related
An MCP server built into the Netdata agent: metrics, logs, alerts and live process, service and container data for an AI assistant
GitHub's official MCP server: code, issues, pull requests, Actions and security alerts straight from the agent
Agent Skills for Google products
Agent Skills for Google products and technologies
Official Google skill collection for working with Google Cloud, BigQuery, GKE, ads and analytics from an agent
AWS's official MCP server suite: docs, IaC, containers, serverless, databases, cost and monitoring