Productivity & Tools

How to Connect All 20 Publora MCP Tools: Complete Guide

Serge Bulaev

ยท Updated

How to Connect All 20 Publora MCP Tools: Complete Guide

TL;DR

A complete reference to the 20 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 20 tools: posting, media, account limits and connections, LinkedIn engagement, and Mastodon and Bluesky analytics. 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 20 tools fall into five groups.

Group 1: Posts (5 tools)

The core scheduling tools. Everything you would do to a post in a dashboard, as tool calls.

ToolWhat it does
list_postsList posts with filters for status, platform, and date range
create_postCreate a draft or schedule a post to one or more platforms
get_postGet the details of a post group
update_postEdit the text, target accounts, per-platform settings, status (draft or scheduled) or time
delete_postDelete a post group and all its platform posts

Two details are worth knowing. In MCP, scheduledTime is optional on create_post: leave it out and the post is saved as a draft. And platform-specific settings (TikTok privacy, YouTube titles, Instagram video type, Threads reply control, LinkedIn reposts, X replies and quotes) work over MCP too, passed as platformSettings on create_post and update_post, just as they are in the REST API.

Group 2: Media (5 tools)

Uploading a local file is a multi-step job (get an upload URL, send the file, finalise it), so media gets its own tools. Files that are already online can skip them: pass their public URLs as mediaUrls on create_post or update_post. In ChatGPT, attach_media takes a file straight from the chat.

ToolWhat it does
get_upload_urlGet a presigned URL to upload a local file
complete_mediaFinalise an upload once the file has been pushed
attach_mediaAttach a file from ChatGPT to a draft; Publora downloads and checks it
delete_mediaRemove an uploaded media item
prune_media_referenceRemove a stale media reference that delete_media can’t clear

Group 3: Account and Connections (2 tools)

ToolWhat it does
account_contextYour plan, available features, publishing quotas and how far ahead you can schedule
list_connectionsList all connected social accounts and their platform IDs

Small but essential. create_post needs platform connection IDs, and list_connections 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. account_context is the other call worth making before a batch: it returns the plan, the posts left this month and the latest date a post can be scheduled, so the agent plans around the limits instead of discovering them by hitting one.

Group 4: LinkedIn Engagement (6 tools)

LinkedIn gets its own set, so an agent can act on posts rather than only publish them.

ToolWhat it does
linkedin_create_commentPost a comment on a LinkedIn post
linkedin_delete_commentDelete a comment
linkedin_create_reactionReact to a post (LIKE, PRAISE, EMPATHY, and others)
linkedin_delete_reactionRemove a reaction
linkedin_create_reshareReshare a post to your own feed
linkedin_list_mentionablesList LinkedIn people you can @mention, with ready-to-paste mention tokens (paid plans)

LinkedIn analytics and managed-user (workspace) administration are handled through the REST API rather than MCP, so an agent that needs them calls the API directly.

Group 5: Analytics (2 tools)

Added after the first version of this guide: read-only stats for the two open networks, so an agent can report on what it published. Both need a plan with analytics (Pro or Premium).

ToolWhat it does
post_statsEngagement counters (reactions, comments, reposts, quotes, saves) for up to 50 published Mastodon or Bluesky posts
profile_statsFollowers, following and post count of a connected Mastodon or Bluesky account

Metrics a platform doesn't expose come back as null, not zero: Mastodon has no saves, and neither network reports impressions or reach. Ask “How did my last Bluesky post do?” and the agent calls list_posts, then post_stats.

Connecting the Server

All 20 tools come from one server. In Claude, install it from the connectors directory, claude.ai/directory/publora, sign in to Publora, and every tool appears at once. In any other MCP client, point at https://mcp.publora.com/mcp and either complete the OAuth sign-in your client offers, or send your Publora API key as a Bearer token.

# Claude Code: sign in with OAuth, no API key
claude mcp add --transport http --scope user publora https://mcp.publora.com/mcp
# then run /mcp, pick publora and choose Authenticate

# CI or a machine without a browser: send a key instead
claude mcp add --transport http --scope user publora https://mcp.publora.com/mcp \
  --header "Authorization: Bearer sk_YOUR_API_KEY"

# Verify the server is up
curl https://mcp.publora.com/health
# {"status":"ok","service":"publora-mcp"}

An API key works for both MCP and the REST API. Once Publora is connected, you never call these tools by name, you just describe what you want and the agent picks the tool. Setup for Claude, Claude Code, Cursor and other clients is in the MCP client setup guide.

A Note on the Count

Tool counts move as the server changes, and published documentation can lag behind it. The 20 above were read from the live server with a tools/list call on 2 October 2026 (August 2026 had 16; the two analytics tools came in September, attach_media on 28 September and account_context on 1 October). The server also lists 12 company_* tools for Agency client work, which are not counted here. 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?

20: five for posts, five for media, two for your account and connections, six for LinkedIn engagement, and two for Mastodon and Bluesky analytics. The server also lists 12 company_* tools for Agency client work.

How do I connect the MCP server?

In Claude, install it from the connectors directory, claude.ai/directory/publora, sign in to Publora, and every tool appears at once. In any other MCP client, point at https://mcp.publora.com/mcp and either complete the OAuth sign-in your client offers, or send your Publora API key as a Bearer token. All 20 tools become available immediately, driven by plain-language prompts.

What can't MCP do that REST can?

LinkedIn analytics, webhooks, post logs and workspace management (managed users) are REST-only. Platform-specific settings (TikTok privacy level, YouTube title, Instagram video type, Threads reply control) work over MCP too, through platformSettings. MCP covers scheduling, media, account limits, Mastodon and Bluesky analytics, and LinkedIn engagement.

Give your agent 20 tools

Connect Publora's MCP server once and let Claude, or any MCP agent, schedule, publish, and engage across your social accounts by prompt. Free to start.

Get Started Free

Further Reading


About this article. Every tool listed is from the live MCP server documented at docs.publora.com.

Related Articles