What an MCP Server Is
An MCP server is a small declaration that tells an AI model what your tool is called, what it does, what inputs it accepts and what it returns. The Model Context Protocol is a general purpose standard for connecting models to external data and tools. It was created by Anthropic and is now governed by the Linux Foundation.
The important thing to understand early is that it is usually not a rebuild. If your product already has a working endpoint, the server is mostly a description of that endpoint in a format a machine can read and act on. It is closer to a menu than to an application.
The one line version
A citation is a mention. A tool call is a job. Being cited puts your name in the answer. Being callable puts your product in it.
Citation and Tool Call Are Not the Same Win
Most AI visibility work, ours included, is about being mentioned: being readable, being quotable, ending up inside the answer instead of underneath it. That remains the foundation. But a mention and a tool call are different relationships with the model, and they pay differently.
| Citation | Tool call | |
|---|---|---|
| What the model does | Recommends you | Uses you |
| Who does the work | The user, later | Your service, immediately |
| Where it happens | Your site, after a click | Inside the conversation |
| Friction at the moment of need | Click, landing page, signup | None |
| What you give up | Nothing | Interface, branding, pricing page |
That last row is the honest cost and we will come back to it. A tool call means somebody used your product without ever seeing your interface. For a free tool trying to become a habit that is close to free distribution. For a paid product behind a signup wall it is a real decision.
Who Governs the Protocol, and Why That Matters
MCP was created by Anthropic and is now governed by the Linux Foundation. Those are two separate facts and the second one is the one that should decide whether you invest engineering time.
Adopting a protocol controlled by a single company means betting that the company's interests stay aligned with yours. Twenty years of platform history says that bet goes badly often enough to price it in. A protocol handed to a neutral foundation is a different risk profile. It does not guarantee the standard wins. It means that if it does win, the rules are not a private product decision that can be changed against you.
The governance test
A protocol one company controls is a risk. A protocol a foundation governs is a floor. Check who holds the specification before you build against any standard, not after.
What a Server Actually Contains
Strip away the tooling and a tool definition is four fields. This is the whole surface a model sees when it decides whether your product is the right one for the job in front of it.
name
A short machine readable identifier, for example convert_text_to_speech. Not your brand name, the action.
description
One or two sentences saying what the tool does and when to use it. This field does more work than everything else combined, because it is what the model reads when choosing between your tool and somebody else's.
inputs
The parameters you accept, their types, and which are required. Keep the required set as small as the job allows.
returns
What comes back, typed. A URL, a number, a structured object. The model has to be able to use the result in its next sentence.
The Description Field Does the Work
The plumbing is the easy half. The hard half is the description, because that sentence is the entire pitch and the audience is a model choosing between candidates in a fraction of a second.
Write it as if you were explaining the tool to a competent stranger with no patience. Say what it does and when it applies. Do not write marketing copy, because the model is not the buyer, it is the dispatcher. A description that says fast, powerful, industry leading audio platform tells a dispatcher nothing. A description that says turns written text into a natural sounding audio file in over one hundred languages tells it exactly when to call you.
Shipping the Smallest Useful Server
You do not expose the whole product. You expose one action, and the right one is the smallest thing a person would ask an assistant for in a single sentence.
Pick one action
Not the product, one job. The thing somebody would request in one sentence. If you cannot phrase the request in one sentence, it is the wrong first tool.
Point it at an endpoint you already have
If the action already works over HTTP, you are wrapping it, not building it. This is why the first server is usually a day of work rather than a sprint.
Write the description last and rewrite it three times
It is the highest leverage text in the whole integration. Test it by asking whether a stranger could tell when to use the tool and when not to.
Type the inputs and the return strictly
Loose types produce failed calls, and a tool that fails gets deprioritised. Required parameters should be the minimum the job needs.
Publish, then watch what gets called
The first useful signal is which arguments models actually send. That tells you what people are really asking for, which is often not what you assumed.
The Trade You Are Making
Be honest about this before you ship, because it is a real cost and it is easy to discover late. A tool call means the work happens without anybody seeing your interface, your branding or your pricing page. You are choosing usage over attention.
Where this goes wrong
If your business depends on the user landing on a page that upsells them, a tool call removes the page and keeps the cost. Decide whether the exposed action is a loss leader you are happy to give away, or gate it behind a key so usage is attributable to an account.
Who Should Not Build One Yet
If nothing in your product can be reduced to a single callable action, an MCP server is not your next move, and making sure the right crawlers can reach you comes first. Content sites, brochure sites and consultancies mostly fall here, and for them the work is still getting cited rather than getting called. The same is true if you have no way to meter usage and the exposed action costs you money on every call.
The window, though, looks like the early crawler window did. The protocol is young, governance has just settled, and in most categories nobody has shipped one. That combination does not last, and it is usually only obvious in hindsight that it was ever open.