# Cassit

> Cassit schedules and publishes social media posts for brands. Each brand's owner decides whether posts wait for approval or go out on schedule. It has a REST API and an MCP server, both authorised with a bearer key.

- [Developer docs](https://cassit.app/docs): keys, scopes, endpoints and tools
- [OpenAPI document](https://cassit.app/openapi.json): the REST API as OpenAPI 3.1
- [A complete example](https://cassit.app/docs#example): a Node script that creates and publishes a text post
- [Changelog](https://cassit.app/changelog): what changed
- [How it works](https://cassit.app/how-it-works)
- [Data and security](https://cassit.app/data)

## MCP

- Endpoint: https://house.cassit.app/mcp
- Header: `Authorization: Bearer ck_...`
- Sign-in (OAuth 2.1 with PKCE): discovery at https://house.cassit.app/.well-known/oauth-protected-resource; the owner approves on a consent page; the app gets these scopes: brands:read, content:read, content:draft, content:schedule, insights:read, tray:read, engine:read, notifications:read
- REST base URL: https://house.cassit.app/api/v1