What an MCP connector is, in plain terms

At Samarkand Bakery, the owner runs the day from his phone by typing things like "what's on for Sunday?" or "close Saturday except plov and karak" into an AI assistant. The answer comes from the bakery's own ordering system, not from a web search. The piece that makes that possible is an MCP connector.

MCP stands for Model Context Protocol. The official specification describes it as an open protocol for connecting AI applications to outside data and tools. It has three parts. The host is the AI app, such as Claude or ChatGPT. The client is the connector inside that app. The server is the service that provides the data and the actions. For an owner, the server is the part that gets built for you: a small program beside your website or ordering system that answers the assistant's questions and carries out only what it is allowed to.

The actions a server offers are called tools, and tools are model-controlled: the AI decides when to call them.

Reading versus changing: what a connector can do

Every tool either reads something or changes something. That is the first line to draw when you plan a connector.

A ledger with a magnifying glass for reading and a pencil for changing, linked to a laptop, showing the two kinds of MCP connector tool

Samarkand Bakery is Sherzod's own family bakery in Tetouan, Morocco, so we were the owner and the builder at once. Its connector does both. The owner can ask how many orders there are for a day and what to bake, for a sales report for any period, which items sell best and worst, what a particular customer has bought, how many people visited the website and what they searched on Google, what each product costs to make and its margin, and about reviews, promo codes and loyalty points.

It can also change things: product prices, names and descriptions, order status and notes, closing or reopening a day, ingredient prices, promo codes, loyalty points, approving or replying to reviews, blog posts, and recording sales at an event stall. A message such as "I'm at the stall: 2 meat samsas, client Abu Musa" becomes a recorded sale.

Read-only is a perfectly good place to start. Our Shopify owner connector is read-only and sees no customer emails, phones or addresses.

Who approves a change: the chat app or your own server

The specification says "Hosts must obtain explicit user consent before invoking any tool". But as Rillor's report on MCP access control points out, the specification also says MCP itself "cannot enforce" these principles at the protocol level. It is left to the apps and to whoever builds the server.

A preview card, a padlock and a one-time key in front of a server box, showing a change approved by the server rather than the chat app

In Claude, admins can set each tool to Always allow, Needs approval or Blocked. OpenAI says ChatGPT may ask for confirmation depending on app permissions, the action's context and its potential impact, and that the Allow all actions setting means supported actions may run without another confirmation.

We learned what that means in testing at Samarkand: ChatGPT changed a product price on its first call without asking. The fix is to enforce approval on your own server. Every change shows a preview first, the owner says yes, and the server refuses the change unless it carries the one-time code from that preview. The AI cannot skip the step, because the step is not the AI's to skip.

What should stay in the admin panel

The rule we agreed for Samarkand is simple: everyday work happens in the chat, and anything that could wipe the business needs the admin panel itself. If someone used an open laptop with Claude connected, they must not be able to destroy the shop.

Each kind of change then gets limits that the server enforces, not the AI's good behaviour:

  • A new price only between half and double the current one.
  • Deleting only cancelled orders, and they can be restored.
  • At most 30 changes an hour.
  • A Telegram message to the owner for every change made through an assistant.
  • The old values kept in a history log.

Some things are never possible from a chat at all: deleting customers, products or active orders, refunds, and changing settings, passwords or payment keys. Bulk changes belong in the admin panel too. A chat is good for "close Saturday". It is the wrong place to reprice the whole menu.

How sign-in works, and how to switch a connector off

Authorisation is optional in the MCP specification. Where it is used over the web, the server acts as an OAuth 2.1 resource server. In plain words: ask your builder how people sign in, because a connector without sign-in is open to anyone who has its address.

Anthropic describes the usual flow for Claude custom connectors: you sign in and grant specific permissions, and Claude works with the service without ever seeing your actual password. The same page warns that a shared credential, such as an API key, gives everyone who uses the connector that credential's access. Each person should sign in as themselves.

Custom connectors are available in Claude on Free, Pro, Max, Ultra, Team and Enterprise plans, and Free users are limited to one. On Team plans only Owners and Primary Owners can add one. OpenAI lists custom MCP server connections for ChatGPT Business and Enterprise/Edu on the web.

