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.
“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.”
Setup, authentication and the full tool reference live in the official MCP documentation, which is kept up to date with the server.
MCP docsWhat an assistant may do, and which actions wait for your approval, depends on your MCP roles and policy settings. Review them in the MCP dashboard before you connect an assistant.
The MCP server works on top of the same Openprovider API documented here, so you can prototype with an assistant and then move to direct API calls for production automation. MCP uses its own sign-in and API keys, separate from your REST API credentials.
API reference