Shopping MCP server for luxury boutiques

What the server is, and what it is not

It is a Model Context Protocol (MCP) server that you reach over the internet. It reads the same shelves the site shows. Those come from each boutique's own register, its point of sale, so the sizes and stock are the shop's own. An agent and a person asking the same thing get the same answer.

It is not:

• A checkout. No tool adds to a bag, holds a piece or takes a payment.
• A search of the whole web. It reads only the boutiques that sell on within, never mass market stores.
• A style adviser. It says what is on the shelf, not what to wear.
• A package to install. Nothing runs on your computer; you connect to a web address.
• A way into anyone's account. It never sees a shopper's saves, bag or orders.

The endpoint

Address

https://shopwithin.co/mcp

Protocol

Model Context Protocol over Streamable HTTP, stateless, JSON responses. It speaks the protocol versions 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05 and 2024-10-07.

Requests

One JSON-RPC message per POST. Send accept: application/json, text/event-stream; a request that does not accept both gets a 406. There is no session, so you can call tools/list or tools/call without an initialize first.

Other methods

A plain GET answers a short JSON description: the name, the version, the endpoint and the tool names. DELETE answers 405, because there is no session to end.

Browsers

CORS is open to every origin, so code in a web page can call it. Answers are never cached (cache-control: no-store).

Server card

https://shopwithin.co/mcp/server-card, in the MCP server card format: the name, the version, the endpoint and the protocol versions, for apps and lists that look a server up before they connect.

Account and price

No account, no key, free.

Resources

within://about (one paragraph on within and its tools), within://guides (the journal's city and field guides, one per line) and within://guides/{slug} (one guide in full).

Limits and rate limits

• Each address gets a burst of 60 requests, then one a second as the burst refills. All callers together get a burst of 1,200, then 20 a second.
• Past the limit the answer is HTTP 429 with {"error":"rate_limited"} and retry-after: 30.
• A page of results holds 1 to 24 pieces, 12 if you do not say. offset runs to 480, so one search reaches about 500 pieces.
• A query is 200 characters at most. brands, categories, sizes and boutiques take up to 10 values each.
• visual_search takes JPEG, PNG or WebP under 1.5 MB. A linked image must arrive within 8 seconds, and private or local addresses are refused.
• Descriptions are cut at 1,200 characters. Facets show the top 8 values of each kind.
• Prices are never converted. Each piece says its currency.
• Stock is as fresh as the boutique's last sync, and every piece says when that was.

The eight tools

Every tool is marked read only and safe to repeat, and none reaches outside within. Every answer comes twice: a short text an assistant can quote whole, and structuredContent with the fields below. Most tools answer with pieces, and a piece always has these fields:

id, boutique_domain

together, the piece's name in every other tool

title, brand, category

as the boutique lists them

price, price_max, currency, price_label

price_max only when sizes are priced differently; price_label reads like CAD 1,500

sizes_in_stock, units_in_stock

the sizes on the shelf now, and how many pieces in all

boutique

domain, name, neighbourhood, city and its page on within

collect_in_store, delivery

whether the piece can be picked up at the counter or delivered

image, url

the main photograph, and the shopwithin.co page where the shopper buys

price_drop

the earlier price and the day it changed, when the piece is marked down

condition

new, pre-owned, lightly-used, worn-once or vintage, or empty when the shop does not say

stock_checked_at

when within last read the boutique's register for this piece

How a shopper buys a piece the agent found

1. The agent searches and shows the pieces, each with its url on shopwithin.co.
2. The shopper opens that page, which reads the sizes and stock again, fresh.
3. They pick a size and tap Buy.
4. within hands the bag to the boutique's own checkout. Every boutique on within today sells through its own online shop, so the shopper pays the boutique there, at the boutique's own price.
5. The boutique ships the piece or holds it at the counter for pickup. Where it ships, what shipping costs and when a piece is ready to collect all show at checkout.

