Image MCP Server

Image MCP Server is a marketing tool. PostMCP AI writes, schedules and publishes posts to LinkedIn, X, Instagram, Facebook, Threads, Bluesky and YouTube Shorts. It works from a web dashboard or through an open-source MCP server used by Claude, ChatGPT and Cursor, with approval before every publish.

PostMCP AI is a social media management service that drafts, schedules and publishes posts across seven networks: LinkedIn, X, Instagram, Facebook, Threads, Bluesky and YouTube Shorts. A single idea is turned into a separate version for each network, with tone, length and format adjusted to suit it. Nothing goes live without approval, so automatic publishing stays supervised. In practice, accounts are connected once through each platform's official OAuth sign-in. From there, posts can be written in the web composer, or requested in plain English from an AI assistant such as Claude, ChatGPT or Cursor. The assistant reaches the service through an open-source MCP server under the MIT license, started with an npx command and exposing 17 tools for creating, scheduling, publishing, retrying and reading the queue. Browser-based clients like Claude.ai and ChatGPT connect to a hosted copy over HTTPS, and a REST API covering the same networks allows publishing to be wired into other products or automations. Drafting inside a user's own AI over MCP does not consume credits. The web workspace adds a shared visual calendar with drag-to-reschedule, team roles (owner, admin, scheduler, visitor) and invitations by email. Brand voice is set through the AI's own instructions so drafts stay consistent. Analytics are read on demand per post or per profile, covering views, likes, comments and shares, and the same figures can be requested by an agent. A companion app for iOS and Android, currently in beta through TestFlight and Google Play, provides the queue, alerts and AI drafts on a phone. Usage is metered in credits: publishing, AI drafts, analytics reads and generated images each draw from a monthly balance. PostMCP sits between conventional schedulers and developer-oriented publishing APIs. Its distinguishing angle is agent-first control, which suits creators, small teams and developers who already work inside an AI assistant and want publishing to be one more tool it can call.