Meister MCP Server — Streamable HTTP Catalog Tools
Connection and protocol
Endpoint: /.well-known/mcp on the canonical Meister storefront origin. Use the Model Context Protocol Streamable HTTP transport. Clients send JSON-RPC messages by POST with Accept: application/json, text/event-stream and Content-Type: application/json. Initialize before calling tools, send the initialized notification, and use the negotiated MCP-Protocol-Version for subsequent requests. This stateless server returns JSON responses, does not issue session IDs and does not offer a standalone SSE stream; GET returns 405.
Tools and limits
search_products accepts query (up to 120 characters), optional category (fins, suits, guns, accessories or merch) and limit (1–20). get_product accepts a product slug (up to 512 characters). Both return public catalog data and canonical product URLs. Product price ranges and variations must be reviewed before recommending a specific option. Backend failures return tool errors rather than demo products. Request bodies are limited to 64 KiB. An invalid Origin is rejected with 403. Anonymous server clients can read the catalog; customer, cart, order and payment tools are not provided.