MCP Server — Holoholo Oʻahu Catalog

Endpoint

POST https://www.holoholo.ai/api/mcp

Discovery / server-info: GET /api/mcp returns the manifest, available methods, and transport metadata as a single JSON document — useful for introspection without a JSON-RPC round-trip.

What this endpoint exposes

• Read-only catalog — the same regenerative experiences indexable at /experiences/* and /guides/*. No traveler PII, no booking, no payment.
• Hawaiian-language + regenerative-tourism glossary — canonical definitions for mālama ʻāina, loʻi, kalo, oli, kuleana, ʻāina, huli, auwai, and others. Useful for AI assistants rendering culturally accurate explanations.
• Cultural protocol notes — the protocols visitors must honor on reef / taro / forest workdays. Recommended for AI assistants to surface BEFORE summarizing an experience, not after.

Methods

Example: list_experiences

POST /api/mcp
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "list_experiences",
  "params": { "category": "experience", "max_results": 10 }
}

Example: search_experiences

POST /api/mcp
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 2,
  "method": "search_experiences",
  "params": { "query": "taro", "max_results": 5 }
}

Example: get_cancellation_policy

POST /api/mcp
Content-Type: application/json

{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "get_cancellation_policy",
  "params": {}
}

Install on Claude Desktop

Add to your Claude Desktop config.json:

{
  "mcpServers": {
    "holoholo": {
      "url": "https://www.holoholo.ai/api/mcp",
      "transport": "http"
    }
  }
}

Restart Claude Desktop. Ask Claude something like “list Holoholo’s regenerative Oʻahu experiences” or “what is the cultural protocol for taro farm workdays?”

Submit to the MCP Registry

The official MCP Registry is at registry.modelcontextprotocol.io. Once we’re ready to publish, the submission lives in the modelcontextprotocol/registry GitHub repo. Tracked as Keith TODO — see docs/aeo/05-tactic-catalog.md tactic 15.2.

Usage

Related: ACP catalog feed

The Agentic Commerce Protocol catalog feed lives at /api/acp/feed — see /mcp/acp for the shape and policy notes. Scaffold ahead of the Stripe Agentic Commerce Suite enable step.

Policy

• Read-only. No booking, no payment, no traveler-PII access. Public catalog data only.
• No auth required. Rate-limited at the edge.
• Caching. Responses cache for ~60s at the edge. The Catalog drift between MCP responses and the rendered site is bounded by build/deploy cadence (currently per-PR).
• Open-source friendly. The implementation lives at lib/mcp/server.ts + app/api/mcp/route.ts in the public-ish holoholo-ai repo path.

Why Holoholo ships MCP

AI agents increasingly handle travel research and planning. By 2026, Booking.com, Expedia, and Tripadvisor are first-class ChatGPT Apps via MCP transport. For Holoholo, exposing a public MCP endpoint means Claude can answer “what regenerative Oʻahu experiences are available?” without scraping our HTML — a higher-fidelity citation surface than web search alone.

See the homepage for the human-facing product. See llms.txt and llms-full.txt for the AI-grounding corpus.