Schedule and publish social posts to seven networks through AI agents with a required Postlia Pro API key.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
One-click editor setup isn’t available for this listing yet — we don’t have a confirmed install command, and we’d rather show nothing than point your editor at the wrong package or host. Follow the project’s own setup instructions, linked above.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Postlia.
The Postlia MCP server connects AI agents to Postlia for social publishing workflows. Its stated scope is scheduling and publishing social posts to seven networks. This places it in the 🌐 Social Media category and makes it relevant when an agent needs to move content from an automated workflow into scheduled or published social posts.
The available information does not list the seven networks by name, describe supported post formats, or identify additional account-management features. Treat the documented capability as limited to scheduling and publishing social posts through Postlia rather than assuming support for analytics, engagement, media handling, or campaign management.
An AI agent uses the Postlia MCP server as the connection point to Postlia. The server exposes Postlia’s social-posting capability to the agent, which can then schedule or publish posts for the connected social networks. The source description does not provide the individual tool names, request fields, scheduling options, or response formats.
The Postlia MCP server requires a Postlia API key on the Pro plan. The provided material does not specify the environment-variable name, authentication header, endpoint details, installation command, or configuration file format. Those details should be checked in Postlia’s current documentation before implementation.
A Postlia Pro API key is required to use the Postlia MCP server. Obtain the key through Postlia before configuring an agent or MCP host. Because no README or configuration example is available, the exact setup steps cannot be confirmed from the supplied material.
Do not infer a particular variable name or client configuration from this listing. The source also does not state whether the server can be configured in Claude Desktop, Cursor, Windsurf, Cline, or another MCP client. Confirm client compatibility and the required key placement with Postlia’s documentation.
The documented capabilities are:
The source does not name separate MCP tools or explain whether scheduling and publishing are exposed as separate operations. It also does not document post editing, deletion, previews, analytics, replies, direct messages, or support for specific media types.
The main documented limitation is the Pro-plan requirement: a Postlia API key is needed. The listing does not identify the supported networks, so verify that the destinations needed by your workflow are included among the seven supported networks.
The Postlia MCP server should be evaluated against the exact scheduling and publishing behavior your agent requires. Details such as time zones, recurring schedules, drafts, approval steps, rate limits, error handling, and account permissions are not provided. No license information is available in the supplied material, and no compatible MCP clients are confirmed.
No reviews yet — be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/postlia)<a href="https://allmcps.com/mcp/postlia"><img src="https://allmcps.com/api/badge/postlia?style=directory" alt="Postlia on AllMCPs" /></a>