MCP Server

What publora/mcp-server MCP server does

The publora/mcp-server MCP server exposes Publora’s social media scheduling functions through the Model Context Protocol. An MCP-compatible assistant can create posts for one or more connected platforms, inspect existing posts, change their schedule or status, and delete them. Posts can be filtered by status, platform, and date range when listing content.

Publora supports Twitter/X, LinkedIn, Instagram, Threads, TikTok, YouTube, Facebook, Bluesky, Mastodon, and Telegram. The server also provides a presigned upload URL for media workflows and can list the social accounts connected to a Publora workspace.

LinkedIn-specific tools add reporting and engagement actions. These include post-level metrics, account statistics, follower totals and growth, and a combined profile summary. The tool set also supports adding or removing reactions and creating or deleting comments on LinkedIn posts. Workspace tools let clients list team members, add a user, or remove a user from the workspace.

How it works

The hosted deployment is available at https://mcp.publora.com. An MCP client sends requests to that HTTP endpoint, and the server uses the supplied Publora credentials to access the associated account and workspace data. The API key is passed in an Authorization: Bearer ... header; the README also documents x-publora-key as an alternative header.

This arrangement lets users express tasks conversationally, such as scheduling a post for a specified time, publishing the same content to several connected platforms, or checking LinkedIn performance. The server does not itself establish social network connections; those accounts must already be connected in Publora for the relevant operations to work.

Setup and configuration

For the hosted version, obtain a Publora API key from the API settings in Publora, then add the endpoint and authorization header to the MCP client configuration. The README provides setup examples for Claude Desktop, Claude Code, and Cursor. Restarting the client makes the tools available.

A local development instance can be run from a clone of the repository after installing its npm dependencies. The documented start command uses PUBLORA_API_URL=https://api.publora.com npm start and serves locally on port 3100 by default. PORT changes the listening port, while PUBLORA_API_URL selects the backend API URL.

Tools and capabilities

The publora/mcp-server MCP server provides 18 listed tools across four areas:

• Posts: list, create, inspect, update, delete, and obtain media upload URLs.
• Connections: list connected social accounts.
• LinkedIn: retrieve post and account analytics, inspect follower growth, summarize a profile, and manage reactions and comments.
• Workspace: list, add, and remove team members.

The post creation tool schedules content to one or more platforms rather than limiting an operation to a single network.

Limitations and notes

The material documents a hosted service and a local development mode, but it does not describe platform-specific posting restrictions, media file limits, rate limits, or the required Publora subscription for each operation. LinkedIn analytics and engagement tools are specific to LinkedIn and should not be assumed to provide equivalent functions for the other supported platforms.

The publora/mcp-server MCP server requires a Publora API key for the hosted configuration. Keep that key in the MCP client’s protected configuration rather than exposing it in prompts or source code. The repository is licensed under MIT.