Skip to content

v0.2.0 — OpenAPI connectors

Choose a tag to compare

View all tags
@chris-dare chris-dare released this 13 Jun 09:11
v0.2.0
86a483a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Auto-generate governed tools from an OpenAPI spec — onboarding a system goes from code to config.

Highlights

  • OpenAPI connectors — register_openapi_tools(...) reads an OpenAPI 3.x spec (URL, file, or dict; JSON or YAML) and registers one MCP tool per allowlisted operation. Each tool is wrapped in the same tool_runtime as a hand-written one — same scope check, audit row, and error envelope. Auto-generated does not mean ungoverned.
  • Config-only onboarding — point PONTIFEX_CONNECTORS_CONFIG at a connectors YAML file and the server registers the tools at startup. No domain code required.
  • Derived scopes — each generated tool enforces a domain:resource:action scope derived from the operation (resource from the path, action from the verb), slotting straight into the existing scope model.
  • Opt-in by design — operations are exposed via an explicit include allowlist; mutating verbs require allow_mutations. Typos and unapproved writes fail at startup, never silently.
  • Backend auth — BearerFromEnv / HeaderFromEnv authenticate the generated adapter to the downstream API; secrets are read from the environment (presence checked at boot).
  • Resilient — downstream calls run through a generated DataAdapter under DataSourceManager, so circuit breaking applies; connector health appears in /health/ready.

New docs: the Connectors guide. Full detail in #38 / #40.

Compatibility

Additive and backward compatible with 0.1.0. New dependency: pyyaml.

Assets 2
Loading