Skip to content
MCP-Bridge
ProductivityAuto-generatedScore: 34

Auckland Museum API MCP Server

The Auckland Museum API, provided by the Auckland War Memorial Museum (Tāmaki Paenga Hira), is a robust and open web service designed to grant programmatic access to the museum's rich digital collections and scholarly metadata.

Quick Start Summary

The Auckland Museum API MCP server is a Model Context Protocol bridge that connects AI assistants — including Claude Desktop, Cursor, Windsurf, and VS Code Copilot — to the Auckland Museum API API through natural language. It exposes 6 API endpoints as callable tools, such as Retrieve media associated with Collections and Cenotaph subjects in Auckland Museum, Explore details about a given subject node, Perform simple search queries over Auckland Museum Collections and Cenotaph data, and more. No authentication is required — setup takes approximately 30 seconds. The server uses STDIO transport and can be installed by running npx -y @mcp/aucklandmuseum-com. This integration is sourced from the auto Auckland Museum API OpenAPI specification (v2.0.0) and has a quality score of 34/99 (fair documentation coverage).

6Endpointstools mapped
NoneAuthopen access
34/99Qualityfair
~30 secSetupno auth
View Hosted Config URLClaude Desktop Setup Guide

Server Details

Category
Productivity
Authentication
None
Endpoints
6 operations
Transport
STDIO
Spec Version
v2.0.0
Install Command
npx -y @mcp/aucklandmuseum-com

Environment Variables

AUCKLAND_MUSEUM_API_API_KEY

Example: your_auckland_museum_api_api_key

Top Endpoints

GET
/id/media/{path}

Retrieve media associated with Collections and Cenotaph subjects in Auckland Museum

GET
/id/{identifier}

Explore details about a given subject node

GET
/search/{index}/{operation}

Perform simple search queries over Auckland Museum Collections and Cenotaph data

POST
/search/{index}/{operation}

Perform complex search queries over Auckland Museum Collections and Cenotaph data

GET
/sparql

Auckland Museum SPARQL endpoint

Own this API?

Verify ownership of this listing to control the description, configuration details, and documentation links. Choose between free manual verification or instant premium placement.

Option 1: Free Verification

Slow manual review. Requires creating a GitHub issue with verified documentation or domain verification.

  • • Verified badge on page
  • • Standard search sorting
  • • 2-3 business days review
Start Free Claim →
Instant & Boosted

Option 2: Featured Upgrade($9/mo)

Instant verification plus premium styling, featured badges, and directory placement boost.

  • • ★ Featured star & amber highlight border
  • • Top of directory search placement
  • • Instant activation via claim token

📖 Detailed MCP Integration Guide

A technical breakdown of capabilities, agent workflows, and security/configuration best practices.

⚡Capabilities & Use Cases
The Auckland Museum API, provided by the Auckland War Memorial Museum (Tāmaki Paenga Hira), is a robust and open web service designed to grant programmatic access to the museum's rich digital collections and scholarly metadata. Its core capabilities revolve around the discovery and retrieval of information related to millions of cultural heritage objects, artworks, specimens, and archival records. The API enables structured queries against its collections index through flexible search operations, allowing users to filter and sort records by various fields such as object type, collection, name, or date. Furthermore, it provides direct endpoints for fetching specific media assets (like images or documents) associated with records using a stable file path and for resolving unique identifiers to their corresponding data records. These functions serve a wide array of use cases, from academic researchers conducting large-scale data analysis of collection trends, to educators building interactive learning resources, and developers creating rich, data-driven web or mobile applications that showcase the museum's holdings for public engagement.
🤖AI Agent Value
Exposing the Auckland Museum API as a toolset through the Model Context Protocol (MCP) for an AI coding assistant fundamentally transforms its utility from a static data source into a dynamic, conversational development resource. For a developer using an AI-augmented IDE, this integration allows the AI to act as a knowledgeable intermediary that can autonomously explore the museum's vast datasets. The AI can formulate and execute precise API calls on the developer's behalf, bypassing the need for manual endpoint construction and documentation lookup. This provides immense value by accelerating development workflows, enabling rapid prototyping of collection-browsing features, and offering contextual insights during the coding process. The AI can, for instance, analyze the structure of returned JSON data in real-time, suggesting data models or parsing logic, thereby reducing boilerplate and ensuring adherence to the API's actual data schema from the outset.
💬Example Workflows
In practice, a developer can instruct their AI coding assistant to perform complex, multi-step tasks that leverage the full spectrum of the API's endpoints. For example, a natural language command like "Find all Māori cloaks in the collection, retrieve the primary image for the first three results, and write a Python function to download and save them locally" would prompt the AI to sequentially use the search endpoint to query the object index with specific filters, parse the identifiers from the results, then call the media endpoint with the appropriate paths for each item, and finally generate the corresponding code. Similarly, an instruction such as "Help me build a React component that takes an object ID and displays its name, a brief description, and thumbnail" would lead the AI to query the identifier endpoint to fetch the record details, map the relevant fields to component props, and generate the necessary UI code. The AI can also assist with exploratory tasks like "What are the most frequent categories of insects in your entomology collection?" by constructing a search query to aggregate and analyze that specific field.
🛡️Security & Auth
It is critical to note that the Auckland Museum API currently operates with an open authentication model, requiring no API keys or credentials for access. While this simplifies development and encourages open innovation, developers and organizations implementing MCP servers must still adhere to responsible usage principles. This includes rigorously implementing rate limiting and request throttling on the client side to avoid overwhelming the museum's infrastructure, respecting any documented terms of service, and clearly attributing the Auckland War Memorial Museum as the data source in any derived applications. When building an MCP server, developers should configure it to cache responses appropriately to reduce unnecessary calls and ensure that any application built on this data acknowledges the non-commercial, scholarly, and cultural nature of the source material, upholding the museum's mission of preservation and education.

