postiz-agent¶
Postiz Public API client, MCP Server, and A2A agent for the agent-utilities ecosystem — schedule, publish, and govern social-media content across every connected channel from a single typed tool surface.
Official documentation
This site is the canonical reference for postiz-agent, maintained alongside
every release.
Overview¶
postiz-agent wraps the Postiz Public API with typed,
deterministic MCP tools and a Pydantic-AI agent server. It provides:
PostizApi— arequests-based REST facade over the Postiz Public API, aggregating the integrations, posts, uploads, video, notifications, and analytics surfaces into one client.- Action-routed MCP tools across six domains (integrations, posts, uploads, video, notifications, analytics), each gated by an environment toggle.
- An A2A agent server (
postiz-agentconsole script) that exposes the same capability to other agents over the agent-to-agent protocol.
Every domain remains inactive when its tool toggle is disabled, so the deployed surface is exactly what you configure.
Explore the documentation¶
- Installation — pip, source, extras, and the prebuilt Docker image.
- Deployment — run the MCP and agent servers, Docker Compose, Caddy + Technitium.
- Usage — the MCP tools, the
PostizApiclient, and the CLI. - Backing Platform — deploy a self-hosted Postiz instance with Docker.
- Overview — the connector's role, architecture, and enterprise posture.
- Concepts — the
CONCEPT:PA-*registry.
Quick start¶
Connect it to a Postiz instance:
export POSTIZ_URL=https://api.postiz.com/public/v1
export POSTIZ_TOKEN=your_postiz_token
postiz-mcp --transport streamable-http --host 0.0.0.0 --port 8000
See Installation and Deployment for the full matrix (PyPI extras, Docker image, all transports, the agent server, reverse proxy, and DNS).