What is MCP (Model Context Protocol)? A plain-English explainer for Australian small business

The plain-English mental model

Imagine your business apps (Shopify, Xero, Slack, Gmail) as a row of houses on a street. Before MCP, every AI tool that wanted to visit one of those houses needed its own special key, cut individually for each house. Custom work, slow, fragile.

MCP standardised the lock. Now every AI tool uses the same key shape. Every house can install the same kind of door. Visit happens. Less plumbing, more talking.

That’s MCP. A standard for how AI tools and your business apps talk to each other.

Why this matters for your business

The practical impact: AI tools are now genuinely useful for real work, not just chat.

Before MCP (2024 and earlier):

• AI could only do things you copy-pasted into the chat
• Connecting AI to your tools required custom development
• Each tool was its own project

After MCP (mid-2026):

• AI can read your Shopify inventory directly
• AI can post to your Slack workspace
• AI can read and reply to your Gmail
• AI can update your Xero categorisation
• AI can book appointments in your Cliniko / NOOKAL
• Setup for each: 5-15 minutes

The difference is “AI that helps me think about my business” vs “AI that does parts of my business”.

The specific things MCP unlocks

For an Australian SMB owner, the concrete wins:

Operations:

• AI reads your Shopify inventory each night, flags stockouts (our AI Inventory Watch service)
• AI categorises your Xero transactions daily (our AI Bookkeeping Assist service)
• AI watches your Stripe payouts and flags anomalies

Customer-facing:

• AI answers customer questions on your website (using your Notion knowledge base as context)
• AI replies to inbound emails with full context from your CRM
• AI books appointments directly into your calendar

Internal:

• AI summarises your Slack channels each morning
• AI drafts the weekly team update from your Linear tickets
• AI generates monthly client reports from your billing data

All possible because MCP standardised how AI tools plug into other tools.

Which MCP servers exist (May 2026)

A non-exhaustive list of the ones useful to Australian SMBs:

The list grows weekly. New ones we expect in 2026: MYOB, NOOKAL deeper integration, ServiceM8, Cin7, Xero+ deeper writes.

If a tool you use doesn’t have an MCP server yet, you can either wait (most popular tools get one within 6 months of demand showing) or have someone build a custom one. We do this for clients on Quick Start engagements.

How to use MCP (the non-technical version)

You don’t directly install MCP servers; your AI tool does. The flow:

1. You decide you want AI to work with [tool X] (e.g. Xero)
2. You search for “[Tool X] MCP server” or check your AI tool’s marketplace
3. You install it via your AI tool’s interface (Claude Code, ChatGPT, etc.)
4. You authenticate (typically OAuth: log in to the tool, click “allow”)
5. You start using AI with that tool

For Claude Code specifically: claude mcp add <server> runs the install. Setup typically 5-15 minutes per server.

For ChatGPT: it’s via the “Connectors” or “Custom GPT Actions” interface, slightly less developer-y.

What MCP doesn’t do

• MCP isn’t AI itself. It’s the standardised connector. The AI still does the thinking.
• MCP doesn’t bypass tool permissions. Each MCP server respects the underlying tool’s auth model. Read-only Shopify access via MCP means the AI can read; it can’t write unless you grant that.
• MCP isn’t magic. It still requires the AI to know what to do. A well-crafted prompt + good MCP servers = useful AI agent. Bad prompt + good MCP = same bad results, just connected.

Why “you don’t need to learn MCP technically”

Most explainer content makes MCP sound complicated. For a non-developer, it isn’t. The technical layer (JSON-RPC over stdio or HTTP, schema discovery, tool calling) is plumbing your AI tool handles.

What you need to know:

• MCP exists
• Most of your business tools have MCP servers
• Setup is fast (5-15 minutes per connection)
• It’s what makes AI useful for real work, not just chat

That’s enough. The technical depth is for your AI consultant or developer.

Real example: how our nightly inventory agent uses MCP

The nightly inventory agent case study we built uses MCP for two things:

1. Shopify MCP server: reads the client’s inventory state, products, recent orders
2. Slack webhook (not MCP, simpler API): posts the digest

Without MCP, that build would have required custom Shopify API integration. With MCP, the agent script is mostly: “Connect to Shopify MCP, run these queries, summarise, post.” 1 build day instead of 5.

That’s the real value: MCP makes the “let’s connect AI to our business” project something you can scope in days instead of weeks.

What’s next

• Model Context Protocol for the glossary-style technical definition.
• Claude Code MCP servers for the Australian business stack for the technical setup guide.
• Building your first Claude Code agent for a real walkthrough using MCP.

If you want help wiring AI into your Australian business tools, our Quick Start build at $497 AUD includes one MCP-connected workflow as part of the scope.