Quickstart

Get your first AI agent governed by MITRITY in under five minutes. By the end of this guide, you will have a Mitrity Gateway deployed alongside your agent, connected to the MITRITY control plane, and streaming governance events in real-time.

Prerequisites

Before you begin, make sure you have:

A MITRITY account -- sign up here if you have not already
At least one AI agent running in your environment (any framework: LangChain, CrewAI, AutoGen, MCP, or custom)
Docker installed (for the quickest setup), or a 64-bit Linux host for the standalone binary
Your Agent Key — generated when you register an agent in the MITRITY dashboard

Step 1: Create your workspace

Name: sales-bot
Mission scope: "Read CRM contacts, send follow-up emails, update deal stages"

MITRITY will generate an Agent ID and a one-time Agent Key (ak_...). Save the Agent Key — it cannot be retrieved later.

Step 2: Install Mitrity Gateway

Create a config file (mitrity-gateway.yaml) that defines your upstream MCP servers:

agent_id: "your-agent-id"
api_key: "ak_your-agent-key"
control_plane:
  base_url: "https://api.mitrity.com"

upstreams:
  - name: "filesystem"
    command: "/usr/local/bin/mcp-filesystem"
    args: ["--root", "/data"]

Docker (recommended for getting started)

docker run -d \
  --name mitrity-gateway \
  -v $(pwd)/mitrity-gateway.yaml:/etc/mitrity/config.yaml \
  ghcr.io/mitrity-io/mitrity-mcp-gateway:latest

Standalone binary

curl -Lo mitrity-gateway \
  https://releases.mitrity.com/mcp-gateway/latest/mitrity-mcp-gateway-linux-amd64
chmod +x mitrity-gateway
./mitrity-gateway --config mitrity-gateway.yaml

For systemd and Cloud Run deployment options, see the deployment guide.

Step 3: Point your agent at the gateway

Configure your MCP client to use Mitrity Gateway as its MCP server:

{
  "mcpServers": {
    "mitrity-gateway": {
      "command": "/path/to/mitrity-gateway",
      "args": ["--config", "mitrity-gateway.yaml"]
    }
  }
}

Your agent now accesses all upstream tools through the governed gateway. No proxy environment variables or certificate configuration needed.

Alternative: Mitrity MCP Sidecar. For simple, single-server setups, you can use the Mitrity MCP Sidecar instead. The sidecar wraps a single upstream MCP server via stdio and is the lightest possible deployment option.

Step 4: See your first governed event

Trigger an action from your agent. Within seconds, you will see events flowing in the Audit Log in the dashboard. Each event shows:

The agent that performed the action
The action type and parameters
The policy decision (allow, deny, alert, or hold)
The latency of the governance decision (typically <0.5ms)

You are now governing your first agent. From here, explore:

Core concepts to understand mission profiles, behavioral hashes, and drift scores
Demo: Mitrity Gateway or Demo: MCP Sidecar to see all governance capabilities in a scripted 10-minute scenario
Integration modes to learn about Mitrity Gateway and Mitrity MCP Sidecar
Enforcement modes to graduate from monitoring to active enforcement
SIEM integration to forward events to your existing security stack

NextCore Concepts