@opengeni/capabilities

Protocol-neutral integration compilation for OpenGeni. Immutable OpenAPI and GraphQL revisions are compiled into local MCPServer implementations so they use the existing lazy tool router, session policy, approval, auth-needed, Toolspace, child-session, and scheduled-task paths.

The package owns protocol parsing and invocation only. Connection persistence, credential encryption, tenant authority, operation receipts, and catalog lifecycle stay in OpenGeni's core/database layers.

Security defaults:

• credentials are resolved for one exact destination and verified before use;
• header, query, and cookie placements are bounded and validated atomically;
• curated Google/Microsoft Integration Definition OAuth stays in the normal encrypted Connection spine;
• redirects are never followed on credential-bearing requests;
• response bodies, schemas, operation counts, and deadlines are bounded;
• mutating operations are marked approval-required by default;
• a safe read/query may refresh and retry exactly once on 401, while a mutation is never replayed after an ambiguous provider authorization result; and
• errors contain structural recovery facts, never provider bodies or secrets.

Local MCP bridge kit

src/mcp-bridge.ts defines the shared contract for provider APIs exposed as in-process MCP servers. A bridge declares a secret-free catalog identity, actual authority class, reviewed tool-surface class, 1-32 exact HTTPS destinations, and the safe-read-only replay rule. Adapter matching is generic and fails closed on ambiguity. The descriptor is not authorization: each adapter still revalidates its Connection or host-owned authority before every provider request.

The Gmail REST adapter is the static reviewed example. OpenAPI and GraphQL Integration Definitions keep their existing local MCP adapters without claiming this descriptor. Google Drive remains one functional Integration row with its existing Connection and facet authority. See docs/design/first-party-mcp-bridges.md.