Nothing is reserved or charged through the tools: every piece carries its shopwithin.co page, and the boutique's own checkout does the rest. This is the finding half of agentic commerce. The paying half stays between the shopper and the boutique, and the boutique keeps its customer.

What it never does

It never takes a payment, holds a card, or places an order. It never stores a photograph: an image sent to visual search is matched in memory and discarded. It never invents a size, a price or a stock level; when nothing matches, it says so.

• It never shows a test shop or a demo showroom, only boutiques that sell on within.
• It never writes anything. No tool changes a bag, a save, a price or a shelf.
• It never asks for a name, an email or a login.
• When a city has no boutique yet, it says so and names the cities that do.

How to connect

From an assistant app

Open its settings, find connectors, add a custom connector, and paste https://shopwithin.co/mcp. No key or account is needed. If it asks for a name, use within.

From a command line

Add a remote MCP server named within, transport HTTP, at the endpoint. Most command line agents take it in one line of this shape:

<your-agent> mcp add --transport http within https://shopwithin.co/mcp

From a code editor

Add it to the editor's MCP settings file. Most editors read this shape:

{
  "mcpServers": {
    "within": {
      "url": "https://shopwithin.co/mcp"
    }
  }
}

Some editors also want a type of http beside the url. The server answers the same way.

From your own code

Any MCP client library connects the same way, or you can send JSON-RPC yourself. To list the tools:

curl -s https://shopwithin.co/mcp \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

To call one:

curl -s https://shopwithin.co/mcp \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{
        "name":"search_pieces",
        "arguments":{"query":"black leather loafers under $600","sizes":["42"],"limit":3}}}'

In an app that shows widgets

Search, piece and shelf answers come with a widget, ui://widget/within-shelf.html, that shows the results as a shelf of photographs, each with its price, its sizes, its shop and a link to buy on within.

The pages an agent can cite

The tools read the shelves. These pages answer the rest, one kind of page per line, each at its own address.

• Designers, for a reader anywhere: one page per designer, with the boutiques that hold it today, the count, the prices and how it reaches you. Every designer has one at /designers/{designer-slug}, and the A to Z is at /designers.
• Sneakers: every pair on the shelves, then one page per line and one per model, new and pre owned, for example /shop/toronto/sneakers/jordan-1.
• Winter jackets and parkas: every winter coat on the shelves, warmest first by each maker's own rating, with the makers side by side.
• Comparisons: SSENSE, Farfetch and other designer sites side by side for Canada and the US (duty, returns and who takes your card), from each site's own pages: /compare/ssense-alternatives, /compare/farfetch-alternatives and /compare/ssense-vs-farfetch.
• Cities: one page per city the boutiques deliver to, with the designers people there look for and the pieces in stock, for example /city/new-york.
• Prices: what each designer costs on the shelves today, with the range, the middle price and the count, for example /guides/prices/chrome-hearts.
• Sale: designer pieces marked down today, across every boutique.
• Everything else: art, books, candles and objects for the home.
• Free tools: every tool on one page, each free, in the browser, with no download.
• Sizes: size charts and a converter for rings, shoes, clothes, suits, belts and hats, and one chart per designer, each with its source and the day it was read.
• Duty: what a piece costs at the door in the US, Canada or the UK, each line with its official source.
• Is it legit: whether a shop or a resale site is legit, read from its own policy pages with the day they were read: returns, duty and what it checks.
• How to spot a fake: how to check a piece before you pay, starting with who sold it, from the maker's own words.
• Sizing notes: whether a designer runs big or small, model by model, from its own size pages.
• Why it costs what it does: why a designer's pieces cost what they do, with the prices on the shelves.
• The boutiques: one note per boutique: its street, its hours, what it holds and how it sells.
• Shopping streets and cities: the shops on a street or in a neighbourhood, with addresses and hours.
• What to wear: what to wear to an event or a city, from the dress code it prints and the weather on the day.

Boutiques

Your register is the listing. When your shop is on within, your shelf is readable from any assistant or app that connects, with your name on every piece. Invite your boutique.