Integrations and API

Kinoder exposes a versioned REST API under /api/v1 and an OAuth-protected Streamable HTTP MCP server at /api/v1/mcp.

Browser contract

The generated OpenAPI document is the canonical browser contract. Frontend types are generated from it rather than duplicated manually.

MCP Pages authoring

Administrators can delegate hierarchical Pages authoring to compatible MCP clients. Delegation uses OAuth authorization code with PKCE, short-lived access tokens, rotating refresh tokens, resource binding, live role checks, explicit scopes, idempotency, and audit events.

MCP content uses Kinoder’s typed widget catalogue. Arbitrary HTML, CSS, JavaScript, data URLs, and permanent third-party media URLs are rejected.

IMAGE PLACEHOLDER - MCP connection flow Replace with MCP client -> OAuth discovery -> Kinoder consent -> scoped tools -> Pages draft -> confirmed publication. Recommended size: 1800 x 1000 px.

Optional integrations include Stripe, S3-compatible storage, Google Fonts, AI providers, TikTok, Facebook Pages, and YouTube. Each requires its own credentials, scopes, approvals, and Kinoder configuration.