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

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

Is this a GoDaddy Domains v3 MCP server?

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

Where do GoDaddy Domains v3 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 v3 integration

GoDaddy Domains v3 integration for AI agents.

GoDaddy Domains v3 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 v3 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 v3 actions, managed and audited.

Your user connects GoDaddy Domains v3 once; your agent can then discover, quote, register, renew, transfer, and manage domains and DNS through GoDaddy Domains API v3 — 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 v3 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 v3 tools.

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

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

Create a DNS record for a zone: Creates a new DNS record in the GoDaddy-managed zone. Changes are applied synchronously; no operation polling required.; Records
Delete a DNS record: Permanently removes a DNS resource record from the zone. The recordId must refer to an existing record within the specified zone. Changes are applied synchronously. GoDaddy-managed system records (SOA and NS) are read-only. When recordId refers to such a record, the request fails with `409 Conflict` — the record exists but cannot be deleted.; Records
Get a registered domain: Returns the management view of a single registered domain owned by the authenticated account, including status, nameservers, privacy and auto-renew preferences, and expiry date.; Domains
Check availability of a single domain: Returns an indicative availability result for one domain, including per-term pricing when available. Availability is best-effort; the authoritative check is performed at quote time. This operation does not persist the check — there is no check identity or poll URL. A domain that cannot be checked is still returned as a `200` with an `error` object on the body; request-level failures use the `4xx` responses.; Discovery
Poll an async domain operation: Universal poll endpoint for all asynchronous domain mutations. Returns the current state of the operation. Non-terminal responses include a `Retry-After` header. Terminal statuses: - `COMPLETED` — operation succeeded; `result` contains the final outcome. - `FAILED` — operation terminated with an error; `error` contains detail. While status is non-terminal (`CONFIRMED`, `EXECUTING`), neither `result` nor `error` is present. Poll until a terminal status is reached. The poll URL is provided in the `Location` header of the initiating 202 response and in `links[rel=self]`. Clients must not construct this URL independently.; Operations
Get a registration record: Returns a single registration record by its server-assigned registrationId, including the current execution status and the domain expiry date once the registration completes. This is the concrete poll endpoint for registration operations; the abstract equivalent is GET /operations/{operationId}.; Registrations
List DNS records in a zone: Returns a paginated collection of DNS resource records for the specified zone. Supports filtering by record type and host name, field projection, and page-based pagination. Pagination uses page (1-based) and pageSize query parameters. Pass totalRequired=true to include totalItems and totalPages when at least one record matches; both are omitted for empty result sets. Defaults to false to avoid count-query overhead. Filter parameters are combined with logical AND. Pagination links in the response preserve active filter, pagination, and field-projection parameters. sortBy and sortOrder are not supported. Results are always returned in canonical zone-file order: resource record type (IANA RR type number ascending — e.g. A before NS before CNAME), then name, then data. This matches authoritative DNS ordering and is not client-configurable.; Records
Quote a single-domain registration (no commitment): Prices the registration, resolves contact and preference settings, returns required legal agreements, and mints a single-use quoteToken with a 10-minute TTL. Free and read-only; safe to call speculatively. When the domain is unavailable, `available: false` is returned with no quoteToken — this is a valid non-error response. When required contact fields are missing, a `422` is returned with field-level details so the agent can collect the missing data and re-quote. May pass `iscCode` to lock pricing at applicable rates; the same value must be supplied on /registrations if provided here. The `period` supplied here must be re-supplied on /registrations; a mismatch returns `quote_mismatch`. If `profile` or `profileId` is supplied here, the same value must be re-supplied on /registrations; a mismatch returns `quote_mismatch`.; Registration Quotes
Register a domain (requires quoteToken): Executes a previously quoted domain registration. **Irreversible once accepted; creates a charge.** Requires a valid unexpired quoteToken from `quoteDomainRegistration`, an `Idempotency-Key` header, and a consent record. The target domain and period are in the request body alongside the quoteToken. Before calling this endpoint, retrieve `requiredAgreements` from the quote response and review each agreement before submitting the registration. Each agreement includes a `title` (display label) and optional `url` (full legal text). The `consent.agreementTypes` array must contain the `agreementType` value from every item in `requiredAgreements`; a mismatch returns `INVALID_AGREEMENT_KEYS`. Idempotency takes precedence over the single-use check: retrying with the same `Idempotency-Key` replays the original operation even after the token is consumed. Returns a `Registration` entity. Poll `links[rel=self]` (`GET /registrations/{registrationId}`) until status is `COMPLETED` or `FAILED`. The `operationId` field is also provided for clients that prefer `GET /operations/{operationId}`; both resolve the same resource. Poll either until status is `COMPLETED` or `FAILED`. The operation is fire-and-forget; always poll at least once even if the server completed it synchronously. When `iscCode` was supplied at quote time, the same value must be provided here or the request fails with `quote_mismatch`. When `period` was supplied at quote time, the same value must be provided here or the request fails with `quote_mismatch`. When `profile` or `profileId` was supplied at quote time, the same value must be provided here or the request fails with `quote_mismatch`.; Registrations
Suggest available domains for a query: Returns available domain name suggestions for a natural-language query or keyword set. All results are available (available-only contract). Prices are indicative; the authoritative price and availability check is at quote time.; Discovery
Replace the nameservers for a domain: Replaces the authoritative nameservers for the domain with the provided list. Minimum 2, maximum 13. Returns a DomainOperation; propagation to the registry is asynchronous.; Domain Management

FAQ

GoDaddy Domains v3 integration, answered

How do AI agents use GoDaddy Domains v3 through Open Connector?: Your user connects GoDaddy Domains v3 once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes GoDaddy Domains v3 tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
Is this a GoDaddy Domains v3 MCP server?: Yes. Open Connector can serve GoDaddy Domains v3 as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call GoDaddy Domains v3 actions with credentials injected server-side.
Where do GoDaddy Domains v3 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 v3 — keep the keys.

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

View source on GitHub How the MCP gateway works →