# Postkeg

> Postkeg is an API for posting to social networks and reading the results, without your own platform approvals. Your app calls one REST API; Postkeg holds the connected accounts, publishes on time and collects numbers. An MCP server exposes the same API to assistants.

## Docs

- [Everything in one file](https://api.postkeg.com/llms-full.txt): the guide, reference, snippets and recipes below, as Markdown
- [OpenAPI 3.1 description](https://api.postkeg.com/api/v1/openapi.json): machine-readable, for code generators
- [Developer page](https://api.postkeg.com/developers): the same for people
- Integration guide (MCP resource postkeg://docs/integration-guide): How to use Postkeg from an app: API keys, connect links, posting with media links, webhooks and signature checks, idempotency, rate limits and caps, errors.
- Webhooks (MCP resource postkeg://docs/webhooks): Every webhook event with its payload, the envelope and headers, signature checks in PHP, Node and Python, retries, the delivery log, sending again, wildcards and automatic switch-off.
- API reference (MCP resource postkeg://docs/api-reference): Every endpoint with its scope, input and answer, generated from the live OpenAPI document.
- Code snippets (MCP resource postkeg://docs/snippets): Ready-to-paste curl, JavaScript, Python and PHP for the common tasks.
- Recipes for your assistant (MCP resource postkeg://docs/recipes): Jobs to hand to an assistant connected to Postkeg ("ask your assistant: ..."), and how to build the integration with one.

## Connect an assistant

- MCP server (Streamable HTTP): https://api.postkeg.com/mcp
- Authenticate with an API key: `Authorization: Bearer <key>`, or sign in with OAuth where the assistant supports it.
