pontifex-mcp 0.5.0

The security, access-control, and governance layer for MCP servers.

pontifex-mcp

The security and governance layer for MCP servers, built on the official MCP Python SDK.

pontifex-mcp lets you build MCP servers that connect AI agents to real systems without giving up control over who can call what. You write the tools; it handles authentication, per-caller scopes, rate limits, and a full audit trail.

Key features

• Secure by default — OAuth 2.1 JWTs and sk_… API keys; every tool call is authenticated. Any OIDC provider (Auth0, Entra, Clerk, Keycloak).
• Least-privilege scopes — namespace:resource:action, checked before every call. Callers can't widen their own access.
• Auditable — every call recorded: who, what, when, data source, cache hit, latency.
• Standards-based — RFC 9728 discovery + WWW-Authenticate; MCP clients bootstrap auth on their own.
• Resilient — per-caller rate limiting, adapter failover, circuit breaking.
• Observable — Logfire / OpenTelemetry tracing and metrics wired in.
• Drop-in connectors — generate governed tools from an OpenAPI spec (code or config), with optional per-user OAuth token exchange (RFC 8693) to the downstream.
• Built on the MCP SDK — keep its tools, protocol, and transports; add the controls a production server needs.
• Coding-agent friendly — bundles an official agent skill (uvx library-skills) so your coding agent builds on guidance that matches your installed version.

Asymmetric-only JWT validation, generic auth errors, and no token claim can escalate a caller.

Install

pip install pontifex-mcp     # or: uv add pontifex-mcp

Requires Python 3.12+. The floor below needs nothing else; Postgres and Redis come in only when you turn on API-key auth.

Start in a few lines

PontifexMCP is a drop-in subclass of the MCP SDK's FastMCP. The floor needs no database, no Redis, and no auth — the caller is anonymous and every call is audited to stdout.

from pontifex_mcp import PontifexMCP

mcp = PontifexMCP("payments")

@mcp.tool(scope="balance:read")
async def get_balance() -> dict:
    return {"available": 421000, "currency": "usd"}

@mcp.tool(scope="refunds:execute")
async def issue_refund(charge_id: str, amount: int, idempotency_key: str) -> dict:
    return {"refunded": amount, "charge_id": charge_id, "status": "succeeded"}

if __name__ == "__main__":
    mcp.run()                 # stdio; mcp.run(http=True) binds 127.0.0.1

The scope= you declared is advisory until you add an auth backend — then it's enforced, unchanged.

Graduate to enforcement

from pontifex_mcp import PontifexMCP, ApiKeyAuth

mcp = PontifexMCP(
    "payments",
    auth=ApiKeyAuth(),        # Bearer required, scopes enforced (DATABASE_URL + REDIS_URL)
    audit="audit.db",         # durable audit — SQLite here; a Postgres URL in production
)

Now every request needs a valid sk_… API key (or an OAuth 2.1 JWT via JwtAuth()), a caller without payments:refunds:execute is rejected before issue_refund runs, and each call persists an audit row — who, what, when, latency. The same switches flip from the environment, so laptop → production is config, not code.

Auth, scope checks, rate limiting, the audit row, and the structured error envelope are all applied for you — your handler just returns data.

Configuration

Infrastructure settings read from bare, unprefixed env vars:

DATABASE_URL, REDIS_URL          # required (the app fails fast if unset)
AUTH_JWKS_URL, AUTH_ISSUER, AUTH_AUDIENCE, AUTH_SCOPES_CLAIM   # enable the OAuth/JWT path
PUBLIC_BASE_URL                  # canonical URL advertised in OAuth discovery

Namespace-specific settings on your subclass read with your namespace's env_prefix.

Connect an existing API (no hand-written tools)

If the system already has an OpenAPI spec, generate governed tools from it — each one wrapped in the same tool_runtime (scope check, audit, error envelope). Operations are opt-in via an explicit include allowlist.

from pontifex_mcp import register_openapi_tools, BearerFromEnv

register_openapi_tools(
    mcp,
    spec="https://api.internal/openapi.json",   # URL, path, or dict; JSON or YAML
    namespace="orders",
    base_url="https://api.internal",
    audit=audit,
    auth=BearerFromEnv("ORDERS_API_TOKEN"),     # service credential to the backend
    include=["GET /orders", "GET /orders/{id}"],
)

Or onboard with config alone — point PONTIFEX_CONNECTORS_CONFIG at a connectors YAML file and the server registers the tools at startup, no namespace code.

For a backend that enforces its own per-user permissions, swap the service credential for OAuth token exchange (RFC 8693) — Pontifex exchanges the caller's token for one scoped to the downstream, on their behalf (the inbound token is never forwarded):

from pontifex_mcp import TokenExchange

auth = TokenExchange(
    token_endpoint="https://idp.example.com/oauth/token",
    audience="https://api.internal",
    client_id_env="PONTIFEX_OAUTH_CLIENT_ID",
    client_secret_env="PONTIFEX_OAUTH_CLIENT_SECRET",
)

Exchanged tokens are cached in process memory by default, or in Redis (PONTIFEX_TOKEN_CACHE=redis, encrypted at rest). See the Connectors guide for the full configuration.

Who it's for

Reach for pontifex-mcp when you're exposing internal or proprietary systems — an orders API, a customer database, an analytics warehouse — to AI agents (Claude Desktop, your own agents, anything that speaks MCP), and unauthenticated tool access isn't an option.

If you're shipping a single public tool over non-sensitive data, the MCP SDK on its own is simpler. Come here when access control and an audit trail start to matter.

License

Apache-2.0 © Chris Dare. Part of Argonauts.