MCP Portico

A generic, multi-tenant MCP frontend for HTTP APIs.

MCP Portico turns OpenAPI descriptions or inspected backend source code into policy-controlled MCP connections. One deployment can expose multiple backend systems while isolating tenants, credentials, catalogs, and runtime sessions.

Status: Phase 2 (catalog v2 + deterministic compiler) complete. This repository is a fresh implementation following the implementation plan.

Why MCP Portico

• The catalog is the gate - operations are compiled from OpenAPI/Swagger or AI-analyzed backend metadata into a validated catalog. Only catalog-gated operations can run, keyed by stable operation ID.

• One deployment, many backends - a backend registry and tenant-scoped connections isolate URLs, credentials, and policies.

• A fixed MCP toolset - discovery, description, and gated execution instead of arbitrary method/path input.

• An operator CLI - catalog import/validate/diff, registry validation, connection testing, and usage analysis.

Related MCP server: anythingmcp

Architecture

flowchart LR
    OA["OpenAPI / Swagger 2.0-3.2"] --> IM["Import adapters"]
    REPO["Backend repository"] --> AI["AI analysis skill"]
    AI --> OA2["Generated OpenAPI + policy overlay"]
    OA2 --> IM
    IM --> IR["Normalized API model"]
    POL["Policy overlay"] --> COMP["Catalog compiler"]
    IR --> COMP
    COMP --> CAT["Validated catalog v2"]
    CAT --> REG["Backend & connection registry"]
    SEC["Secret resolver"] --> REG
    IDP["Portico identity provider"] --> RT["Tenant-aware runtime"]
    REG --> RT
    RT --> MCP["Fixed MCP toolset"]
    MCP --> UP["Authorized upstream APIs"]

Authentication at two layers

flowchart LR
    CLIENT["MCP client"] -->|"Portico API key"| AUTH["IdentityProvider"]
    AUTH --> RT["MCP Portico runtime"]
    RT -->|"Connection auth"| CONN["UpstreamAuthProvider"]
    CONN --> BACKEND["Backend API"]

Client credentials and upstream credentials are never shared. Secrets are stored as environment references, and nothing secret appears in logs, telemetry, or MCP responses.

Quick start

# Prerequisites: Node.js >= 22 and pnpm 11
pnpm install
pnpm ci:check   # typecheck, format, tests, sweeps, build, smoke
pnpm serve      # Phase 1 health server on http://127.0.0.1:3000

mcp-portico --help and mcp-portico serve are available after pnpm build.

Planned interface

mcp-portico serve
mcp-portico catalog import <openapi-file>
mcp-portico catalog validate <catalog-file>   # implemented
mcp-portico catalog diff <old-catalog> <new-catalog>   # implemented
mcp-portico registry validate <registry-file>
mcp-portico connection test <connection-id>

The catalog v2 JSON Schema and policy overlay schema are published under schemas/; see examples/sample-catalog.json for a compiled example and examples/sample-overlay.json for its policy overlay.

What's next

The implementation plan defines seven phases: catalog v2 and the deterministic compiler (2, done), tenant registry and authentication (3, next), OpenAPI importers (4), the operation runtime (5), the AI backend-analysis skill (6), and the inspector plus clean cutover (7).

Contributing

See CONTRIBUTING.md for setup and verification requirements, SECURITY.md for the security policy, and docs/deprecation-inventory.md for the legacy module removal map.

License

Apache-2.0. See LICENSE.