An MCP server is a controlled bridge that lets an AI client discover and use a service’s tools and data. It is not the model, and it is not automatically safe just because it speaks MCP.

An MCP server gives an AI client a tool catalogue.

An MCP server describes capabilities an AI client can call, such as searching a knowledge base, querying a system, or creating a record. The client reads the available tools and their inputs, then requests a tool call when it is relevant to the user’s task.

The standard helps services expose capabilities in a consistent form. It does not mean every server provides the same functions or the same safety properties.

The protocol does not erase permission design.

MCP can carry powerful access.

A server may read internal documents, call production APIs, or send information to a third party. Before connecting it, identify who runs it, where it is hosted, how it authenticates, and which operations are exposed.

Do not grant a broad token because the AI use case sounds convenient. Start with the least privilege needed for one concrete workflow and review the server’s tool list.

Native integrations, browser sessions, and MCP solve different access problems.

A native integration is a product-built connection with named operations.

A browser session is useful when work must happen in the signed-in website you already use. MCP is a flexible option for a vendor’s own server or an internal system that exposes the protocol.

The right path depends on the task. The important thing is to be clear about the boundary rather than pretending all integrations work identically.

A small server with narrow tools is easier to trust.

Prefer servers that expose small, understandable operations over a catch-all tool with unlimited reach. A good tool description says what it reads or changes and takes structured inputs.

In Strawberry, an MCP connection is added deliberately. Review its operations, keep external consequences approval-gated, and remove the connection when the project that needed it ends.

Frequently asked questions