How to Connect All 16 Publora MCP Tools: Complete Guide

TL;DR
A complete reference to the 16 Publora MCP tools, what each one does, and how to connect the server so an AI agent can schedule, publish, and manage social media by prompt.
Publora's MCP server turns your social scheduling into something an AI agent can operate directly, no HTTP code, no browser clicking, just prompts. Connect it once and the agent gets 16 tools: posting, media, connections, and LinkedIn engagement. Here's every tool, what it does, and how to wire the server up.
What MCP Gives You
MCP (Model Context Protocol) is the standard that lets an AI agent call real tools instead of guessing. Publora exposes its API as MCP tools, so when you tell Claude "schedule this to LinkedIn and Bluesky for 9am," it calls list_connections and create_post itself. The 16 tools fall into four groups.
Group 1: Posts (6 tools)
The core scheduling tools. Everything you would do to a post in a dashboard, as tool calls.
| Tool | What it does |
|---|---|
list_posts | List posts with filters for status, platform, and date range |
create_post | Schedule a post to one or more platforms |
get_post | Get the details of a post group |
update_post | Change status (draft or scheduled) or reschedule |
delete_post | Delete a post group and all its platform posts |
get_upload_url | Get a presigned URL to upload media |
One difference from the REST API is worth knowing: in MCP, create_post requires a scheduledTime so agents always specify when to publish. Platform-specific settings (TikTok privacy, YouTube titles, Instagram video type, Threads reply control) are not available over MCP; those go through the REST API.
Group 2: Media (3 tools)
Uploading a file is a multi-step job, so it gets its own tools alongside get_upload_url.
| Tool | What it does |
|---|---|
complete_media | Finalise an upload once the file has been pushed |
delete_media | Remove an uploaded media item |
prune_media_reference | Detach a media reference from a post |
Group 3: Connections (1 tool)
| Tool | What it does |
|---|---|
list_connections | List all connected social accounts and their platform IDs |
Small but essential. create_post needs platform connection IDs, and this is where the agent gets them, which is why the server's own instructions tell agents to call it first and copy the IDs verbatim rather than inventing them.
Group 4: LinkedIn Engagement (6 tools)
LinkedIn gets its own set, so an agent can act on posts rather than only publish them.
| Tool | What it does |
|---|---|
linkedin_create_comment | Post a comment on a LinkedIn post |
linkedin_delete_comment | Delete a comment |
linkedin_create_reaction | React to a post (LIKE, PRAISE, EMPATHY, and others) |
linkedin_delete_reaction | Remove a reaction |
linkedin_create_reshare | Reshare a post to your own feed |
linkedin_list_mentionables | List people and organizations you can @mention |
Analytics and workspace management are handled through the REST API rather than MCP, so an agent that needs post statistics or managed-user administration calls the API directly.
Connecting the Server
All 16 tools come from one server. Point your MCP client at https://mcp.publora.com with your API key as a Bearer token, and every tool appears at once.
# Claude Code, one command claude mcp add publora --transport http https://mcp.publora.com \ --header "Authorization: Bearer sk_YOUR_API_KEY" # Verify the server is up curl https://mcp.publora.com/health # {"status":"ok","service":"publora-mcp"}
The same key works for both MCP and the REST API. Once it's added, you never call these tools by name, you just describe what you want and the agent picks the tool. Full setup for Claude Desktop and Claude Code is in the API and MCP guide.
A Note on the Count
Tool counts move as the server changes, and published documentation can lag behind it. The 16 above were read directly from the live server with a tools/list call in August 2026. If you want to check the current set yourself rather than trust any article, ask your MCP client to list the server's tools, or make the same call against mcp.publora.com.
FAQ
How many MCP tools does Publora have?
16: six for posts, three for media, one for connections, and six for LinkedIn engagement.
How do I connect the MCP server?
Add https://mcp.publora.com to your MCP client with your Publora API key as a Bearer token. All 16 tools become available immediately, driven by plain-language prompts.
What can't MCP do that REST can?
Platform-specific settings (TikTok privacy level, YouTube title, Instagram video type, Threads reply control) and the deeper workspace operations are REST-only. MCP covers scheduling, media, analytics, engagement, and basic workspace user management.
Give your agent 16 tools
Connect Publora's MCP server once and let Claude, or any MCP agent, schedule, analyze, and engage across your social accounts by prompt. Free to start.
Get Your API KeyFurther Reading
- What Is a Social Media Scheduling API?
- Headless Social Media Publishing
- Build a White-Label Social Media Workflow
About the author. Written by the Publora team. Every tool listed is from the live MCP server documented at docs.publora.com; the three pending LinkedIn feed tools are noted as such.
Related Articles

How to Build a White-Label Social Media Workflow for Clients
Build a white-label social media workflow where your product is the brand and Publora runs headless behind it, using the Workspace API's managed users and per-user keys.

The Agency Guide to Social Media Scheduling Workflows That Scale
The workflows that let a social media agency add clients without adding chaos: intake, drafting, approvals, scheduling, and reporting that actually scale.

Build a Content Bot: RSS to AI Caption to Auto-Publish
Build a content bot that reads an RSS feed, writes a caption with AI, and auto-publishes to social media through the Publora API. Full flow, real endpoints.

Social Media API: Rate Limits, Tokens, and Webhooks Explained
A developer reference for the Publora social media API - how API-key auth works, what rate limits actually apply, and how to set up webhooks for post events.