postlayer-connect

Let your AI post to your socials — an open MCP server for LinkedIn, X, Bluesky, Mastodon, Reddit, and more.

postlayer-connect is a local Model Context Protocol server. Point any MCP client at it — Claude Desktop, Claude Code, Cursor, ChatGPT desktop — connect your social accounts with your own app credentials, and your assistant can publish posts and read analytics for you.

• Runs 100% locally. Your tokens never leave your machine.

• Uses your developer apps and your accounts. No middleman API, no per-post fees.

• Tokens are encrypted at rest (AES-256-GCM) in a local file.

• MIT licensed. Fork it, audit it, extend it.

you: "post this to LinkedIn and X: shipping day. the open MCP social server is live 🚀"
AI:  ✅ posted to linkedin (id 7…)   ✅ posted to x (id 18…)

30-second quickstart

1. Add it to your MCP client. No install step — npx fetches and runs it.

Claude Desktop / Claude Code — add to your claude_desktop_config.json (or .mcp.json):

{
  "mcpServers": {
    "postlayer-connect": {
      "command": "npx",
      "args": ["-y", "postlayer-connect"],
      "env": {
        "LINKEDIN_CLIENT_ID": "your_id",
        "LINKEDIN_CLIENT_SECRET": "your_secret"
      }
    }
  }
}

Only add the credentials for the platforms you want. Bluesky and Nostr need none — you connect them with an app password / key. The server boots fine with an empty env and tells you what each platform needs.

2. Restart your client and ask it to connect an account:

"List the social platforms postlayer supports." "Connect my Bluesky — my handle is you.bsky.social and here's an app password."

3. Post:

"Post 'hello world from my AI' to Bluesky."

That's it.

Related MCP server: Outpost

Supported platforms

Works now — register your own app (a 5-minute, free, self-serve process), paste the keys, done. Bluesky and Nostr need no app at all.

Threads works for you + testers in dev mode. Scaling it to other people's accounts needs Meta App Review.

Needs your own approved app — the connector code is complete and correct, but these platforms only allow programmatic posting through a developer app that has passed their review. Get your app approved, flip one env flag, and it works.

Until then these tools return an honest, specific "here's exactly what to submit" message — never a fake success.

The MCP tools

Example prompts

• "Post this to LinkedIn and X, and attach ~/Desktop/launch.png."

• "Submit this as a text post to r/SideProject with the title 'I built an open MCP social server'."

• "How did my last LinkedIn post do?" (feed it the post id post returned)

• "Connect my Mastodon on mastodon.social."

How the OAuth connect works (local)

Because this server runs locally with no public URL, it starts a tiny loopback listener to catch the OAuth redirect.

1. Register http://localhost:8790/callback as an authorized redirect URL in each OAuth app you create.

2. Call connect_account → it returns an authorize URL.

3. Open it, approve, and the browser redirects back to the local listener, which exchanges the code and saves the account automatically.

Change the port with POSTLAYER_OAUTH_PORT (and POSTLAYER_OAUTH_HOST) if 8790 is taken — just register the matching URL.

Configuration

Set these in your MCP client's env block, or in a .env file in the working directory (auto-loaded). See .env.example for the full list.

Where your tokens are stored

Connected-account tokens are written to ~/.postlayer-connect/tokens.json. The secret fields (access + refresh tokens, app passwords, signing keys) are encrypted at rest; the file is created 0600. Nothing is ever sent anywhere except directly to the platform's own API.

Run it yourself / develop

git clone https://github.com/<you>/postlayer-connect
cd postlayer-connect
npm install
npm run build
node dist/index.js   # boots on stdio, prints its status to stderr

Node 20+. The server speaks MCP over stdio, so run it through an MCP client rather than typing at it directly.

Want it fully managed + learning what works for you?

postlayer-connect is the open, run-it-yourself core. If you'd rather not manage apps and tokens — and want a system that schedules, approves, and learns which posts actually perform — that's Postlayer.

License

MIT © 2026 Chris Poka / Designpulse. See LICENSE.