MCP server for Beget API

Beget Hosting MCP

Connect Beget domain, DNS, website, mail, database and backup management to Cursor, Codex or any other MCP-compatible client.

Python 3.11+ stdio MIT License
Cursor / Codex tools/list
Beget Hosting MCP 4 tools
Beget API domain.getList
connected · read + guarded write
4universal MCP tools
65Beget API methods indexed
2write-protection levels

One interface for hosting operations

The server follows the standard MCP protocol without hiding the Beget API model: clients can discover, inspect and call methods with explicit parameters.

01

Tools are discovered automatically

Cursor, Codex and other MCP clients receive the tool list at startup and can search the built-in catalogue for the right API method.

02

Writes require explicit consent

Mutating requests need both server-level enablement and a separate confirmation flag on every tool call.

03

Documentation stays local

The repository includes a Markdown archive and structured index of the official documentation, removing the need to scan the website again.

Beget API coverage

Individual operations depend on the hosting plan, API password permissions and capabilities available to the Beget account.

user.*Account and limits
domain.*Domains and subdomains
dns.*DNS records
site.*Sites and bindings
ftp.* / mysql.*FTP and databases
mail.*Mail and mailboxes
cron.*Scheduled tasks
backup.* / statistic.*Backups and statistics

Quick start

Install without a separate service

Install the package, create a dedicated Beget API password and add the launch command to your MCP client configuration.

Open setup guide
terminal
python -m pip install .
beget-hosting-mcp --list-tools

# Credentials for a dedicated API password
BEGET_LOGIN=your-login
BEGET_API_PASSWORD=your-api-password

# Writes are disabled by default
BEGET_ALLOW_WRITE=false

Predictable operations

The wrapper adds checks around the API, but final results still depend on external infrastructure and may not be visible immediately.

  • A dedicated API password must be enabled in the Beget control panel.
  • DNS changes propagate with a delay because of TTL and resolver caching.
  • Website, mail and backup operations may complete asynchronously.
  • Result checks do not repeat mutating requests unless explicitly required.