Postizz MCP Server

Postizz mcp mcp server lets Claude, Cursor and other MCP clients work with Postizz MCP directly. This repository contains a Model Context Protocol (MCP) server implementation for the Postiz platform.

What Postizz MCP does

This repository contains a Model Context Protocol (MCP) server implementation for the Postiz platform.

Key capabilities

• Supports both SSE, HTTP and stdio transports
• Provides access to Postiz API functionality through MCP tools
• Manage Postiz content
• Secure by default with non-root user in Docker
• Environment variable configuration
• Health check endpoint

Tools it exposes

Once connected, the assistant can call these 3 tools directly:

• create-post — get-posts
• get-integrations — get-self
• Debugging — To debug the container, you can run it with an interactive shell:

Installing the postizz mcp mcp server

The server is distributed via a container image as oculair/postiz-mcp, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply 2 environment variables: POSTIZ_API_URL, POSTIZ_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Postizz MCP sits in that group, and the shape of its toolset — create-post, get-integrations, Debugging — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• Maintained by oculairmedia.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the postizz mcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.