llms.txt Content
# QPost
> Video publishing infrastructure for AI agents. QPost publishes to the three
> platforms that matter for generated video — YouTube, TikTok, and Instagram —
> through a REST API and a native MCP server, so an agent can publish
> autonomously without a human clicking through a dashboard.
>
> Publishing to these three requires app approvals (TikTok video.publish,
> Instagram content publishing, YouTube upload) that take months to obtain.
> QPost already holds them, so you connect an account and publish immediately.
QPost is API-first. A human connects their social accounts once and generates
an API key; from then on an agent can create, schedule, inspect, retry, and
delete posts on its own.
## Using QPost as an agent
Hosted MCP endpoint (nothing to install) — point your client at:
```
https://qpost.dev/mcp
```
Authenticate with your QPost API key via the `x-api-key` header (or
`Authorization: Bearer <key>`). Transport is Streamable HTTP, stateless.
Or run it locally over stdio:
```
claude mcp add qpost -e QPOST_API_KEY=your_key_here -- npx -y qpost-mcp
```
Available MCP tools: `list_connected_accounts`, `create_post`, `list_posts`,
`get_post`, `update_post`, `delete_post`, `retry_post`.
Authenticate REST calls with the `x-api-key` header (or
`Authorization: Bearer <key>`). Keys carry scoped permissions
(`posts: read/write/delete`).
## Key endpoints
- `POST /api/post` — create/schedule a post (multipart form: `caption`,
`platforms` JSON, `video` or `images[]`, optional `title`, `scheduledFor`,
`timezone`)
- `GET /api/post` — list posts, filter by `status` or `platform`
- `GET|PATCH|DELETE /api/post/{id}` — inspect, update, or remove a post
- `POST /api/post/{id}/retry` — retry a failed post
- `GET /api/accounts` — list connected platforms before posting
Platforms: `YOUTUBE`, `TIKTOK`, `INSTAGRAM`.
Post statuses: `DRAFT`, `SCHEDULED`, `POSTED`, `FAILED`.
## Docs
- [API & MCP documentation](https://qpost.dev/docs): full request/