Skip to content

Cratis Arc MCP: commands and queries as agent tools

Cratis Arc MCP is the Cratis.Arc.Mcp package. It serves a Model Context Protocol endpoint from your Arc application, so an AI agent can call the commands and queries you choose as tools.

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 admitted, so tenancy and identity come from the same place as for REST.
  • 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.
  1. The endpoint is served only on the capabilities endpoint group 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.
I want to Page
See it work in ten minutes Quick start
Decide what to expose Expose a command or query safely
Understand who may call what Authorization
Gate the endpoint Gate the endpoint
Declare the agent-visible allowlist in one file Capability manifest
Name tools and choose scopes Scopes and descriptions
Connect Claude, VS Code or another client Connect clients
Debug with a visual client Test with MCP Inspector
See which agent did what Audit log
Fix an error Troubleshooting
Look up an option Options reference

Tool sources and authorizers covers curated tool sources, authorizers, exclusive tools, session authority and the Origin check in depth.