Mamanida for AI agents

Mamanida is MCP-ready

Mamanida supports the Model Context Protocol (MCP). We run a public, read-only MCP server that compatible AI clients and agents can connect to in order to discover and compare maternity and nursing fashion from the Mamanida catalogue, across ten localized storefronts.

MCP compatibility means a compatible client can connect to Mamanida once it has been given this endpoint. It does not mean that any AI platform discovers Mamanida automatically: assistants only reach this server when an operator or user configures it. Mamanida is a comparison and discovery service — we do not sell products, we are not the merchant of record, and no purchase can be completed through MCP.

Endpoint
https://mamanida.com/mcp
Transport
Streamable HTTP
Authentication
None
Access model
Public, read-only
Server name
mamanida-mcp
Server version
1.0.0
Tools
5

01

Connecting

Point any MCP client that speaks Streamable HTTP at https://mamanida.com/mcp. No API key, account or authentication header is required. The endpoint is read-only: there are no write, checkout, import or administrative operations.

Use standard MCP protocol negotiation rather than assuming one fixed protocol revision. The server negotiates the revision with the client during initialization, and newer client revisions are supported alongside the server's baseline.

02

Available tools

The server exposes exactly five tools.

  • search_products

    Search the eligible Mamanida catalogue for a specified storefront, optionally by free-text query, canonical category, brand or sale state.

  • get_product

    Retrieve structured public product information for one product on one storefront.

  • compare_products

    Compare multiple Mamanida products on one storefront using consistent structured fields.

  • list_categories

    Discover the valid, localized canonical product categories for a storefront, with the exact slugs to pass to search_products.

  • get_guides

    Discover and retrieve Mamanida's editorial shopping guides in the storefront's own language.

03

Storefronts

Mamanida is organised into ten storefronts. Where a tool requires it, the storefront must be supplied explicitly — there is no implicit default and no cross-storefront fallback. Catalogue eligibility, language, pricing and outbound availability all depend on it.

  • int International (English)
  • us United States
  • se Sweden
  • dk Denmark
  • no Norway
  • fi Finland
  • fr France
  • nl Netherlands
  • es Spain
  • de Germany

04

Price semantics

Prices are returned with explicit provenance so an agent never presents a converted figure as a retailer price.

  • retailer_authoritative — the retailer-native authoritative price, in the currency the retailer actually charges.
  • local_display — the localized display price for the requested storefront. When it is a conversion rather than a retailer-native price it is explicitly marked as approximate and its display text is prefixed with ~. Such a value must never be presented as an authoritative retailer price.
  • original_retailer_authoritative and original_local_display — present only when a product carries an authoritative original (pre-discount) price, and following exactly the same authoritative/approximate distinction. They are omitted for products that are not on sale; a missing value must not be reconstructed from a discount percentage.

05

Availability

Availability is a tri-state value.

  • IN_STOCK — the retailer reports the product as available.
  • OUT_OF_STOCK — the retailer reports the product as unavailable.
  • UNKNOWN — Mamanida has no reliable stock signal for that product.

UNKNOWN must be preserved as unknown. It must not be interpreted, summarised or rendered as OUT_OF_STOCK.

06

Shopping handoff

Each product/storefront combination carries one public commercial state.

  • AFFILIATE — Mamanida may receive a commission when an eligible shopping handoff is used.
  • DIRECT — the shopping handoff is available without an affiliate relationship.
  • BLOCKED — Mamanida does not expose an outbound commercial destination for that product on that storefront.

MCP responses contain canonical Mamanida product URLs only. Retailer destinations and affiliate links are never returned, and an agent should hand the visitor off to the canonical Mamanida product page. Mamanida does not operate the retailer checkout.

07

Example agent workflow

User intent: “Find maternity jeans for Sweden.”

  1. list_categories(storefront: "se")
  2. identify the appropriate canonical category slug from the result
  3. search_products(storefront: "se", category: "<canonical slug>")
  4. optionally get_product for one candidate
  5. optionally compare_products across a shortlist
  6. present the results and hand off with canonical Mamanida product URLs

A guide-assisted path works the same way: get_guides for editorial and category context, then the guide's category call-to-action slug into search_products, then get_product or compare_products.

08

Errors and recovery

  • Invalid category — the error lists the valid canonical slugs; call list_categories and retry with a canonical slug.
  • Unknown product — do not fabricate a product, a price or a URL.
  • Unknown guide — do not fabricate a guide; list guides instead.
  • UNKNOWN availability — preserve it as unknown.
  • BLOCKED commercial state — do not fabricate or reconstruct a retailer destination.
  • Localized free-text search — a local phrase may not always resolve. The recommended recovery is list_categories → canonical localized category → search_products.

09

Versioning and compatibility

  • The server identity is currently mamanida-mcp 1.0.0.
  • Additive, compatible fields and capabilities may be introduced without breaking existing consumers.
  • Breaking contract changes require an explicit server version change and documentation on this page.
  • MCP protocol revision negotiation is handled by compatible clients.
  • Consumers should not depend on undocumented or internal fields.

10

Interoperability

Mamanida's production MCP server has been verified for interoperability with the official TypeScript and Python MCP SDKs over Streamable HTTP, using ordinary protocol negotiation and no Mamanida-specific client code. This is our own testing; it is not an external certification, and Mamanida makes no claim of certification by any standards body.

11

Technical contact

For integration questions, partner enquiries or verification requests, use the contact page.