Integration

PowerDNS Authoritative integration

PowerDNS Authoritative Server is a self-hosted authoritative DNS server whose HTTP API drives every part of a zone's life. List the servers a deployment exposes and read their runtime configuration settings and statistics, create, read, replace and delete zones, edit records by sending RRset changes, export a zone in AXFR text form, retrieve a secondary zone from its primary, send NOTIFY to the configured secondaries, rectify a zone after a DNSSEC change, search across zone names, record names and record contents, manage DNSSEC cryptokeys and per-zone metadata such as ALLOW-AXFR-FROM and SOA-EDIT, manage TSIG keys, manage autoprimaries, place zones into views and map networks to a view, and flush one name out of the packet cache. The host is part of the credential because every install is its own deployment. Authentication is the api-key configured on the server, sent in the X-API-Key header.

Connect PowerDNS Authoritative How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in PowerDNS Authoritative.Built from the 41 PowerDNS Authoritative tools below, on the connection you add once.

What you can do with PowerDNS Authoritative

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Zone, 6 operations

create_zoneCreate zonePOSTCreates a new domain, returns the Zone on creation.
delete_zoneDelete zoneDELETEDeletes this zone, all attached metadata and rrsets.
get_zoneGet zoneGETzone managed by a server.
list_zonesList zonesGETList all Zones in a server.
update_zoneUpdate zonePUTModifies basic zone data.
update_zone_rrsetsUpdate zone rrsetsPATCHCreates/modifies/deletes RRsets present in the payload and their comments. Returns 204 No Content on success.

Cryptokey, 5 operations

create_zone_cryptokeyCreate zone cryptokeyPOSTCreates a Cryptokey.
delete_zone_cryptokeyDelete zone cryptokeyDELETEThis method deletes a key specified by cryptokey_id.
get_zone_cryptokeyGet zone cryptokeyGETReturns all data about the CryptoKey, including the privatekey.
list_zone_cryptokeysList zone cryptokeysGETGet all CryptoKeys for a zone, except the privatekey.
update_zone_cryptokeyUpdate zone cryptokeyPUTThis method (de)activates a key from zone_name specified by cryptokey_id.

Metadata, 5 operations

create_zone_metadataCreate zone metadataPOSTCreates a set of metadata entries.
delete_zone_metadataDelete zone metadataDELETEDelete all items of a single kind of domain metadata.
get_zone_metadataGet zone metadataGETGet the content of a single kind of domain metadata as a Metadata object.
list_zone_metadataList zone metadataGETGet all the Metadata associated with the zone.
replace_zone_metadataReplace zone metadataPUTReplace the content of a single kind of domain metadata.

Tsigkey, 5 operations

create_tsig_keyCreate tsig keyPOSTAdd a TSIG key.
delete_tsig_keyDelete tsig keyDELETEDelete the TSIGKey with tsigkey_id.
get_tsig_keyGet tsig keyGETGet a specific TSIGKeys on the server, including the actual key.
list_tsig_keysList tsig keysGETGet all TSIGKeys on the server, except the actual key.
update_tsig_keyUpdate tsig keyPUTThe TSIGKey at tsigkey_id can be changed in multiple ways: * Changing the Name, this will remove the key with tsigkey_id after adding. * Changing the Algorithm * Changing the Key.

View, 4 operations

add_zone_to_viewAdd zone to viewPOSTAdds a zone to a given view, creating it if needed.
list_viewsList viewsGETList all views in a server.
list_view_zonesList view zonesGETList the contents of a given view.
remove_zone_from_viewRemove zone from viewDELETERemoves the given zone from the given view.

Autoprimarie, 3 operations

create_autoprimaryCreate autoprimaryPOSTAdd an autoprimary.
delete_autoprimaryDelete autoprimaryDELETEDelete the autoprimary entry.
list_autoprimariesList autoprimariesGETGet a list of autoprimaries.

Network, 3 operations

get_network_viewGet network viewGETReturn the view associated to the given network.
list_networksList networksGETList all registered networks and views in a server.
set_network_viewSet network viewPUTSets the view associated to the given network.

Config, 2 operations

get_config_settingGet config settingGETReturns a specific ConfigSetting for a single server.
list_config_settingsList config settingsGETReturns all ConfigSettings for a single server.

Server, 2 operations

get_serverGet serverGETList a server.
list_serversList serversGETList all servers.

Axfr retrieve, 1 operation

retrieve_zone_from_primaryRetrieve zone from primaryPUTRetrieve slave zone from its master.

Flush, 1 operation

flush_cache_entryFlush cache entryPUTFlush a cache-entry by name.

Notify, 1 operation

notify_zoneNotify zonePUTSend a DNS NOTIFY to all slaves.

Rectify, 1 operation

rectify_zoneRectify zonePUTRectify the zone data.

Search data, 1 operation

search_zones_and_recordsSearch zones and recordsGETSearch the data inside PowerDNS.

Statistic, 1 operation

get_statisticsGet statisticsGETQuery statistics.

Use PowerDNS Authoritative from Claude Code, Cursor or Codex

Connect PowerDNS Authoritative in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its PowerDNS Authoritative operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect PowerDNS Authoritative

Create your workspace
Sign up free. Nothing to install.
Connect PowerDNS Authoritative once
Add your PowerDNS Authoritative connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.