Skip to content
MCP-Bridge
ProductivityNo Auth RequiredAuto OpenAPIQuality Score: 34/99

Auckland Museum API MCP Server Integration Guide

Quick Start Architecture Summary

The Auckland Museum API MCP server is a Model Context Protocol integration that connects AI assistants (Claude Desktop, Cursor IDE, VS Code, Zed) to the Auckland Museum API API through natural language directives. It exposes 6 API operations as callable MCP tools, including 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 — operates out of the box immediately. Sourced from the auto Auckland Museum API OpenAPI specification (v2.0.0) with an overall quality score of 34/99.

Technical Overview & Protocol 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.

By converting the OpenAPI 3.0 specification for Auckland Museum API into native Model Context Protocol (MCP) tool definitions, developers and AI agents gain programmatic access to endpoints over stdio or HTTP transports. Every endpoint is translated into a discrete tool payload complete with input argument validation, parameter descriptions, and return type definitions.

This setup enables LLM agents to execute multi-step workflows, search records, mutate state, and analyze responses safely within local desktop client sessions like Claude Desktop and Cursor IDE.

2. Technical Specifications Matrix

System Specifications

API NameAuckland Museum API
Slug Identifieraucklandmuseum-com
CategoryProductivity
Auth MethodNone Required
Endpoint Count6 tools mapped
Spec VersionOpenAPI v2.0.0
Transport TypeSTDIO
Publisher Sourceauto

Developer Resources

Hosted Config JSON Registry URL→Claude Desktop Config Guide→

3. Multi-Client Installation Matrix

Copy and paste these pre-formatted JSON snippets into your MCP client configuration files.

Claude Desktop

Add to claude_desktop_config.json

{
  "mcpServers": {
    "aucklandmuseum-com": {
      "command": "npx",
      "args": [
        "-y",
        "@mcp/aucklandmuseum-com"
      ],
      "env": {
        "AUCKLAND_MUSEUM_API_API_KEY": "your_auckland_museum_api_api_key"
      }
    }
  }
}
Deep link

Cursor IDE

Settings → MCP Servers → Add Hosted Config

{
  "mcpServers": {
    "aucklandmuseum-com": {
      "url": "https://mcpbridge.org/config/aucklandmuseum-com.json"
    }
  }
}

Saves as .cursor/mcp.json in the download. Move it to your project root.

Deep link install →

VS Code / Cline

Use with MCP extension config

{
  "mcpServers": {
    "aucklandmuseum-com": {
      "url": "https://mcpbridge.org/config/aucklandmuseum-com.json"
    }
  }
}

4. Environment Variables & Authentication Reference

Key parameters and credential variable mappings for Auckland Museum API.

Variable NameRequiredExample Value
AUCKLAND_MUSEUM_API_API_KEYREQUIREDyour_auckland_museum_api_api_key

5. Endpoints & Tool Schemas Matrix

Search and inspect the 6 tool signatures mapped from OpenAPI.

Executable Code Integration Examples

Call Auckland Museum API endpoints via cURL, TypeScript, or Python REST SDKs.

curl -X GET "https://api.apis.guru/v2/specs/aucklandmuseum.com/2.0.0/swagger.json/id/media/{path}" \
  -H "Content-Type: application/json" \
  # No auth required

6. Real-World AI Assistant Prompts

Prompt directives for invoking Auckland Museum API operations inside AI client chats.

1. Information Search & Resource Querying

Read Query

"Use Auckland Museum API MCP server tools to search resources matching path '/id/media/{path}' and summarize available properties."

2. Action Execution & API Payload Creation

Action Execution

"Call Auckland Museum API operation '/id/media/{path}' with parameters configured for environment testing."

3. Multi-Step API Workflow Automation

Workflow Automation

"Inspect recent responses from Auckland Museum API API, extract target identifiers, and format a clean diagnostic report."

4. Introspection & Schema Audit

Introspection

"Retrieve the full OpenAPI tool schema list for Auckland Museum API MCP server and generate a technical summary of capabilities."

7. Error Resolution & Troubleshooting Guide

HTTP status codes and JSON-RPC protocol error resolution matrix.

400 Bad Request

Root Cause: Malformed request payload parameters or missing required JSON Schema fields.

Resolution Action: Verify request schema in Section 5 tool specifications before calling operation.

401 Unauthorized

Root Cause: Missing or invalid API key credentials in MCP environment config.

Resolution Action: Define required key in client config under env object.

403 Forbidden

Root Cause: Insufficient scope permissions or unauthorized resource access.

Resolution Action: Check key permissions in developer control panel.

404 Not Found

Root Cause: Resource URL path or requested target ID does not exist.

