mcpbeat

Publora MCP Server

com.publora/mcp-server
answering

Publora is answering right now. Last checked 14 min ago. It exposes 16 tools.

Schedule and publish to 10 social platforms: LinkedIn, X, Instagram, TikTok, YouTube, and more.

Uptime history 44 hours of history
44 hours agonow
100.0%
Uptime 24h
91 of 91 checks
16
Tools
read from the server
522 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add mcp-server --transport http https://mcp.publora.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.publora.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp-server]
url = "https://mcp.publora.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.publora.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.publora.com/mcp"
    }
  }
}

Available tools 16

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

linkedin
linkedin_create_comment
Post a comment on a LinkedIn post
linkedin_create_reaction
React to a LinkedIn post (like, praise, etc.)
linkedin_create_reshare
Reshare (repost) an existing LinkedIn post to your feed, optionally with commentary
linkedin_delete_comment
Delete a comment from a LinkedIn post
linkedin_delete_reaction
Remove your reaction from a LinkedIn post
linkedin_list_mentionables
List LinkedIn people captured from engagement (comments/reactions) on your connected company pages. Each entry carries the native app-scoped person id — the only id namespace LinkedIn resolves in mentions — plus a ready-to-use mention token in the form @{urn:li:person:ID|Name}. Requires a paid plan (403 UPGRADE_REQUIRED otherwise).
post
create_post
Create a post. FASTEST for media posts: pass mediaUrls (public https URLs — Publora downloads them server-side) together with scheduledTime to create AND schedule in one call; platforms like Instagram, TikTok, YouTube require media before scheduling. Manual alternative for local files: omit scheduledTime to create a draft, upload media with get_upload_url + HTTP PUT + complete_media (once per file), then call update_post with status 'scheduled'.
delete_post
Delete a scheduled post group and all its platform-specific posts
get_post
Get details of a scheduled post group and its platform-specific posts
update_post
Edit an existing draft/scheduled post without deleting it. You may change its base content, target platforms, status, scheduled time, per-platform settings, and/or APPEND media from public https URLs via mediaUrls. Before changing platforms, call list_connections and copy each target's platformId verbatim. Published/failed posts and posts already being published are not editable. Scheduling re-validates the complete final content/media/platform state; omitting a field keeps its current value.
complete
complete_media
Finalize an uploaded media file after the HTTP PUT to the presigned uploadUrl: Publora probes the bytes server-side and marks the media 'ready' for scheduling. Call once per uploaded mediaId (from get_upload_url), then schedule via update_post. Not needed for media attached via mediaUrls.
connections
list_connections
List all connected social media accounts (Twitter, LinkedIn, TikTok, etc.)
media
delete_media
Remove one media file from a post group — e.g. a duplicate or never-uploaded slot that blocks scheduling with MEDIA_COUNT_EXCEEDED or media-not-ready errors. Find mediaIds via get_post (its 'media' array shows status per file). Deleting media from a scheduled post demotes it to draft; re-schedule with update_post afterwards.
posts
list_posts
List scheduled/published posts with filtering by status, platform, date range
prune
prune_media_reference
Repair MEDIA_REFERENCE_MISSING by removing a stale/dangling media reference from an owned post group, even when the MediaFile row is absent or inaccessible. Use delete_media for normal existing media rows.
upload
get_upload_url
Get a presigned S3 URL to upload a LOCAL media file (image/video) for a post. Call ONCE per file — repeat calls with the same fileName return the same mediaId instead of adding duplicate slots; use unique fileNames for different files. Next: HTTP PUT the raw bytes to uploadUrl with a Content-Type header EQUAL to the contentType passed here (the signature enforces it), then call complete_media with the mediaId. If the file is already reachable at a public URL, prefer create_post/update_post with mediaUrls — no upload steps at all.

Endpoints

URLTransportStateLatencyChecked
https://mcp.publora.com/mcp streamable-http answering 194 ms 14 min ago

Publora — questions

Answers built from our own checks of this server.

What can Publora do?
It exposes 16 tools, read directly from the server on our last check. Among them: complete_media, create_post, delete_media, delete_post, get_post, get_upload_url and 10 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Publora mostly used for?
Its tools cluster around linkedin and post. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Publora working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 522 ms. The bar chart above shows every period we have measured.
How do I connect Publora?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Publora need an API key?
No. Publora completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 16 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Publora?
It answers our handshake in 522 ms on average, which is faster than 21% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.