What is an MCP server, and does a small business need one?
An MCP server gives an AI assistant limited access to one business system. How it works, with a CRM example and the rules around it.
- 5 min
Assistants answer questions well, but most of them cannot see a company’s CRM, quotes or invoices. An MCP server is the usual way to give them that access without handing over the keys.
What an MCP server is
MCP stands for Model Context Protocol, an open standard that lets an AI assistant call tools in other software. An MCP server is the piece that sits in front of one system, such as a CRM, and offers the assistant a short list of actions. The assistant asks. The server checks the request against its rules, runs it with its own credentials and returns the result. For example, the assistant sends a request for the quotes on one contact. The server confirms that this action is on its list, runs it with its own key and returns only the fields the rule allows. AINS builds each server so that the assistant never holds the CRM key.
A CRM example
Take a sales team that works in a CRM. Its assistant gets one MCP server with a handful of actions. It can look up a contact, read the quotes attached to a deal and log a note after a call. It can draft a follow-up email for a person to review. Sending that email needs approval from a named person, and it has no action for deleting a record, so it cannot delete one, whatever it is asked. A salesperson asks in plain words which quote is open on a contact, and the answer comes from the CRM at that moment, not from the assistant’s memory.
What it may read, change and never do alone
Each rule is short, and the set is agreed with the client before anything is built.
| Action | Rule |
|---|---|
| Read a quote | Allowed. The call is logged. |
| Change a contact | Allowed and logged, with the old value kept. |
| Send an email to a client | Needs approval from a named person before it leaves. |
| Issue a refund | Allowed up to a set limit. Above it, a person approves. |
| Delete a record | Blocked. The server has no delete action. |
Where it runs and who owns it
The server runs in the client’s own accounts, with a key that has only the permissions in the table. Every call is written to a log: who asked, which action, what changed. If the client later changes assistant, vendor or agency, the server, the rules and the log stay with the client. This is the same ownership rule AINS applies to workflows, described on the n8n automation page. Switching a server off takes one step: revoke the key and the assistant loses access at once.
When a small business needs one
Often it does not need one yet. If an assistant only has to read a few documents, pasting them into the conversation is enough. A server starts to pay off when the same assistant has to work inside a system every day: looking up live CRM data, logging calls, preparing quotes. A practical test is to list the lookups and updates a person repeats in the same tool each week. A long list in one tool points to a server. A short list, or one spread over many tools, points to a plain workflow first. The next two notes cover how to connect an assistant to a CRM safely and how to choose between an agent and a fixed workflow.
What to do next
The free 30-minute review lists the repeat tasks inside your tools and says whether an MCP server, a workflow or neither fits. See the services or book the review.