Posthive MCP Server

MCP server for Posthive — schedule posts to 11 social platforms from Claude, Cursor, Windsurf, or any MCP-compatible AI agent. That is what the posthive mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

The agentic social media scheduling platform with built-in AI agent support.

• Multi-platform posting — - write once, publish to 14+ platforms simultaneously
• AI agent support — - connect Claude, ChatGPT, Cursor, VS Code via MCP; OAuth 2.0 + PKCE, no API key to paste
• Calendar view — - FullCalendar month/week/day with drag-to-reschedule
• Bulk CSV scheduling — - upload a spreadsheet to schedule hundreds of posts at once
• Post templates — - save and reuse post drafts
• First comment scheduling — - auto-reply immediately after the post goes live

The tools it exposes

The server publishes 14 tools. What each one is for:

• Multi — platform posting** - write once, publish to 14+ platforms simultaneously
• Per — platform overrides** - custom text and first comment per account
• Self-hostable — Docker compose, one command, billing optional
• Layer — Technology
• Frontend — Next.js 16 (App Router), React 18, Tailwind CSS
• Backend — Fastify v4, TypeScript ESM, Node.js
• Database — Prisma 5 + Postgres
• Queue — BullMQ + Redis (Upstash / Railway)
• Storage — Local disk (dev) / Supabase Storage (prod)
• Email — Resend
• Billing — Dodo Payments (optional)
• Monitoring — Sentry

What it needs from you

Configuration is passed through the environment: ENCRYPTION_KEY, DATABASE_URL, REDIS_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Posthive's toolset — Multi, Per, Self-hostable and 11 more — is a fair guide to whether it matches your workflow. It is maintained by guna_a; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Posthive's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Posthive.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.