Letmepost

io.github.rosekamallovePublished by GitHub account rosekamallovev0.2.1Updated Oct 24, 2026

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

VerifiedSTDIODesktop onlyCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

Lets an assistant publish and schedule posts across eight social platforms, and manage media, accounts, webhooks and API keys through letmepost.dev.

What you can do
An MCP server for letmepost.dev whose tool surface is generated from the service's OpenAPI spec at startup, so documented endpoints are reachable without bespoke wrappers. Tools follow a method_path naming scheme and cover publishing or scheduling a multi-target post that fans out to up to 25 connected accounts, listing and fetching posts with cursor pagination, listing media, reading and disconnecting platform accounts, driving the account connect handshake, managing Pinterest boards, minting, listing and revoking API keys, and managing outbound webhook endpoints. Each tool's input schema merges path, query and body fields into one flat object, and idempotency keys are auto-injected on…
When to use it
Worth adding when an assistant should publish or schedule social posts across several platforms, inspect past posts and their publish attempts, or administer letmepost.dev resources such as connected accounts, webhooks and API keys from within an agent workflow.
Requirements
Runs locally over stdio, typically via npx @letmepost/mcp, so Node.js is needed. Requires a letmepost.dev API key supplied as the LMP_API_KEY environment variable; the optional LMP_API_BASE variable overrides the default API endpoint for self-hosted deployments. Network access to the letmepost.dev API is required.
Before you install
The server holds a bearer API key (LMP_API_KEY) that can publish content and manage accounts, webhooks and API keys, so treat it as sensitive. Tools can write, schedule, disconnect accounts and delete resources such as API keys and webhook endpoints. Media upload is multipart-only and not exposed through this JSON-only MCP surface. Self-hosting is described as bypassing platform approval gates and using your own credentials.

Installation

In SourceWeft

  1. Open Letmepost in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@letmepost/mcp

MCP server for letmepost.dev. Lets AI agents drive the full publishing API — posts, media, accounts, webhooks, API keys — through one MCP connection. The tool surface is generated from the canonical OpenAPI spec at startup, so every documented endpoint is reachable without a bespoke wrapper.

Install

sh
npx @letmepost/mcp

Or wire it into Claude Code:

sh
claude mcp add letmepost npx @letmepost/mcp --env LMP_API_KEY=lmp_live_...

Cursor / Cline / any MCP client:

json
{  "mcpServers": {    "letmepost": {      "command": "npx",      "args": ["@letmepost/mcp"],      "env": { "LMP_API_KEY": "lmp_live_..." }    }  }}

Configuration

VariableRequiredDefaultDescription
LMP_API_KEYyes—Bearer token from https://dashboard.letmepost.dev
LMP_API_BASEnohttps://api.letmepost.devOverride for self-hosted deployments

Tools

Tool names follow {method}_{path} with {param} segments rewritten as by_{param}. The current surface, generated from the OpenAPI spec:

  • post_v1_posts — Publish or schedule a multi-target post. One call fans out to up to 25 connected accounts.
  • get_v1_posts — List posts with cursor pagination, filterable by platform, status, error code, and time window.
  • get_v1_posts_by_id — Fetch a single post with all its publish attempts.
  • get_v1_media — List uploaded media. (Upload itself is multipart-only and exposed via the REST API; the MCP surface stays JSON-only.)
  • get_v1_accounts, get_v1_accounts_by_id, delete_v1_accounts_by_id — Read and disconnect platform accounts.
  • post_v1_accounts_connect_by_platform, post_v1_accounts_connect_by_platform_complete — Drive the connect handshake.
  • get_v1_accounts_by_id_pinterest_boards, post_v1_accounts_by_id_pinterest_boards, patch_v1_accounts_by_id_pinterest_default_board — Pinterest board lifecycle.
  • post_v1_api_keys, get_v1_api_keys, delete_v1_api_keys_by_id — Mint / list / revoke API keys.
  • post_v1_webhook_endpoints, get_v1_webhook_endpoints, get_v1_webhook_endpoints_by_id, patch_v1_webhook_endpoints_by_id, delete_v1_webhook_endpoints_by_id, post_v1_webhook_endpoints_by_id_test — Outbound webhook management.

Each tool's inputSchema is a flat JSON schema with path / query / body fields merged into one object — the agent doesn't need to know which slot a field lives in. Idempotency keys are auto-injected on writes.

Self-host

Self-host bypasses every platform approval gate. Bring your own credentials, every platform works the day you clone the repo. See docs.letmepost.dev/self-host/quick-start.

License

Apache 2.0.

Source: apps/mcp/README.md at commit ab3b970

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts