# MCP

> Add MCP servers once, then give agents and MCP clients their tools through governed gateways

[MCP](https://modelcontextprotocol.io/specification) (Model Context Protocol) is the open standard that gives AI agents tools. An MCP server offers tools, such as "create a GitHub issue". An MCP client, such as Claude Code or Cursor, calls them.

Add an MCP server once, and every agent and MCP client can use its tools. Archestra does the hard parts for you:

- Runs servers in your cluster. Give Archestra a command or a Docker image. It deploys the server on Kubernetes, restarts it, shows its logs, and can sleep it when idle. See [Self-Hosted Servers](https://archestra.ai/docs/mcp/servers/self-hosted).
- Signs in for each person. A tool call can use the caller's own account, a shared service account, or the caller's company identity through your identity provider. OAuth tokens refresh by themselves when the provider allows it. See [Authentication](https://archestra.ai/docs/mcp/authentication).
- Keeps credentials out of clients. Archestra stores each server's credential. Clients sign in to the gateway and never see it.
- Checks who can call what. Each call must pass your access rules for the server, the tool, and the credential.
- [Logs each call](https://archestra.ai/docs/admin/logs), with the caller, the account it used, and the result.
- Gives each client only its tools. An [MCP Gateway](https://archestra.ai/docs/mcp/gateway) offers the set you choose. By default, the client sees only two tools: one to search the set, and one to run a tool it finds. This keeps the model's context small. See [Load Tools When Needed](https://archestra.ai/docs/mcp/gateway#load-tools-when-needed).

```mermaid
graph LR
    Clients["Claude Code, Cursor,<br/>your apps"] --> Gateway["MCP Gateway"]
    Agents["Archestra agents"] --> Gateway
    Gateway --> Checks["Credentials · Access rules<br/>Logs"]
    Checks --> Remote["Remote MCP servers<br/>GitHub, Jira, …"]
    Checks --> SelfHosted["Self-hosted MCP servers<br/>in your cluster"]

    class Gateway accent
    class Checks guard
    class Remote external
```

<span id="how-tools-are-reached"></span>

## Give a Client Tools

Install a server, and your coding agent can use its tools. No gateway to set up. A client set up through [Connect](https://archestra.ai/docs/get-started/connect) picks up new servers by itself.

1. Go to **MCP Registry** and find the server. Not there? [Add it](https://archestra.ai/docs/mcp/servers/adding).
2. Click **Install**, then enter your credential or sign in.
3. Ask your agent to use the new tools. Each call shows in [Logs](https://archestra.ai/docs/admin/logs).

For a team, an app, or a script that needs a fixed set of tools, [create a gateway](https://archestra.ai/docs/mcp/gateway#create-a-gateway).

<span id="environments"></span><span id="observability"></span>

## What to Know

- **Environments:** a gateway or agent reaches only the servers in its own [environment](https://archestra.ai/docs/admin/environments). The environment also sets where self-hosted servers run, and which hosts any server can reach.
- Guardrails run in the [LLM Proxy](https://archestra.ai/docs/llm-proxy), not here. They check a tool call when the model asks for it. Connect the client to both. See [Guardrails](https://archestra.ai/docs/agents/guardrails/clients).
- **Metrics and traces:** tool calls produce [MCP metrics](https://archestra.ai/docs/admin/observability/metrics/mcp) and [tool call spans](https://archestra.ai/docs/admin/observability/tracing#mcp-tool-call-spans).

## Explore

- [MCP Servers](https://archestra.ai/docs/mcp/servers.md): Add MCP servers to your organization's registry, install them, and give their tools to agents and gateways
- [MCP Gateway](https://archestra.ai/docs/mcp/gateway.md): One MCP endpoint that gives a client the tools, knowledge, subagents, and skills you choose
- [MCP Authentication](https://archestra.ai/docs/mcp/authentication.md): How clients sign in to a gateway, and how Archestra signs in to each MCP server