Resolution Action: Inspect path parameters and resource ID values.

429 Rate Limit Exceeded

Root Cause: Upstream API rate limit quota exceeded.

Resolution Action: Implement exponential backoff retry in tool execution loop.

500 Internal Server Error

Root Cause: Upstream service runtime fault or stdio process crash.

Resolution Action: Inspect STDIO stderr output stream for diagnostic trace.

8. Quality Scorecard & Audit Metadata

Automated evaluation metrics for OpenAPI specification quality.

Quality Grade Index
34
★ Fair Quality Grade
Score Breakdown Checklist
✓Auto-generated specification (+12 pts)
✓OpenAPI 3.0 specification available (+8 pts)
✓6 endpoint schemas (+14 pts)

Similar Productivity APIs

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.

← Back to Directory

Related MCP Server Integrations

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 →

Amazon Lex Runtime V2 MCP Setup

Amazon Lex Runtime V2 is a sophisticated conversational AI service provided by Amazon Web Services that enables developers to manage and interact with chatbot sessions in real time. This API serves as the runtime interface for Amazon Lex bots, allowing applications to communicate with bots that have already been built and published. The service is designed to handle natural language understanding and dialogue management at scale, supporting multiple languages and locales within a single bot configuration. Typical enterprise use cases include deploying intelligent virtual agents for customer service portals, automating FAQ responses in e-commerce platforms, integrating voice and text-based conversational interfaces into enterprise applications, and powering interactive voice response systems for contact centers. Consumer-facing applications often leverage Lex V2 for personal assistant functionality, appointment scheduling bots, and interactive troubleshooting guides. The Runtime V2 API is distinct from the Build-time API, as it focuses exclusively on session-based interactions rather than bot creation or training, making it the critical endpoint for any production deployment that requires real-time user engagement.

ProductivityConfigure →

Amazon Textract MCP Setup

Amazon Textract is a machine learning service from Amazon Web Services (AWS) that automatically extracts text, handwriting, and structured data from scanned documents. Going beyond basic OCR, it employs advanced models to understand document layouts and identify the semantic relationships between data elements. Its core capabilities include the detection and analysis of printed text, handwritten text, and complex tabular data, as well as the extraction of specific data points from pre-defined document types like invoices, receipts, and identity documents. Typical enterprise use cases span automating accounts payable workflows by parsing invoices, digitizing medical records for analysis, automating loan processing by extracting information from financial statements, and enhancing searchability across vast archives of scanned documents. For consumer applications, it can power apps that digitize receipts for expense tracking or automate form filling by reading physical ID cards.

ProductivityConfigure →

Appwrite Client MCP Setup

The Appwrite Account API represents a core component of the Appwrite Backend-as-a-Service (BaaS) platform, designed to radically accelerate development by managing the complete lifecycle of user accounts through a simplified RESTful interface. Provided by Appwrite, an open-source, self-hosted backend server, this API abstracts complex user management logic into a series of secure endpoints. It handles essential operations including creating and deleting accounts (POST /account, DELETE /account), updating core profile details like email, name, and password (PATCH /account/email, PATCH /account/name, PATCH /account/password), and managing authentication sessions and JSON Web Tokens (POST /account/jwt). Furthermore, it provides access to user activity logs (GET /account/logs) and allows for the storage and retrieval of arbitrary user preferences (GET /account/prefs, PATCH /account/prefs). Typical use cases span from simple mobile applications needing quick user signup to enterprise platforms requiring robust, self-service account administration, with Appwrite handling the secure storage, session management, and verification processes that would otherwise demand significant custom backend development.

ProductivityConfigure →

Appwrite Server MCP Setup

Appwrite is a comprehensive open-source Backend-as-a-Service (BaaS) platform designed to dramatically accelerate the development of modern web, mobile, and Flutter applications by abstracting complex backend infrastructure into a suite of intuitive, secure, and scalable RESTful APIs. It provides a self-hosted or cloud-based backend that handles critical services such as user authentication, database operations, file storage, messaging, and serverless functions, effectively eliminating the need for developers to build and maintain these intricate systems from scratch. The specific account management endpoints detailed here form the core of Appwrite's user identity system, enabling robust operations like retrieving user profiles, updating credentials and metadata, managing password recovery flows, and maintaining audit logs. This API is provided by Appwrite and is utilized across a wide spectrum of applications, from individual developer projects and startups seeking rapid prototyping to enterprise-scale solutions requiring a secure, compliant, and customizable user management backbone for their SaaS platforms, e-commerce sites, or internal tools.

ProductivityConfigure →
← View Auckland Museum API Directory Entry