Publora MCP Server

Publora MCP Server

Official Model Context Protocol (MCP) server for Publora — control your social media scheduling directly from AI assistants like Claude, Cursor, and any MCP-compatible client.

No coding required. Just describe what you want in plain English:

"Schedule a LinkedIn post for tomorrow at 9am" "How did my last post perform?" "Post this to Twitter and LinkedIn"

Quick Start

Remote Server (Recommended)

Publora hosts an MCP server at mcp.publora.com/mcp — no installation needed.

Using Claude? Install it from the connectors directory: claude.ai/directory/publora. Select Connect, sign in to Publora, approve. No API key, no config file — on web, desktop and mobile alike.

Every other client:

1. Get your API key at app.publora.com/dashboard/api (API in the dashboard sidebar)

2. Add to your MCP client:

{
  "mcpServers": {
    "publora": {
      "type": "http",
      "url": "https://mcp.publora.com/mcp",
      "headers": {
        "Authorization": "Bearer sk_YOUR_API_KEY"
      }
    }
  }
}

Clients that support OAuth (Claude Code, Cursor, VS Code, Codex and others) can leave out headers and sign in through the browser instead.

3. Restart your client and start talking to your AI about social media!

---

Client Setup

claude mcp add --transport http --scope user publora https://mcp.publora.com/mcp

Run /mcp, select publora, choose Authenticate and sign in to Publora in the browser. No API key needed.

For CI or headless machines, send a static key instead:

claude mcp add --transport http --scope user publora https://mcp.publora.com/mcp \
  --header "Authorization: Bearer sk_YOUR_API_KEY"

The same entry can go in ~/.claude.json or a project .mcp.json (JSON above). Verify with the /mcp command.

Claude Desktop uses the same connectors as Claude on the web: open claude.ai/directory/publora and select Connect. There is no config file to edit.

Settings → Developer → Edit Config is only needed to run this repository locally over stdio, after cloning it and running npm install (see Local Development for how its tools differ from the hosted server):

{
  "mcpServers": {
    "publora": {
      "command": "node",
      "args": ["/path/to/mcp-server/src/stdio.js"],
      "env": {
        "PUBLORA_API_KEY": "sk_YOUR_API_KEY"
      }
    }
  }
}

Create .cursor/mcp.json in your project:

{
  "mcpServers": {
    "publora": {
      "type": "http",
      "url": "https://mcp.publora.com/mcp",
      "headers": {
        "Authorization": "Bearer sk_YOUR_API_KEY"
      }
    }
  }
}

Run your own instance:

git clone https://github.com/publora/mcp-server.git
cd mcp-server
npm install
PUBLORA_API_URL=https://api.publora.com npm start

Server runs on http://localhost:3100

The code in this repository is an April 2026 snapshot of the server. Its tool set is older: it has LinkedIn analytics and workspace tools, and lacks complete_media, delete_media, prune_media_reference, post_stats, profile_stats, linkedin_create_reshare and linkedin_list_mentionables. Use the hosted server for the current tools.

---

Available Tools (18)

The hosted server at mcp.publora.com/mcp exposes:

Posts

Media

Connections

Statistics (Mastodon and Bluesky, Pro or Premium plan)

LinkedIn Engagement

LinkedIn analytics and workspace management are available through the REST API, not MCP. Full parameters: MCP Tools Reference.

---

Example Conversations

Schedule a post:

You: Schedule "Excited about our product launch!" to LinkedIn for tomorrow 9am AI: Done! Post scheduled for tomorrow at 9am EST.

Cross-platform posting:

You: Post "We're hiring!" to all my accounts AI: Published to Twitter, LinkedIn, and Bluesky.

Check engagement (Mastodon, Bluesky):

You: How did my last Bluesky post do? AI: 42 likes, 7 reposts and 3 replies so far.

Content calendar:

You: What do I have scheduled for next week? AI: 5 posts: Mon LinkedIn, Tue Twitter+LinkedIn, Wed LinkedIn...

---

Who Is This For?

• Marketers — manage campaigns and check analytics via AI chat
• Content creators — schedule posts without switching apps
• Business owners — delegate social media tasks to AI
• Developers — integrate Publora into AI-powered workflows

---

Supported Platforms

Twitter/X · LinkedIn · Instagram · Threads · TikTok · YouTube · Facebook · Bluesky · Mastodon · Telegram

---

Authentication

Clients that support OAuth 2.1 (Claude, Claude Code, Cursor, VS Code, Codex and others) sign in through the browser — no key to copy.

Everywhere else, use your Publora API key via:

• Authorization: Bearer sk_... (recommended)
• x-publora-key: sk_...

Get your key: app.publora.com/dashboard/api

---

Verification

# Health check
curl https://mcp.publora.com/health

# Test MCP handshake
curl -X POST https://mcp.publora.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "Authorization: Bearer sk_YOUR_API_KEY" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"1.0.0"}}}'

---

Documentation

• MCP Setup Guide: docs.publora.com/guides/mcp-server
• REST API Docs: docs.publora.com
• MCP Protocol: modelcontextprotocol.io

---

Development

# Install
npm install

# Run locally
PUBLORA_API_URL=https://api.publora.com npm start

# Run tests
npm test

Environment Variables

---

Related

• Publora — Social media scheduling platform
• Publora API Docs — REST API documentation
• awesome-mcp-servers — Community MCP servers list

---

License

MIT

---

Publora — Affordable social media API starting at $5.40/month