---
title: 'Cratis Arc MCP: commands and queries as agent tools'
editUrl: https://github.com/Cratis/Arc/edit/main/Documentation/backend/csharp/mcp/index.md
description: Cratis Arc MCP turns the commands and queries you already wrote into Model Context Protocol tools that keep Arc validation, authorization and tenancy intact.
lastUpdated: 2026-11-14T00:00:00.000Z
---


Cratis Arc MCP is the `Cratis.Arc.Mcp` package. It serves a [Model Context Protocol](https://modelcontextprotocol.io) endpoint from your Arc application, so an AI agent can call the commands and queries you choose as tools.

## Why use it

A hand-written MCP server is a second application. It needs its own input checks, its own authorization and its own way to find the tenant, and each one can drift from the real application.

With Arc MCP there is no second code path. A tool call runs the same command or query pipeline as a REST call:

- Command validation runs, and its results come back to the agent as structured validation results.
- Authorization runs, including `[RequiresScope]` and any `IMcpToolAuthorizer` you register.
- The caller is the verified caller the [capability gate](/arc/backend/csharp/capability-hosting/) admitted, so tenancy and identity come from the same place as for REST.

## What stays under your control

- **Opt-in.** Nothing is exposed unless you declare it with `Expose`, `ExposeQuery` or `[ExposeOverMcp]`.
- **Fixed tool set (the tool catalog).** Tool names, descriptions and scopes are checked at startup. A tool that is invalid, has no description, requires no scope, or writes without a write scope stops the application from starting.
- **Scoped visibility.** A caller only sees, and can only call, the tools its scopes allow.
- **No approval-required commands.** A command that requires approval is never exposed.
- **Stateless.** Each request is one call. There are no MCP sessions.

## How it fits together

1. The endpoint is served only on the capabilities [endpoint group](/arc/backend/csharp/endpoint-groups/) port, behind capability hosting.
2. Callers authenticate with a personal access token (PAT) by default (the `PatOnly` profile). `OAuthOnly` and `Combined` profiles accept OAuth grants verified by your installation. Arc does not issue tokens.
3. Browser-based clients and hosted connectors need extra setup; see [Connect clients](/arc/backend/csharp/mcp/connect-clients/).

## Where to go next

| I want to | Page |
| --- | --- |
| See it work in ten minutes | [Quick start](/arc/backend/csharp/mcp/quick-start/) |
| Decide what to expose | [Expose a command or query safely](/arc/backend/csharp/mcp/expose-safely/) |
| Understand who may call what | [Authorization](/arc/backend/csharp/mcp/authorization/) |
| Gate the endpoint | [Gate the endpoint](/arc/backend/csharp/mcp/gating-the-endpoint/) |
| Declare the agent-visible allowlist in one file | Capability manifest |
| Name tools and choose scopes | [Scopes and descriptions](/arc/backend/csharp/mcp/scopes-and-descriptions/) |
| Connect Claude, VS Code or another client | [Connect clients](/arc/backend/csharp/mcp/connect-clients/) |
| Debug with a visual client | [Test with MCP Inspector](/arc/backend/csharp/mcp/test-with-inspector/) |
| See which agent did what | [Audit log](/arc/backend/csharp/mcp/audit-log/) |
| Fix an error | [Troubleshooting](/arc/backend/csharp/mcp/troubleshooting/) |
| Look up an option | [Options reference](/arc/backend/csharp/mcp/reference/) |

[Tool sources and authorizers](/arc/backend/csharp/mcp/advanced/) covers curated tool sources, authorizers, exclusive tools, session authority and the Origin check in depth.
