Skip to content

Stockertim Dictionary · Artificial intelligence · Technology

MCP server

Also called MCP servers, Model Context Protocol server

In short

An MCP server is a program that offers tools, resources or prompt templates to AI applications using the Model Context Protocol, usually wrapping one system such as a database or an accounts package.

  • Intermediate
  • Technology
  • Checked

In detail

An MCP server sits between an AI application and a system it needs to reach. On one side it speaks the Model Context Protocol; on the other it calls the system's own interface, reads its files or queries its database. Each server typically covers one system or one family of functions, so an assistant connected to a calendar, a document store and a ticketing tool might use three servers.

What a server offers is a deliberate design. Each tool has a name, a description written for the model and a schema listing the inputs it accepts; the server checks those inputs before acting. A server for a sales database might offer "find customer" and "list open orders" but no tool that deletes records. Servers can run locally on a person's machine, often started by the host application itself, or remotely as a hosted service that many users connect to over HTTP with sign-in.

A server holds real power. It usually stores or receives the credentials for the system behind it, so its permissions decide the worst an agent can do through it. Installing a server from an unknown source is like installing any untrusted software, and a server's tool descriptions can be altered to mislead the model.

Good practice is to give each server the narrowest account and permissions its tools need, keep write tools behind approval, log every call and pin the version in use so that an update cannot change behaviour unnoticed.

Worked example

The IT lead at Marigold Housing Association reviews a proposed server for the repairs system before enabling it.

  1. Tools offered: search repairs, read one repair, create repair note, close repair.
  2. Closing a repair cannot easily be undone, so that tool is removed from the configuration.
  3. The server runs under a service account that can read repairs and add notes only.
  4. Version 1.4 is pinned, and every call is logged with its inputs and results.

The assistant can look up and annotate repairs, but closing them stays a human task, enforced by the account as well as the tool list.

In practice

Organisations keep a register of approved MCP servers, review each tool before enabling it, run servers under dedicated low-privilege accounts, and treat updates to a server like any other software change.

Watch out

  • Hiding a tool from the model is weaker than denying the permission in the system behind the server.
  • A server from an unknown publisher can read whatever its credentials allow.

Learn it properly

Official sources

Facts last checked on 9 November 2026.

Education, not advice: the Stockertim Dictionary explains what terms mean. It never recommends buying or selling anything.

English