Similar APIs

Other APIs in the Productivity category.

Notion API

Create and manage Notion pages, databases, and blocks through your AI agent.

OAuth2

Linear API

Manage issues, projects, and workflows in Linear through your AI agent.

API Key

Platform API

The Platform API is a comprehensive RESTful interface provided by Ably, a leading provider of real-time messaging and presence infrastructure, designed to give developers granular, programmatic control over their Ably applications and resources. Its core capabilities extend beyond simple pub/sub messaging, enabling the management and inspection of channels, the retrieval and publishing of messages, the manipulation of presence state for users across those channels, and the configuration of push notification subscriptions. Typical use cases span enterprise and consumer applications where real-time functionality is critical, such as live activity feeds for e-commerce platforms, collaborative tools requiring synchronized state, multi-user gaming, real-time chat, and IoT device status monitoring. This API serves as the foundational control plane for any application built on the Ably ecosystem, allowing for dynamic, server-side orchestration of real-time behaviors.

Control API v1

The Control API v1, provided by Ably, is a comprehensive programmatic interface designed for the administrative management and automation of Ably’s real-time messaging infrastructure. It serves as the central nervous system for controlling core resources within an Ably account, enabling developers and platform engineers to dynamically provision and configure applications, manage authentication credentials (keys), organize message flow with namespaces, and establish operational rules. Its primary function is to transition infrastructure management from manual, dashboard-driven tasks to scalable, code-first operations. This makes it indispensable for enterprise use cases such as automated environment provisioning for development and testing, multi-tenant SaaS platforms requiring isolated customer channels, and large-scale IoT deployments where device groups (represented by namespaces) or security credentials (keys) must be managed programmatically in response to dynamic demand. The API currently operates in a Beta state, indicating it is feature-rich but subject to refinement based on developer feedback.

Related MCP Server Integrations

Notion API MCP Setup

Create and manage Notion pages, databases, and blocks through your AI agent.

ProductivityConfigure →

Linear API MCP Setup

Manage issues, projects, and workflows in Linear through your AI agent.

ProductivityConfigure →

Platform API MCP Setup

The Platform API is a comprehensive RESTful interface provided by Ably, a leading provider of real-time messaging and presence infrastructure, designed to give developers granular, programmatic control over their Ably applications and resources. Its core capabilities extend beyond simple pub/sub messaging, enabling the management and inspection of channels, the retrieval and publishing of messages, the manipulation of presence state for users across those channels, and the configuration of push notification subscriptions. Typical use cases span enterprise and consumer applications where real-time functionality is critical, such as live activity feeds for e-commerce platforms, collaborative tools requiring synchronized state, multi-user gaming, real-time chat, and IoT device status monitoring. This API serves as the foundational control plane for any application built on the Ably ecosystem, allowing for dynamic, server-side orchestration of real-time behaviors.

ProductivityConfigure →

Control API v1 MCP Setup

The Control API v1, provided by Ably, is a comprehensive programmatic interface designed for the administrative management and automation of Ably’s real-time messaging infrastructure. It serves as the central nervous system for controlling core resources within an Ably account, enabling developers and platform engineers to dynamically provision and configure applications, manage authentication credentials (keys), organize message flow with namespaces, and establish operational rules. Its primary function is to transition infrastructure management from manual, dashboard-driven tasks to scalable, code-first operations. This makes it indispensable for enterprise use cases such as automated environment provisioning for development and testing, multi-tenant SaaS platforms requiring isolated customer channels, and large-scale IoT deployments where device groups (represented by namespaces) or security credentials (keys) must be managed programmatically in response to dynamic demand. The API currently operates in a Beta state, indicating it is feature-rich but subject to refinement based on developer feedback.

ProductivityConfigure →

Adyen Test Cards API MCP Setup

The Adyen Test Cards API, provided by the global payment platform Adyen, is a specialized utility designed to streamline the payment integration development and testing lifecycle. Its core capability is the programmatic generation of custom test card numbers, a critical requirement for developers and QA engineers building and validating payment flows in sandbox or test environments. By exposing a dedicated endpoint, `POST /createTestCardRanges`, the API eliminates the manual process of sourcing static test card numbers from documentation or community lists. This is particularly valuable for enterprise-scale applications where testing must cover a complex matrix of scenarios, including various card schemes (Visa, Mastercard, etc.), card types (credit, debit, prepaid), issuer countries, and specific transaction outcomes like approvals, declines, and 3D Secure challenges. Typical use cases span from automated continuous integration (CI) pipelines that require unique test data for each run, to teams developing payment interfaces that must simulate a wide array of real-world customer payment methods.

ProductivityConfigure →