At Samarkand, a staff sign-in expires after 7 days. To switch the connector off, the owner opens the Connectors section of Claude's or ChatGPT's settings and presses Disconnect. If a phone or laptop goes missing, changing the admin password and revoking the connector sign-ins cuts every connection at once, and the activity log shows what was done.

What happens when a customer orders through the chat

The website order form at Samarkand stays, and most customers still use it. Ordering through an assistant is an extra way in. A customer can ask questions first, in English, French or Arabic: what feeds five people, which days plov is available, what has nuts in it. The assistant checks dates and prices against the bakery's own rules before anything is ordered.

A bakery box, a phone with chat bubbles, a calendar and a cash tray, showing a customer pre-order placed through an MCP connector

Before an order is placed, the assistant has to show the items, total, date and time, and the customer has to say yes. The server requires the one-time code from that preview, so the AI cannot place an order on its own. The order then goes through the website's own ordering system, exactly like a website order: an instant Telegram alert, a confirmation email if the customer gave one, loyalty points added, and the order waiting as pending in the admin panel. The bakery confirms with the customer on WhatsApp before baking. Payment is cash at collection, or a pay link for that exact order on the bakery's own PayPal checkout, straight into the bakery's account, with no commission taken on the order.

Before launch it was tested with 121 automated checks on a copy of the site, then checked again by staff on the live site. Because the connector uses the website's own rules rather than a copy of them, the two cannot drift apart. An item not on the menu is refused, and the assistant is told which items it did not recognise. A date the bakery cannot do is refused with the reason, and the assistant checks availability for one that works. Prices only come from the bakery's own data. Customer tools see only that customer's orders, and one connection can place at most 5 orders an hour.

One more lesson: the chat app decides how an answer looks. Asked for the menu, ChatGPT once added food photos from a web search, showing other bakeries' food under the bakery's names. Only the connector's own cards inside the chat guarantee the real photos and prices.

Your data, your contracts and the rules that still apply

A connector does not change your existing duties. If you sell food, the FSA says allergen information for food sold online must be available free before the purchase is concluded and at the moment of delivery. At Samarkand every product page lists its allergens, and the assistant reads that same list when a customer asks. Ask any builder where your connector gets its allergen answers.

If customer personal data passes to an AI service, the ICO says the roles of each party should be set out in agreements drafted before any sharing takes place, with a written contract between controller and processor. A data protection impact assessment is not required just because you use AI; it is required where processing is likely to result in a high risk to people. We do not give legal advice, so read the ICO pages or ask your own adviser. The simplest protection is to keep customer contact details out of what the assistant can see unless a tool truly needs them.

When you do not need a custom connector

If you run a Shopify store and mainly want to ask questions about it, our ready-made connector will do. The owner connector takes about 2 working days to set up and the shopping connector about a week. You can read what each includes on our Shopify connector page.

If your real problem is enquiries sitting in an inbox, a better form or a small automation may solve it for less, and we will say so. And if your admin panel is already a tangle of workarounds, sort the system first. A connector can only be as reliable as the rules behind it. Samarkand works because the assistant uses the same ordering rules as the website's own system.

Questions to ask before you have one built

Take these to any builder, us included:

  1. Which tools read and which change? Ask for the list in writing.
  2. Is approval enforced by the server, or left to the chat app?
  3. What is never possible from a chat, whatever anyone types?
  4. What limits apply to each change, such as price ranges and changes per hour?
  5. Who is told when a change is made, and where are the old values kept?
  6. How does each person sign in, when does that expire, and is any shared key involved?
  7. How do I cut every connection at once if a phone goes missing?
  8. Which Claude or ChatGPT plan do my staff and customers need?
  9. What was tested on a copy of the site before customers use it?
  10. Will customers see my own photos and prices, or whatever the app finds?

You can see how these answers played out in practice in the Samarkand Bakery case study, and more about what we build on our connectors page.

Write two short lists: the questions you ask about your business most weeks, and the changes you make most often. Mark each change as everyday or dangerous. That one sheet of paper decides what a connector should read, what it may change and what stays in the admin panel.

Sources

Thinking about a connector for your business?

Bring your list of weekly questions and everyday changes to a free 30-minute call with Sherzod. He will tell you plainly whether a custom connector, a ready-made Shopify connector or a smaller tool fits how you work.

Book a free 30-minute call