Auckland Museum API MCP Server Integration
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.
Technical Integration & Multi-Client Support
The Auckland Museum API MCP Integration translates REST paths, operational endpoints, and tool schemas into standardized Model Context Protocol JSON-RPC 2.0 messages. This allows AI assistants like Claude Desktop, Cursor IDE, VS Code (Cline/Roo Code), and Zed Editor to run tool queries and execute functions seamlessly.
Add stdio configuration block to claude_desktop_config.json.
Configure workspace root at .cursor/mcp.json or Settings -> MCP.
Insert server JSON payload into cline_mcp_settings.json.
Specification & Compatibility Table
| Property | Specification Detail |
|---|---|
| Target Integration | Auckland Museum API (aucklandmuseum-com) |
| Directory Category | productivity |
| Protocol Spec | JSON-RPC 2.0 (stdio) |
| Canonical Path | /mcp/aucklandmuseum-com/ |
Frequently Asked Questions
How do I access the full JSON configuration for Auckland Museum API?
Click 'Open Full Auckland Museum API MCP Config' above to view the complete parameter schema, environment variable setup, and copy-pasteable JSON configs for Claude Desktop, Cursor, and VS Code.
Does Auckland Museum API require authentication secrets?
Authentication depends on upstream API requirements. Check the environment variable table on the detail page to view required API keys and header tokens.
Related Integrations
Notion MCP
Create and manage Notion pages, databases, and blocks through your AI agent.
Linear API MCP
Manage issues, projects, and workflows in Linear through your AI agent.
Platform API MCP
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 MCP
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.
Browse by Category
Explore MCP server integrations organized by platform and use case.