relay
Enables MCP clients to drive Relay, an AI support-triage agent, by exposing tools for customer lookup, documentation search, ticket classification, reply, and escalation, with full guardrails and read-only mode option.
README
Relay
Live demo: https://relay-6i5seq.fly.dev — the root redirects to a dashboard of real agent runs (cost, latency, outcomes).
An AI support-triage agent, built as a production service — not a notebook.
Relay receives support tickets for a fictional SaaS product (Lanekeep) over a REST API and works each one autonomously: it looks the customer up in a real database, classifies the ticket, searches the product documentation so every claim is grounded, and either sends a resolved reply or escalates to a human with a structured handover — streaming its reasoning steps to the client as server-sent events the whole way.
The agent loop is written by hand on the Claude API (no orchestration framework), so the control flow, step caps, and event stream are fully visible and testable.
Status / roadmap
- [x] Phase 1 — Core agent service: FastAPI + SSE, hand-written agent loop,
tools (
lookup_customer,search_docs,set_category,send_reply,create_escalation), SQLite with seed data, keyword doc search - [x] Phase 2 — Guardrails: Pydantic-validated tool inputs, per-run cost
budget with hard abort, write-tool policy (
?dry_run=true), structured error events on API failure, per-stepusageevents with running cost - [x] Phase 3 — Evaluation harness: 12-ticket golden dataset, deterministic
action/category grading plus LLM-as-judge grounding checks, JSON report
artifact, threshold exit code for CI (
python -m relay.evals) - [x] Phase 4 — Observability: JSON structured logs, OpenTelemetry spans
per run/model-call/tool (OTLP export via
OTEL_EXPORTER_OTLP_ENDPOINT), per-run metrics in SQLite,/metricsaggregates,/dashboardpage - [x] Phase 5 — MCP server: the same tool registry (plus ticket lifecycle tools) served over the Model Context Protocol via stdio, behind the same validation and write-policy guardrails
- [x] Phase 6 — Ship it: Dockerfile with container healthcheck, GitHub Actions CI (lint + tests + Docker smoke test on every push; on-demand eval workflow with report artifact), Fly.io deploy config
See docs/PROJECT_BRIEF.md for the full project definition.
Quick start
python3 -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"
cp .env.example .env # add your ANTHROPIC_API_KEY
uvicorn relay.main:app --reload
Then, in another terminal:
./scripts/demo.sh
You'll see the agent's run streamed as SSE — text updates, each tool call and its
result, and a final resolution event.
API
| Method | Path | Description |
|---|---|---|
GET |
/health |
Liveness + configured model |
POST |
/tickets |
Create a ticket |
GET |
/tickets/{id} |
Fetch a ticket |
POST |
/tickets/{id}/process |
Run the agent; streams steps as SSE. ?dry_run=true denies write tools by policy |
GET |
/metrics |
Run counts, outcomes, token/cost totals, latency p50/p95 |
GET |
/dashboard |
Minimal live dashboard over /metrics |
MCP server
The same tools are exposed over the Model Context Protocol, so Claude Desktop, Claude Code, or any MCP client can drive Relay directly:
claude mcp add relay -- /path/to/.venv/bin/python -m relay.mcp_server
Tool calls go through the same guardrail chain as the agent loop (Pydantic
input validation + write policy). Set RELAY_MCP_ALLOW_WRITES=false to serve
a read-only surface.
Tests
pytest
Tests cover the tools and the HTTP surface without calling the Claude API, so they run free and fast in CI.
Architecture
client ──POST /tickets/{id}/process──▶ FastAPI ──▶ agent loop (Claude API)
◀───────── SSE: text / tool_use / tool_result / resolution ─────────┘
│
tools ──▶ SQLite (customers, tickets,
escalations, replies)
└─▶ kb/*.md (docs search)
Deployment
CI runs lint, the 37-test suite, and a Docker build + container smoke test on
every push. The eval suite runs on demand (Actions → Evals) against the
ANTHROPIC_API_KEY repository secret and uploads the JSON report as an
artifact.
Deploy to Fly.io with the included fly.toml:
fly launch --no-deploy
fly volumes create relay_data --size 1
fly secrets set ANTHROPIC_API_KEY=sk-ant-...
fly deploy
Or run the container anywhere:
docker build -t relay .
docker run -p 8000:8000 -e ANTHROPIC_API_KEY=sk-ant-... relay
License
MIT
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
Neon Database
MCP server for interacting with Neon Management API and databases
E2B
Using MCP to run code via e2b.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.