Does a small business need an MCP server?
Some do, most don't yet. The test is simple: could a customer ask an assistant for what you sell in one sentence, and could a system give them the answer without a person stepping in?
"Book me a car service in Melton on Thursday morning" passes. So does "what's the price for 500 printed leaflets, delivered by Friday?". "Design us a new office" doesn't, because the real work starts with a conversation. If most of your enquiries look like the first two, an MCP server is worth a serious look.
Which small businesses get the most from one?
The ones with a clear, repeatable offer and a system that already runs it.
- Appointment businesses: garages, salons, clinics, tutors and trades with set slots.
- Hire businesses: vans, equipment, venues and rooms, where availability is the question.
- Retailers and makers with stock, sizes and prices that change.
- B2B suppliers whose customers reorder the same things.
- Any business with a quote that follows clear rules: size, quantity, distance or date.
When is it too early?
Hold off if any of these sound like you. There's better work to do first.
- Every job is bespoke, and the price only exists after a site visit.
- Bookings live in a diary or an inbox, with no system behind them.
- Assistants don't name you yet when buyers ask for what you do.
- Your website doesn't show prices, availability or how to start.
What should you do before an MCP server?
Get recommended first. A connector lets an assistant act once it has picked you, but it doesn't make the assistant pick you.
That means clear facts on your site, a "from" price where you can, crawler access, consistent listings and reviews. Alongside that, make your existing booking or enquiry page easy for AI agents to use: plain HTML, clear steps and no CAPTCHA in the way. Some assistants can already fill in a web form for a customer, so that page does a lot of the job on its own.
What does a small business MCP server usually do?
Two or three things, done well. Small is better: every action you add is one more thing to test and keep safe.
The usual starting pair is one action that looks something up, such as prices or availability, and one that does something, such as booking a slot. Looking up is low risk and useful on day one. Booking comes with a confirmation step, so nothing happens without the customer's say-so.
How do you decide, step by step?
Seven questions, in order. If you stall at one, that's the work to do first.
- List your five most common customer requests, in the words customers use.
- Mark the ones a system could answer without a person stepping in.
- Check which system holds the answer today: a booking tool, a stock list, a price sheet or nothing.
- Ask whether that system has an API, or whether the booking or ordering layer needs building first.
- Run your buyers' questions in ChatGPT and Claude, and check whether you're named.
- Pick one or two actions to start with, and decide what needs the customer's confirmation.
- Agree how you'll measure it: bookings, quotes or orders that come through the connector.
What are the risks, and how are they handled?
The risks are the ones you'd expect: a wrong price, a double booking or someone seeing what they shouldn't. Each one has a standard fix.
You choose which actions exist, and nothing else is reachable. Customers sign in before anything personal is shared. Anything that books or charges needs their confirmation. Spend limits cap what one request can do, and every action is logged. Our MCP guide covers each of these in more detail.
What does an MCP server cost a small business?
It depends on what it needs to do, and whether the booking or ordering layer already exists. Wrapping a booking tool that has an API is a much smaller job than building the booking system too.
We usually price it as an add-on to SEO or a website rebuild, because being bookable works best when you're already being recommended. You get a fixed price after a short call, before any work starts.