Let AI assistants safely manage domains, DNS and SSL on your behalf, through the Openprovider API.
The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external tools and data sources. The Openprovider MCP server exposes the REST API as a set of MCP tools, so assistants like Claude can check availability, register domains, edit DNS zones and order certificates using natural language, while every action still runs through your authenticated account.
Beta. The Openprovider MCP server is being rolled out. Full setup and tool details are in the official MCP documentation at mcp.openprovider.com/docs. You can also check the API reference for the underlying endpoints available today.
“Is mybrand.io available? If so, register it for two years.”
“Add an A record for app.example.com pointing to 203.0.113.10.”
“Order a DV certificate for example.com and email the approver.”
Add the Openprovider server to your MCP-compatible client (for example, Claude Desktop) by editing its configuration file. Provide your Openprovider credentials via environment variables:
{
"mcpServers": {
"openprovider": {
"command": "npx",
"args": ["-y", "@openprovider/mcp-server"],
"env": {
"OPENPROVIDER_USERNAME": "you@example.com",
"OPENPROVIDER_PASSWORD": "your-password"
}
}
}
}Once connected, the assistant can call Openprovider tools that map directly onto REST endpoints such as POST /domains/check, POST /dns/zones and POST /ssl/orders.
An MCP server acts with your account’s full permissions. Run it with a dedicated API user, enable IP whitelisting, and review the assistant’s proposed actions before approving anything that creates, modifies or deletes resources.
The MCP server is a thin, AI-friendly wrapper over the same REST API documented here. Anything the server can do is also available directly over HTTPS, so you can prototype with an assistant and then move to direct API calls for production automation.
Browse the API reference