# Publish Zuola

> Private social publishing workspace with a public integration contract. Go + SQLite handle durable video delivery and explicit multi-platform scheduling. Documentation is public; all business requests require an owner-issued application Bearer token.

## Integration documents
- [Developer portal](https://publish.zuola.com/developers): Human-readable quick start, REST endpoints, MCP scope, limits and examples.
- [OpenAPI 3.1](https://publish.zuola.com/openapi.json): Authoritative machine-readable service API request and response schemas.
- [Full integration guide](https://publish.zuola.com/llms-full.txt): Workflow, provenance rules, retries and instructions for coding agents.

## Entry points
- REST base: https://publish.zuola.com/api/v1/integrations/clip
- MCP endpoint: https://publish.zuola.com/mcp (Streamable HTTP, stateless JSON, custom Bearer header required).
- MCP read-only tools: publish_capabilities, publish_package_status.
- MCP resource: publish://integration.
- [Owner application settings](https://publish.zuola.com/dashboard#settings): Only the owner can create/revoke tokens. General visitors cannot self-provision publishing access.

Binary uploads and explicit scheduling use REST, not MCP. The public integration currently accepts video packages, not arbitrary text-only posts or inbox administration. Never submit a real publishing request just to test connectivity. Never put tokens in chat, URLs, browser code or logs.