Connect an AI agent
Use this guide to connect an MCP-compatible AI client to Domain Chief and control what it may read or change.
Choose your task
- Connect an AI client
- Try a request
- Review the available tools
- Change the connection's permissions
- Fix a connection or permission problem
Connect an AI client
Before you connect
Your AI client must support remote MCP servers and browser-based sign-in. Use this server URL:
Code
Connect a client
Look for MCP or integrations in your client's settings, then:
- Open the client's MCP or integrations settings.
- Add a remote MCP server with the URL above.
- Sign in with your Chief account.
- Review and approve the requested scopes.
Review the requested access
The authorization screen presents all requested scopes as one set. You must approve the full set or cancel the connection.
What happens next
After connecting, give the client a specific task. For example:
- Check whether
copper-lantern.comis available. - List the DNS records for one of my domains.
- Change the
tagmetadata on this domain tostaging. - Create a redirect from
wwwto the root domain.
Review proposed write operations before allowing the agent to continue.
Available tools
The scopes you approve determine which tools the server makes available.
TLDs and contacts
| Tool | Action | Required scope |
|---|---|---|
list-tlds | List supported TLDs and indicative pricing | domainchief:tlds:read |
get-tld | Retrieve one TLD | domainchief:tlds:read |
list-contacts | List team contacts | domainchief:contacts:read |
get-contact | Retrieve one contact | domainchief:contacts:read |
Domains
| Tool | Action | Required scope |
|---|---|---|
list-domains | List team domains | domainchief:domains:read |
update-domain | Update an existing domain | domainchief:domains:write |
check-domain-availability | Check whether a domain can be registered or transferred | domainchief:domains:read:availability |
DNS records
These tools work only with domains using Domain Chief hosted DNS.
| Tool | Action | Required scope |
|---|---|---|
get-dns-record | Retrieve one DNS record | domainchief:dns:read |
list-dns-records | List DNS records | domainchief:dns:read |
create-dns-record | Create a DNS record | domainchief:dns:write |
update-dns-record | Update a DNS record | domainchief:dns:write |
delete-dns-record | Delete a DNS record | domainchief:dns:write |
clear-dns-records | Remove DNS records except records managed by redirects | domainchief:dns:write |
reset-dns-records | Restore the Domain Chief default records | domainchief:dns:write |
Web redirects
| Tool | Action | Required scope |
|---|---|---|
get-web-redirect | Retrieve one web redirect | domainchief:redirects_web:read |
list-web-redirects | List web redirects | domainchief:redirects_web:read |
create-web-redirect | Create a web redirect | domainchief:redirects_web:write |
update-web-redirect | Update a web redirect | domainchief:redirects_web:write |
delete-web-redirect | Delete a web redirect | domainchief:redirects_web:write |
Manage the connection
Change permissions
Start with read scopes. If the client needs a tool that is not available, reconnect it and approve the additional scope. Domain Chief cannot add scopes to an existing connection without another authorization step.
See Domain Chief API scopes for the full scope hierarchy.
Choose MCP or REST
Use MCP when an AI client needs to choose and call Domain Chief tools. Use the REST API for application code, fixed workflows, or endpoints that the MCP server does not expose.
Troubleshooting
Why can't the client connect?
Confirm that the client supports remote MCP servers and browser-based authorization. Copy the server URL exactly, then reconnect and complete the Chief sign-in flow.
Why is a tool missing?
The connection does not have the tool's required scope. Compare the tool with the tables above, then reconnect the client and approve the additional scope.
Why can't the agent manage DNS records?
DNS tools work only for domains using Domain Chief hosted DNS. The connection also needs the matching domainchief:dns:read or domainchief:dns:write scope.
Why does the authorization screen request unexpected access?
Cancel the connection and review which tools or integration the client is trying to enable. Domain Chief approves or rejects the requested scopes as one set.