Integration

DigitalNZ integration

DigitalNZ searches the metadata of millions of New Zealand digital items (images, newspapers, books, audio, video, archives, research papers and more) aggregated from New Zealand libraries, museums, archives, government and community groups. Search records by text with filters on category, content partner, collection, subject, creator, place, date, usage rights and a geographic bounding box, with facet counts; read one record's metadata, including links to the item and its thumbnail; and find records similar to a given one. Not included: the XML and RSS response formats, and the exclusion and OR filter syntaxes, whose parameter names are built per field. DigitalNZ holds metadata and pointers only, never the items themselves. Authentication is a DigitalNZ API key sent in the Authentication-Token header; DigitalNZ also serves unauthenticated requests under a shared rate limit.

Connect DigitalNZ How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in DigitalNZ.Built from the 3 DigitalNZ tools below, on the connection you add once.

What you can do with DigitalNZ

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.

Record, 1 operation

get_recordGet recordGETReturns the metadata of one DigitalNZ record: title, description, content partner, collection, category, creator, subjects, dates, rights and the URLs of the item and its thumbnail.

Records format, 1 operation

search_recordsSearch recordsGETSearches DigitalNZ records by text and filters, and returns one page of matching records with their metadata, plus facet counts when facets is set.

Use DigitalNZ from Claude Code, Cursor or Codex

Connect DigitalNZ in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its DigitalNZ 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 DigitalNZ

Create your workspace
Sign up free. Nothing to install.
Connect DigitalNZ once
Add your DigitalNZ 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.