{"id":1317,"date":"2026-10-05T16:55:14","date_gmt":"2026-10-05T13:55:14","guid":{"rendered":"https:\/\/fluidcrm.io\/blog\/?p=1317"},"modified":"2026-10-06T20:34:13","modified_gmt":"2026-10-06T17:34:13","slug":"what-is-an-mcp-server","status":"publish","type":"post","link":"https:\/\/fluidcrm.io\/blog\/what-is-an-mcp-server\/","title":{"rendered":"What Is an MCP Server? Explained for Non-Developers"},"content":{"rendered":"\n

You keep seeing “MCP server” in product updates, and every page that explains it seems to be written for people who code. You don’t want to build one, you want to know what it is and whether it is any use to you.<\/p>\n\n\n\n

An MCP server is a small piece of software that lets an AI assistant, such as Claude or ChatGPT, use another app for you. It gives the assistant a fixed list of actions it may take in that app, like “find a contact” or “add a task”. The assistant can do those things and nothing else.<\/strong><\/p>\n\n\n\n

<\/span>What An MCP Server Is, In Plain Words<\/span><\/h2>\n\n\n\n

The letters are short for Model Context Protocol<\/a>. A protocol is an agreed way for two pieces of software to talk to each other.<\/p>\n\n\n\n

An AI assistant is smart, but it can’t see your inbox, your calendar or your customer list. An MCP server is what lets it reach one of those apps.<\/p>\n\n\n\n

Here is the best way I know to picture it. The server hands the assistant a menu. Every item on the menu is one action, and the assistant can only order what is printed there.<\/p>\n\n\n\n

A server can share two other things as well. One is information for the assistant to read, and the other is ready-made instructions for common jobs. The actions are the part you will notice most.<\/p>\n\n\n\n

There are three parts, and you only ever talk to the first one.<\/p>\n\n\n\n

Part<\/th>What it is<\/th>Example<\/th><\/tr><\/thead>
The assistant<\/td>The AI you type to<\/td>Claude or ChatGPT<\/td><\/tr>
The MCP server<\/td>The menu of allowed actions for one app<\/td>The server for your CRM<\/td><\/tr>
The app<\/td>Where your real data lives<\/td>Your CRM, the app where a team keeps its customers and deals<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Anthropic, the company behind Claude, published MCP in November 2024. It now sits with a foundation that several big tech companies support, so no single company owns it.<\/p>\n\n\n\n

<\/span>What An MCP Server Does, Shown With Fluid CRM<\/span><\/h2>\n\n\n\n

We built Fluid CRM<\/a>, a simple CRM for small teams that sell to other businesses, and we built an MCP server for it. It shows your deals as cards on a board, and each column is a stage a deal moves through. So I’ll use ours to show what one really does.<\/p>\n\n\n\n

The Fluid CRM server has 21 actions on its menu. Developers call these tools. 8 of them can read your data and 13 can create or change it for you.<\/p>\n\n\n\n

You never see the tools. You type a normal sentence, and the assistant picks the right one.<\/p>\n\n\n\n

What you type to Claude<\/th>What the server lets Claude do<\/th>What happens in Fluid CRM<\/th><\/tr><\/thead>
“Which reminders are due this week?”<\/td>Read your reminders<\/td>Nothing changes. You get a list<\/td><\/tr>
“How is my pipeline doing?”<\/td>Read a summary of your deals<\/td>Nothing changes. You get the numbers<\/td><\/tr>
“Add Tom Russell from Northwind as a contact”<\/td>Create a contact<\/td>A new contact appears<\/td><\/tr>
“Move the Northwind deal to Negotiation”<\/td>Update a deal<\/td>The card moves to the new stage<\/td><\/tr>
“Add these 12 companies from my list”<\/td>Create companies in bulk<\/td>Twelve new companies appear<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
\"Claude<\/figure>\n\n\n\n

There is no delete on that menu. We left it out on purpose, so Claude can add to your pipeline and change it, and it can never wipe a deal. <\/p>\n\n\n\n

The people who build the server decide what goes on the menu, and that choice decides how much can go wrong.<\/p>\n\n\n\n

\"Fluid<\/figure>\n\n\n\n

<\/span>MCP Server vs API: What Is The Difference<\/span><\/h2>\n\n\n\n

You may have heard that apps already talk to each other through something called an API. They do, and an MCP server usually sits on top of one.<\/p>\n\n\n\n

The difference is who it is made for. An API is made for a developer, who writes code that says exactly what to do, step by step. An MCP server is made for an AI assistant, which reads the menu and works out the steps from your sentence.<\/p>\n\n\n\n

<\/th>API<\/th>MCP server<\/th><\/tr><\/thead>
Who uses it<\/td>A developer writing code<\/td>An AI assistant<\/td><\/tr>
Who decides the steps<\/td>The developer, in advance<\/td>The assistant, from what you ask<\/td><\/tr>
What you need<\/td>Coding skills<\/td>A sentence<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Back to the menu. With an API, a developer has to write down the whole order in advance, dish by dish. With an MCP server, you say what you feel like and the assistant picks from the menu for you.<\/p>\n\n\n\n

Fluid CRM has both. Developers use the API to connect it to other tools, and everyone else can use the MCP server from a chat window.<\/p>\n\n\n\n

<\/span>How To Use An MCP Server Without Writing Code<\/span><\/h2>\n\n\n\n

You don’t install anything, and you don’t build anything. You switch on a server that the app’s maker has already built.<\/p>\n\n\n\n

In Claude these are called connectors. You open the connector list, search for the app and sign in to it. Fluid CRM also has its own setup page under Integrations, then MCP, which walks you through it. What the assistant can do once it is connected is on our AI CRM<\/a> page. I compare the connectors worth adding for sales in my post on the best Claude connectors for sales teams<\/a>.<\/p>\n\n\n\n

\"Fluid<\/figure>\n\n\n\n

ChatGPT supports MCP as well and calls them apps. The step-by-step version, with screenshots, is in my guide to the best CRMs for Claude<\/a>.<\/p>\n\n\n\n

Make your first request one that only looks things up, such as “How many open deals do I have?”<\/em> Once the answers look right, let it make a small change. Does the thought of an assistant typing into your CRM make you a little nervous?<\/p>\n\n\n\n

<\/span>Not Every MCP Server Is Built The Same<\/span><\/h2>\n\n\n\n

Each company writes its own list of allowed actions, so two MCP servers can behave very differently. I read three of them line by line this month.<\/p>\n\n\n\n