Letmepost runs on your own machine — the client starts it, so there is no endpoint to ping. 32 installs a week from npm.
MCP server for letmepost.dev. Publish across 8 social platforms from any agent.
The linked repository no longer exists on GitHub — it was deleted or made private.
We have not read this server's code yet, 36 d ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
COPY pnpm-lock.yaml pnpm-workspace.yaml package.json .npmrc* ./
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add letmepost -e 'LMP_API_KEY=<LMP_API_KEY>' -- npx -y @letmepost/mcp
{
"mcpServers": {
"letmepost": {
"command": "npx",
"args": [
"-y",
"@letmepost/mcp"
],
"env": {
"LMP_API_KEY": "<LMP_API_KEY>"
}
}
}
}
[mcp_servers.letmepost]
command = "npx"
args = ["-y", "@letmepost/mcp"]
env = { LMP_API_KEY = "<LMP_API_KEY>" }
{
"mcpServers": {
"letmepost": {
"command": "npx",
"args": [
"-y",
"@letmepost/mcp"
],
"env": {
"LMP_API_KEY": "<LMP_API_KEY>"
}
}
}
}
{
"servers": {
"letmepost": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@letmepost/mcp"
],
"env": {
"LMP_API_KEY": "<LMP_API_KEY>"
}
}
}
}
Put your own value in place of
<LMP_API_KEY> (Your letmepost.dev API key (lmp_live_... or lmp_test_...). Create one at https://dashboard.letmepost.dev/api-keys).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
LMP_API_BASE (Override for self-hosted deployments. Defaults to https://api.letmepost.dev).
Publish to 13+ social media platforms from any AI agent via MCP.
Schedule, publish, and analyze social posts across 11 platforms from any MCP client.
Schedule, publish, and analyze social media posts across 11 platforms from any MCP client.
Schedule, cross-post, and analyze social media posts across 15 platforms from AI agents.
Draft, schedule and publish social posts to nine platforms from any AI agent.
Publish, schedule and analyze social posts across 9 platforms via the Post for Me API.
MCP server for SocialAPI — manage social media comments, DMs, reviews, and mentions across platforms
Schedule and publish social media posts to 10 platforms from your AI agent
Answers built from our own checks of this server.