How do AI agents use GoDaddy Domains v2 through Open Connector?

Your user connects GoDaddy Domains v2 once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes GoDaddy Domains v2 tools to your agent over MCP or a typed API, with credentials injected server-side on each call.

Is this a GoDaddy Domains v2 MCP server?

Yes. Open Connector can serve GoDaddy Domains v2 as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call GoDaddy Domains v2 actions with credentials injected server-side.

Where do GoDaddy Domains v2 credentials live?

In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

GoDaddy Domains v2 integration

GoDaddy Domains v2 integration for AI agents.

GoDaddy Domains v2 integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves GoDaddy Domains v2 tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.

View source on GitHub All integrations →

What your agents can do

Real GoDaddy Domains v2 actions, managed and audited.

Your user connects GoDaddy Domains v2 once; your agent can then manage GoDaddy domains, contacts, hosts, transfers, forwarding, and notifications through Domains API v2 — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.

1
Your user grants GoDaddy Domains v2 access once (OAuth) — the token lands in the vault.
2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
3
Every routed call appends a hash-chained audit record — nothing leaves your infra.

Tools & triggers

Supported GoDaddy Domains v2 tools.

30 tools are generated from the published GoDaddy Domains v2 catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.

Showing 30 tools. All published catalog entries are included in this page's server-rendered HTML.

Cancel the most recent user action for the specified domain: Cancels the most recent user-initiated action if it is still in a cancellable state. Returns 202 Accepted.; Domain Actions
Cancel a pending change of registrant request: Cancels a pending change of registrant. Returns 202 - poll GET .../actions/CHANGE_OF_REGISTRANT_DELETE until COMPLETED, FAILED, or CANCELLED.; Manage Domain Settings
Submit a forwarding cancellation request for the given fqdn: Removes the forwarding configuration for the FQDN. Returns 204 No Content.; Manage Domain Settings
Retrieve the forwarding information for the given fqdn: Returns the forwarding configuration for the FQDN including destination URL and redirect type. Returns 404 if no forwarding rule exists.; Manage Domain Settings
Create a new forwarding configuration for the given FQDN: Creates or replaces the forwarding configuration for the FQDN. Idempotent - replaying the same request produces the same rule. Returns 204 No Content.; Manage Domain Settings
Modify the forwarding information for the given fqdn: Updates the forwarding configuration for the FQDN. Only fields included in the request are modified. Returns 204 No Content.; Manage Domain Settings
Retrieve details for the specified Domain: Returns the full DomainDetailV2 object including status, contacts, nameservers, lock state, privacy flag, and expiration timestamp.; Manage Domain Settings
Retrieves a list of the most recent actions for the specified domain: Returns a paginated list of recent actions for the domain. Use to track long-running operations or audit domain history.; Domain Actions
Retrieves the most recent action for the specified domain: Returns the most recent action of the specified type including status, timestamps, and any error details.; Domain Actions
Retrieve change of registrant information: Returns current change of registrant details including status, requested contacts, and any pending approvals.; Manage Domain Settings
Retrieve privacy email forwarding settings showing where emails are delivered: Returns the current privacy email forwarding configuration including target address and forwarding mode.; Manage Domain Settings
Retrieve the next domain notification: Returns the next unacknowledged domain notification. Returns 200 with a Notification body, or 204 if no notifications are pending.; Domain Notifications
Retrieve a list of notification types that are opted in: Returns the notification types the account is currently opted in to receive.; Domain Notifications
Retrieve the schema for the notification data for the specified notification type: Returns the JSON schema for a specific notification type's data payload. Use to validate or parse notification data before processing.; Domain Notifications
Retrieve the schema to be submitted when registering a Domain for the specified TLD: Returns the JSON schema for the registration request body for the specified TLD. Fetch before registering to identify required fields and TLD-specific constraints.; Register Domains
Retrieve api usage request counts for a specific year/month. The data is retained for a period of three months.: Returns monthly API request counts for the account. Data is retained for three months.; Domains API Usage
Update privacy email forwarding settings to determine how emails are delivered: Updates privacy email forwarding settings. Only fields included in the request are modified. Returns 202 - poll the actions endpoint for completion.; Manage Domain Settings
Initiate inbound transfer: Initiates an inbound domain transfer from another registrar. Requires an authcode and consent object. Returns 202 - poll GET .../actions/TRANSFER until COMPLETED, FAILED, or CANCELLED.; Transfer Domains
Accept the inbound transfer: Explicitly accepts an in-progress inbound transfer to expedite the process. Returns 202 - poll GET .../actions/TRANSFER_IN_ACCEPT until the action reaches a terminal state.; Transfer Domains
Cancel the inbound transfer: Cancels an in-progress inbound transfer. Returns 202 - poll GET .../actions/TRANSFER_IN_CANCEL until the action reaches a terminal state.; Transfer Domains
Restart the inbound transfer from the beginning: Restarts a stalled inbound transfer from the beginning. Returns 202 - poll GET .../actions/TRANSFER_IN_RESTART until the action reaches a terminal state.; Transfer Domains
Retry the inbound transfer with a new authorization code: Retries a failed inbound transfer with a new authorization code. Returns 202 - poll GET .../actions/TRANSFER_IN_RETRY until the action reaches a terminal state.; Transfer Domains
Initiate an outbound transfer: Initiates an outbound transfer for .uk domains. Returns 202 - poll the actions endpoint for completion.; Transfer Domains
Accept the outbound transfer: Accepts a pending outbound transfer request. Returns 202 - poll GET .../actions/TRANSFER_OUT_ACCEPT until the action reaches a terminal state.; Transfer Domains
Reject the outbound transfer: Rejects a pending outbound transfer request, keeping the domain at GoDaddy. Returns 202 - poll GET .../actions/TRANSFER_OUT_REJECT until the action reaches a terminal state.; Transfer Domains
Acknowledge a domain notification: Acknowledges a domain notification, removing it from the notification queue. Returns 204 No Content.; Domain Notifications
Purchase and register the specified Domain: Registers the specified domain. Requires a consent object with TLD agreement keys from the schema endpoint. Charges the account's billing method. Returns 202 - poll GET .../actions/REGISTER until the action reaches a terminal state.; Register Domains
Validate the request body using the Domain Registration Schema for the specified TLD: Validates the registration request body against the TLD schema with no side effects and no charge. Returns 204 on success.; Register Domains
Replaces the existing name servers on the domain.: Replaces the domain's authoritative nameservers. Returns 202 - poll GET .../actions/DOMAIN_UPDATE_NAME_SERVERS until the action reaches a terminal state.; Manage Domain Settings
Opt in to receive notifications for the submitted notification types: Opts the account in to receiving the specified notification types. Returns 204 No Content.; Domain Notifications

FAQ

GoDaddy Domains v2 integration, answered

How do AI agents use GoDaddy Domains v2 through Open Connector?: Your user connects GoDaddy Domains v2 once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes GoDaddy Domains v2 tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a GoDaddy Domains v2 MCP server?: Yes. Open Connector can serve GoDaddy Domains v2 as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call GoDaddy Domains v2 actions with credentials injected server-side.
Where do GoDaddy Domains v2 credentials live?: In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.

Give your agents GoDaddy Domains v2 — keep the keys.

Open source, self-hostable, with GoDaddy Domains v2 credentials that never leave your infrastructure. Run it from source today.

View source on GitHub How the MCP gateway works →