{
    "id": 1081606,
    "title": "Model Context Protocol: how an assistant connects to a shop",
    "slug": "model-context-protocol",
    "type": "page",
    "url": "https://teas.co.uk/wiki/model-context-protocol/",
    "modified": "2026-11-15T08:57:37+00:00",
    "excerpt": "Model Context Protocol, usually shortened to MCP, is an open standard for connecting AI applications to outside tools and information. It gives an\u2026",
    "content_text": "Model Context Protocol, usually shortened to MCP, is an open standard for connecting AI applications to outside tools and information. It gives an assistant a consistent way to discover what a connected service offers and ask to use it.\nWhy a tea shop cares: this is the connection that lets an assistant search the teas, compare two and fill a basket for its person to check.\nAt teas.co.uk, that can mean searching the catalogue or comparing a few products while the customer stays in their conversation.\nWhat connects to what?\nThe assistant's application acts as the client, the side asking for something. The shop provides the server, the side exposing the available tools. A tool has a defined purpose, named inputs and a structured reply.\nFor example, the shop's product-search tool accepts a tea type and a caffeine filter. The reply includes matching products and their recorded details. An assistant can use those facts to explain a choice rather than relying on a remembered price.\nWhere the customer stays in charge\nFinding a tea, adding it to a basket and paying are separate steps. The shop's published boundary is that baskets are built when the person asks, and payment takes place on teas.co.uk. The assistant does not receive the customer's card details or make the payment.\nRead the current assistant shopping guide for setup and availability. Support can differ between applications; a working server does not mean every assistant has connected to it.\nMCP, APIs and structured data\nAn API is a general way for software to communicate. MCP supplies a shared connection approach for AI applications. Structured data is the labelled information either route can return.\nNone of these decides whether a tea is suitable on its own. That still depends on the product record, the customer's requirements and the accuracy of the answer built from them.\nPeople also use agentic commerce to mean shopping where software helps perform parts of the process. Always check which parts are actually available. A search tool is different from permission to spend money, and the built versus planned distinction matters here.\nFor the standard itself, see the official MCP introduction. For the information coming back from the tea shop, see the complete payload.\nRead next: Multimodal and agentic commerce, on how people ask and what an assistant may do on their behalf.",
    "contentSignals": "ai-train=yes, search=yes, ai-input=yes",
    "links": {
        "apiCatalog": "https://teas.co.uk/.well-known/api-catalog",
        "llmsTxt": "https://teas.co.uk/llms.txt",
        "mcp": "https://teas.co.uk/mcp",
        "mcpSetupGuides": "https://teas.co.uk/ai/",
        "mcpCard": "https://teas.co.uk/.well-known/mcp/server-card.json",
        "primaryAgenticRouteAuthority": "https://teas.co.uk/.well-known/teas-primary-agentic-route-authority.json"
    }
}