Agent Atlas is an enterprise MCP (Model Context Protocol) gateway built with ASP.NET Core 10 and .NET Aspire. It turns a messy internal API estate into a governed, searchable catalog of tools that both humans and AI agents can discover and invoke safely.
What it does
Capability
Description
Catalog
Reads OpenAPI specs from a GitOps data-plane repository. Teams annotate operations with x-mcp vendor extensions to mark them as agent tools.
MCP Server
Exposes three MCP tools — SearchTools, DescribeTool, ExecutePlan — via Streamable HTTP transport at /mcp.
Execution Engine
Interprets a JSON plan DSL (call, foreach, if, return steps) and proxies requests to downstream APIs, forwarding the caller’s JWT.
React UI
A read-only capability map for developers and operators.
Quick start
# 1. Trust the HTTPS development certificate (required once per environment)
dotnet dev-certs https --clean
dotnet dev-certs https
dotnet dev-certs https --trust# 2. Run with Aspire (starts all services including Keycloak)
aspire run --project src/Atlas.AppHost
Note: Aspire uses a local HTTPS certificate for service-to-service communication via its internal DCP process manager. Without a trusted certificate the AppHost times out after 20 seconds. On Linux, dotnet dev-certs https --trust may exit with code 4 when it cannot register with browser trust stores — this is non-fatal; the certificate is still trusted for .NET clients.
Note: On first run, Docker pulls the Keycloak and MCP Inspector images. atlas-host will show as Running in the Aspire dashboard only after Keycloak has finished starting (allow 2–5 minutes).
Documentation
Browse the full documentation using the navigation on the left (or above on mobile).