MCP: the Protocol that Gives Claude Superpowers

A metaphor to start

Imagine Claude as a brilliant doctor — well-read, attentive, capable of fine analysis. By default, it works only with what you tell it in consultation. It has no access to your medical records, your test results, your history.

Now imagine you give it access to a specialised file: 74 therapeutic concepts, a network of PNI correspondences, a history of your sessions. Its value multiplies.

That is exactly what MCP does.

What is the Model Context Protocol?

MCP — Model Context Protocol — is an open standard, created by Anthropic, that allows Claude to communicate with external applications and data sources.

In plain terms: MCP is the "connection cable" between Claude and a specialised tool. It defines a common language so that Claude can:

• Call functions in an application
• Read and write data
• Use domain-specific tools

Before MCP, every integration had to be custom-built. With MCP, any tool can "speak" to Claude in a standardised way.

MCP in pictures

Here is how it works in your daily use:

You ──→ Claude (Desktop / Web / Mobile)
              │
              ├──→ AIO Connector (via MCP)
              │         │
              │         ├──→ Base of 74 symbolic concepts
              │         ├──→ Associated PNI data
              │         └──→ Brain AIO synaptic network
              │
              └──→ Your other tools (calendar, notes, etc.)

When you ask Claude a question with the AIO connector active, Claude doesn't simply respond from its general memory. It calls the AIO tool, retrieves the relevant data, and builds an enriched response.

What this changes in practice

Without MCP: Claude knows tarot in general terms — the major traditions, the common meanings. Its response is correct but generic.

With the AIO connector: Claude accesses the structured base of 74 concepts according to the All In One Method, the precise PNI correspondences, and can traverse the synaptic network between the pillars. Its response is grounded in the method.

It's the difference between a general practitioner and a specialist who knows your file.

MCP, server and client: the vocabulary

Three terms come up often:

MCP Client — This is Claude (Desktop, Web, Mobile or Claude Code). It sends the requests.

MCP Server — This is the external application (here, the AIO Évolution server). It receives the requests and executes the tools.

Tool — A specific function exposed by the server. For example: tirage_carte_du_jour, brain_aio_session, approfondir_carte.

When you see a Claude response that references a card, explores its 5 pillars and draws PNI connections — it's an MCP tool that was called behind the scenes.

Is it secure?

Yes, for two reasons:

1. You control which connectors are active. Claude Desktop shows you the list of connected MCP servers. Nothing activates without your knowledge.

2. The AIO connector transmits only the essentials. Your conversations stay in Claude. The AIO server receives only the tool requests — it does not "read" your conversation.

---

In the next article, we guide you step by step to connect AIO Évolution to your Claude in under 5 minutes.