Discovery & Onboarding Gates


MCP Server & UI Tiers

Google Connected Apps — Partner Reference Server & Workbench

This reference application implements a standards-compliant 3P Partner Model Context Protocol (MCP) Server, OAuth 2.1 Identity Provider, and Interactive Conformance Workbench for integrating partner capabilities across Google Search AI Mode and Gemini.

OpenAPI-First Contract Boundary (GET /openapi.json & GET /openapi.yaml)

Every endpoint, HTTP header (WWW-Authenticate, Mcp-Session-Id, X-Simulate-Token-Rotation), OAuth 2.1 flow, and MCP JSON-RPC 2.0 tool schema exposed by this server is formally specified in openapi/producer-openapi.yaml. Reference consumers can generate or drive a complete client strictly from /openapi.json with zero undocumented out-of-band exchanges.

Integration Architecture & Onboarding Tracks

1. Interactive Track & Architecture Selector

Select your partner integration pattern below to inspect the required discovery endpoints, OAuth 2.1 grant types, ingress security controls, and MCP tool annotations:

  • Type 1 — Bilateral User-Linked Integration (OAuth 2.1 + PKCE S256 + Persistent Linking): Enables authenticated users to view and mutate personal account resources (get_user_reservations, create_reservation, update_reservation_notes, cancel_reservation) with persistent refresh tokens.
  • Type 2 — Unilateral Public / M2M Integration (client_credentials + Reverse DNS / CIDR): Enables public catalog search and discovery (search_catalog_items) without requiring per-user account linking.
  • Hybrid Tiered UI Integration (ui:// MCP Apps & a2ui:// Declarative Surfaces): Combines text summaries (Tier 1) with sandboxed HTML5 AppBridge widgets (Tier 2) and declarative JSON component trees (Tier 3).

2. Inspect Live OpenAPI Specification

Fetch the live self-describing Producer OpenAPI 3.0.3 specification (getOpenApiSpec at GET /openapi.json) to verify all 17 registered operationIds and strongly-typed tool schemas.