# posteverywhere/mcp [Health: Active]

**Category:** 🌐 Social Media  
**Repository:** https://github.com/posteverywhere/mcp  
**GitHub Stars:** 3  
**npm Downloads (last month):** 1021  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/posteverywhere-mcp

## Description
Hosted MCP server to schedule and publish across 11 social platforms (Instagram, LinkedIn, TikTok, X, YouTube, Facebook, Threads, Pinterest, Bluesky, Discord, Telegram). 32 tools covering posts, campaigns, bulk operations, media, analytics, webhooks, and AI captions. Connect with one URL, or run locally via npx -y @posteverywhere/mcp.

## Tools
Capabilities this server exposes over MCP:

- **list_accounts** — list all connected social accounts and their health status
- **get_account** — get details for a specific account (token expiry, can-post status)
- **list_posts** — list posts filtered by status (`scheduled`, `published`, `failed`, `draft`) or platform. Drafts include their target accounts + per-platform content so you can review them before publishing.
- **get_post** — get full details for a single post including all destinations (for drafts, the saved accounts + per-platform content)
- **create_post** — publish now, schedule for later, **or save as a draft for human review** (`draft: true`)
- **schedule_post** — publish or schedule a **draft** (the approval step — pass `scheduled_for`, or `publish_now: true`)
- **update_post** — modify a scheduled or draft post (content, schedule time, accounts)
- **delete_post** — delete a scheduled or draft post
- **get_post_results** — per-platform publishing results, errors, and live URLs
- **retry_failed_post** — retry every failed destination of a post
- **list_media** — list files in your media library
- **get_media** — get media file details and processing status
- **upload_media_from_url** — import an image from any public URL into the library (one call, returns a `media_id` ready for `create_post`)
- **delete_media** — remove a media file
- **generate_image** — generate an image from a text prompt (4 models, 7 aspect ratios)

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "mcp": {
    "command": "npx",
    "args": ["-y","@posteverywhere/mcp"],
    "env": {
      "POSTEVERYWHERE_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `POSTEVERYWHERE_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What posteverywhere/mcp MCP server does

The posteverywhere/mcp MCP server exposes PostEverywhere’s social publishing workflow to MCP clients. It can work with connected accounts on Instagram, LinkedIn, TikTok, X, YouTube, Facebook, Threads, Pinterest, Bluesky, Discord, and Telegram, as listed by the project description.

Agents can inspect account health and account-level details, including token expiry and whether an account can publish. Post tools support immediate publication, future scheduling, draft creation, edits, deletion, status filtering, and retrieval of per-platform results. Publishing results can include destination-specific errors and live URLs.

Drafts provide an approval workflow. An agent can save content without publishing it, retrieve drafts and their platform-specific content, and later schedule or publish an approved draft. This is useful when generated content needs review before it reaches any social account.

## How it works

The package communicates with an MCP-compatible client through a standard local stdio process. The client starts the npm package, and the process uses the `POSTEVERYWHERE_API_KEY` environment variable to authenticate with PostEverywhere. The README also describes a hosted connection option, but the package setup shown for Claude Desktop and Cursor uses the local npm process.

A typical workflow begins by listing connected accounts, then creating either a post or a draft. Scheduled and draft posts can be updated or deleted. If publication fails for some destinations, the agent can inspect the individual results and retry failed destinations. Platform filtering and status filters help an agent find scheduled, published, failed, or draft content.

Media operations use the PostEverywhere library. Existing files can be listed, inspected, or removed. A public image URL can be imported in one call; the returned media identifier can then be supplied when creating a post. The image-generation tool accepts a text prompt and supports four models and seven aspect ratios.

## Setup and configuration

Create a PostEverywhere account, connect the social accounts to use, and create an API key from the developer settings. The README identifies read, write, and AI scopes: read access covers accounts, posts, and media; write access covers post and media changes; and AI access covers image generation.

For a local installation, configure an MCP client to run:

```bash
npx -y @posteverywhere/mcp
```

Set `POSTEVERYWHERE_API_KEY` in the client environment. Claude Desktop and Cursor examples use the package above with the API key in an `env` block. The project also states that Claude Code, Claude Desktop, ChatGPT through the hosted connector, Cursor, OpenAI Codex, and other MCP-compatible clients can use the service, although this directory entry provides client-specific configuration for Claude Desktop and Cursor.

## Tools and capabilities

The listed tools include:

- Account listing and account health inspection.
- Post creation, scheduling, approval, updating, deletion, and retrieval.
- Status- and platform-filtered post listing.
- Per-destination publication results and failed-destination retries.
- Media library listing, inspection, URL import, and deletion.
- AI image generation with prompt, model, and aspect-ratio options.

## Limitations and notes

The posteverywhere/mcp MCP server requires a PostEverywhere API key and connected social accounts; the MCP package does not itself establish those accounts. Platform availability and publishing status are exposed through PostEverywhere, so an account may report that it cannot currently publish or that its token is nearing expiry.

The supplied setup documents a local stdio server rather than a self-contained social network connector. Drafts remain unpublished until a later scheduling or publish action. The README points to separate API documentation for complete tool parameters and to a separate Node SDK for programmatic integrations.

_Full upstream README: https://allmcps.com/mcp/posteverywhere-mcp/readme_