# letmepost [Health: Active]

**Category:** 🌐 Social Media  
**Repository:** https://github.com/letmepost/letmepost.dev  
**GitHub Stars:** 1  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/letmepost

## Description
MCP server for letmepost.dev. Publish across 8 social platforms from any agent.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "letmepost": {
    "url": "https://api.letmepost.dev/v1/posts"
  }
}
```

## Documentation

## What letmepost MCP server does

The letmepost MCP server connects an agent to letmepost.dev's social publishing API. It provides an agent-facing way to publish posts to Bluesky, X, Pinterest, LinkedIn, Threads, Instagram, Facebook Pages, and TikTok. YouTube is listed as planned rather than live, so it should not be treated as an available publishing target.

Posts use a common request model with target account IDs and post content. The underlying API is designed to send one publishing request across selected connected accounts instead of requiring separate platform-specific API calls. Account connections are created through letmepost.dev, and the service returns account identifiers for later publishing requests.

## How it works

An agent sends a post request through the MCP server to letmepost.dev. The service validates platform-specific requirements before calling an upstream social API. These checks can cover text length, media rules, account or URN formats, OAuth scopes, audit states, and platform quotas. A request can therefore fail before an external platform call when its content or account configuration is invalid.

The letmepost MCP server relies on letmepost.dev's unified error shape. Failures include a stable error category, the rule that failed, the affected platform, the raw platform response, and a remediation hint. Error categories include preflight failures, authentication failures, platform rejection, platform unavailability, and rate limiting. This gives an agent structured information for deciding whether to revise content, reconnect an account, or retry later.

Writes accept an Idempotency-Key. Reusing the key for a retry is intended to prevent duplicate posts when a worker or agent is interrupted during publication.

## Setup and configuration

Start by creating an account and obtaining an API key from the letmepost.dev dashboard. Connect a supported social account through the account-connection endpoint or the corresponding service flow, then use the returned account ID as a publishing target. The documented API examples authenticate with a bearer token and send JSON requests to the letmepost.dev API.

Installation details should therefore be taken from the repository or the linked quickstart rather than inferred from this listing.

## Tools and capabilities

The service supports these live publishing destinations:

- Bluesky
- X / Twitter
- Pinterest
- LinkedIn
- Threads
- Instagram
- Facebook Pages
- TikTok

Platform behavior remains specific even though the request interface is unified. Examples include Bluesky's grapheme limit, X media and thread rules, Pinterest's board requirement, LinkedIn's posting scopes, and TikTok's inbox-upload flow. TikTok's supported flow uploads content to the creator's inbox for confirmation; direct publishing without that confirmation is not implemented.

The letmepost MCP server is most suitable for agents that need to publish content, handle predictable validation errors, and retry writes safely. It is less suitable when the required destination is YouTube, Reddit, Telegram, Discord, Snapchat, Google Business, or WhatsApp, which are not available in the stated v1 support set.

## Limitations and notes

Platform access still depends on each network's authentication, permissions, quotas, and review requirements. LinkedIn organization publishing remains MDP-gated, and YouTube production access is tied to CASA verification. TikTok's current implementation uses the Upload track rather than Direct Post.

The material provided does not document the MCP tool names, supported clients, transport options, or local server runtime. Confirm those details in the repository before selecting a deployment method. The underlying letmepost.dev project is licensed under Apache-2.0.

_Full upstream README: https://allmcps.com/mcp/letmepost/readme_