{% extends "base.html" %}

{% block title %}{{ name }} — Documentation{% endblock %}
{% block meta_description %}How the {{ name }} MCP connector works: tools, data sources, authentication and limits.{% endblock %}

{% block content %}
<h1>{{ name }} connector</h1>
<p class="lede">An MCP server over the {{ shop_url }} catalogue — fishing,
outdoor clothing, camping and travel gear, knives and lights, hunting and sport
shooting.</p>

<span class="endpoint">{{ mcp_url }}</span>

<p>The connector is <strong>read-only</strong>. It answers questions about the
catalogue: what is available, what it costs, how the price has moved, what
customers wrote about it, and what suits a given shooting discipline. It cannot
place an order, take a payment or change anything in the shop — when a customer
has decided, it links them to the product page on {{ shop_url }}.</p>

<h2>What it is for</h2>

<p>Outdoor equipment is bought on specifications. A rod has a length, a casting
weight and an action; a sleeping bag has a comfort rating; a jacket has a
membrane and a seam construction; a scope has magnification, objective diameter
and a reticle. Which one is right depends on what the buyer actually does with
it, and that is a conversation, not a filter.</p>

<p>The connector lets someone ask in their own words — "a spinning rod for
perch up to 2,500&nbsp;₴", "a two-person tent that survives real wind", "boots
warm enough for a January sit" — and get answers grounded in the live catalogue
instead of guesses.</p>

<p>Typical use:</p>
<ul>
  <li>Find products by description, brand, category, price range or availability.</li>
  <li>Open a full product card: specifications, category path, rating.</li>
  <li>Check how a price has moved over the past months before committing.</li>
  <li>Read customer reviews, including the shop's own replies.</li>
  <li>For shooting specifically, get equipment matched to a discipline using the
  store's own selection rules.</li>
</ul>

<h2>Data</h2>

<dl class="rows">
  <div class="row"><dt>Source</dt><dd>The public catalogue of {{ shop_url }}, operated by {{ legal_entity }}.</dd></div>
  <div class="row"><dt>Coverage</dt><dd>Around 132,000 product variants across 71,000 products, 1,300+ brands and 1,000+ categories.</dd></div>
  <div class="row"><dt>Range</dt><dd>Fishing (~52k variants), clothing and footwear (~38k), camping and outdoor gear (~20k), firearms with optics and ammunition (~13k), military kit (~9k), knives and lights (~8k), gifts (~2k).</dd></div>
  <div class="row"><dt>Freshness</dt><dd>Prices and availability for the in-stock range refresh daily from the shop's product feed; the wider catalogue refreshes on a slower cycle.</dd></div>
  <div class="row"><dt>Currency</dt><dd>All prices are Ukrainian hryvnia (UAH).</dd></div>
  <div class="row"><dt>Language</dt><dd>Product names, descriptions and reviews are in Ukrainian, as published by the shop.</dd></div>
</dl>

<div class="card">
  <p><strong>The catalogue is a snapshot, not a live till.</strong> Availability
  and prices can lag behind the shop by up to a day. The server states this in
  its own instructions, so the model warns the user when the question turns on
  being current. Always confirm on {{ shop_url }} before relying on a price.</p>
</div>

<h2>Tools</h2>

<p>All tools are read-only, and every one of them is annotated as such
(<code>readOnlyHint</code>, non-destructive, idempotent, closed-world), so a
client can reason about them without calling them.</p>

{% for tool in tools %}
<div class="tool">
  <div class="tool-head">
    <span class="tool-name">{{ tool.name }}</span>
    <span class="tag">{{ tool.scope }}</span>
  </div>
  <p>{{ tool.description }}</p>
</div>
{% endfor %}

<h3>Prompts</h3>
<ul>
  {% for slug, text in prompts %}<li><code>/{{ slug }}</code> — {{ text }}</li>
  {% endfor %}
</ul>

<h3>Resources</h3>
<p>The catalogue can also be read as documents rather than called as tools:</p>
<ul>
  {% for uri, text in resources %}<li><code>{{ uri }}</code> — {{ text }}</li>
  {% endfor %}
</ul>

<h3>In-chat product card</h3>
<p>The server ships an MCP Apps UI resource, <code>ui://ibis/product-card</code>,
which renders a product inside the conversation with its photos and price, and
can call back for the price history. Clients that do not support MCP Apps fall
back to plain structured content and lose nothing but the layout.</p>

<h2>Authentication</h2>

<p><strong>No sign-in required.</strong> The connector publishes a product
catalogue — the same information anyone can read on the website — so there is
no account to create and no key to paste. Connect it and ask.</p>

<p>Callers get read-only scopes (<code>catalog:read</code>,
<code>prices:read</code>, <code>reviews:read</code>, <code>images:read</code>)
and a per-address request limit. There is no write scope to grant: nothing in
the server can change anything.</p>

<p>Because no sign-in is needed, the server does not advertise an authorization
server: the OAuth discovery documents and <code>/oauth/*</code> endpoints
answer 404 in this configuration, so a client connects directly rather than
being sent through a consent flow it does not need. An OAuth&nbsp;2.1
implementation exists behind that switch — protected-resource metadata
(RFC&nbsp;9728), authorization-server metadata (RFC&nbsp;8414), Dynamic Client
Registration (RFC&nbsp;7591), PKCE&nbsp;S256, refresh tokens, resource
indicators and revocation (RFC&nbsp;7009) — and will be turned on if the
connector ever carries anything belonging to an individual user. An
organisation that wants a named credential with its own rate limit today can
ask for a static API key.</p>

<h3 id="enterprise">Enterprise setup</h3>

<p>Administrators rolling this out for an organisation need nothing beyond the
endpoint above: there is no sign-in, so there is no per-tenant key to
provision, no OAuth client to register and no allowlist to maintain.</p>

<p>Points a review usually turns on:</p>
<ul>
  <li><strong>No user data leaves your organisation.</strong> The connector
  reads a public product catalogue. It receives the search terms a user types
  and nothing else — no account identity, no conversation history, no files.</li>
  <li><strong>Nothing can be written.</strong> Every tool is read-only; no write
  scope is granted to directory clients.</li>
  <li><strong>Requests are rate limited</strong> per credential, with the limit
  and a retry hint returned in the error, so a misbehaving client degrades
  rather than affecting others.</li>
  <li><strong>Retention</strong> of access logs is described in the
  <a href="{{ privacy_url }}">privacy policy</a>.</li>
</ul>

<p>If your organisation needs a dedicated credential, a different rate limit or
a signed agreement, write to
<a href="mailto:{{ support_email }}">{{ support_email }}</a>.</p>

<h2>Limits</h2>
<ul>
  <li>A single search returns at most 50 items; the total match count comes back
  with it so the model can suggest narrowing rather than paging blindly.</li>
  <li>Image URLs are signed and expire after about an hour.</li>
  <li>Price history defaults to 180 days.</li>
</ul>

<h2>Support</h2>
<p>Questions, bug reports and access requests:
<a href="{{ support_url }}">support</a>.</p>
{% endblock %}