Ultra is a transparent proxy that sits between MCP clients and upstream MCP servers. Every request and response passes through Ultra’s pipeline, where it’s traced, logged, audited, and measured.Documentation Index
Fetch the complete documentation index at: https://docs.ultra.security/llms.txt
Use this file to discover all available pages before exploring further.
The Proxy Model
Your MCP client sees Ultra as a single MCP server. Ultra connects to multiple upstream servers and presents their combined tools, resources, and prompts as a unified interface.Key Components
Transport Layer
Ultra supports all MCP transport types:- stdio — Standard input/output (default for local clients like Claude Desktop and Codex)
- HTTP/SSE — Server-sent events over HTTP
- Streamable HTTP — Modern HTTP streaming transport
Pipeline
Every MCP request passes through a chain of interceptors before reaching the upstream server, and the response passes through the same chain in reverse order:| Interceptor | Purpose |
|---|---|
| Trace | Creates distributed traces for every request and response |
| Logging | Structured request/response logging |
| Audit | Records security audit events |
| Metrics | Counters, histograms, latency tracking |
Auth and Policy interceptors are planned but not yet implemented. See Roadmap: Policy Engine.
Aggregator
The aggregator manages connections to multiple upstream MCP servers and presents them as one:- Tool namespacing — Tools from different servers are namespaced to avoid conflicts
- Routing — Calls are routed to the correct upstream based on the tool/resource name
- Connection management — Handles connection lifecycle across transports
- OAuth — Supports OAuth2 authentication for upstream servers that require it
Storage
Observability data is stored locally on your gateway by default, with optional sync to Ultra Hub for cloud deployments.Hub Sync
When connected to Ultra Hub, your gateway periodically syncs traces and audit events to the cloud. The sync runs in the background with configurable intervals, and supports offline operation — data is stored locally and synced when connectivity is restored.What Gets Recorded
For every MCP operation, Ultra records:- Trace records — Operation type, upstream server, tool/resource name, request/response payloads, duration, status, and OpenTelemetry trace/span IDs
- Audit events — Event type, severity, principal (client identity), outcome (allow/deny/error), and detailed context
- Metrics — Request counts, latency histograms, error rates, per-server breakdowns
Next Steps
Pipeline Deep Dive
Learn about the interceptor chain
Aggregator
Understand multi-server routing