- Home
- MCP servers
- Postiz
Postiz
- javascript
2
GitHub Stars
javascript
Language
4 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
You run a Postiz MCP Server to access Postiz API functionality through MCP tools and to manage your Postiz content. This server supports multiple transports (SSE, HTTP, and stdio) and is designed to be secure by default when deployed with containers. You can configure it with environment variables, run it in Docker, and health-check it to ensure it’s responsive.
How to use
Connect your MCP client to the HTTP SSE endpoint exposed by the server at http://localhost:3084/sse. You can also run the server locally and use stdio transport if you prefer a local process-based setup. The server provides a battery of MCP tools you can call to interact with Postiz content and API capabilities.
How to install
Prerequisites: you need Docker and Docker Compose installed on your machine. You will configure environment variables for Postiz API access and start the MCP server using containerized deployments.
# Step 1: Copy the example environment file
cp .env.example .env
# Step 2: Edit the .env file with your Postiz API credentials
POSTIZ_API_URL=https://your-postiz-instance.com/api
POSTIZ_API_KEY=your_postiz_api_key_here
PORT=3084
NODE_ENV=production
# Step 3: Start the server with Docker Compose
docker-compose up -d
# If you prefer to run the container directly, you can build and run the image
# Build the image
# docker build -t oculair/postiz-mcp:latest .
# Run the container (adjust as needed for your environment)
docker run -p 3084:3084 --env-file .env --rm -it oculair/postiz-mcp:latest
Additional notes
You can interact with the server through the available MCP tools such as creating posts, retrieving posts, getting integrations, fetching self information, and logging in. The server is designed to work with both HTTP-based and stdio-based MCP clients, giving you flexible deployment options.
If you are using a client like Claude Desktop, you can configure the MCP server entry to point at the HTTP SSE endpoint. Example configuration for Claude Desktop:
{
"mcpServers": {
"postiz": {
"url": "http://localhost:3084/sse",
"disabled": false,
"alwaysAllow": []
}
}
}
Available tools
create-post
Create a new post in the Postiz content store via the MCP API.
get-posts
Retrieve a list of posts from Postiz.
get-integrations
Fetch available Postiz integrations configured in your account.
get-self
Return information about the authenticated MCP client user.
login
Authenticate with the MCP server to obtain a session or token for subsequent requests.