postlayer-connect
A local MCP server that enables AI assistants to post to social media platforms (LinkedIn, X, Bluesky, Mastodon, Reddit, etc.) using your own app credentials, with encrypted token storage and no middleman.
README
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.socialand here's an app password."
3. Post:
"Post 'hello world from my AI' to Bluesky."
That's it.
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.
| Platform | Connect with | What you register | Post analytics you get back |
|---|---|---|---|
| OAuth | LinkedIn app | likes, comments | |
| X / Twitter | OAuth 1.0a | X developer app (Read+Write) | impressions, likes, reposts, quotes, bookmarks, clicks |
| OAuth | Reddit app (type: web app) | score, comments, crossposts | |
| Mastodon | OAuth | app on your instance (Preferences → Development) | favourites, boosts, replies |
| Bluesky | App password | nothing — Settings → App Passwords | likes, reposts, replies, quotes |
| Nostr | Private key (nsec) | nothing | — (no canonical analytics) |
| Discord | Bot token | Discord app → Bot | reaction count |
| Telegram | Bot token | @BotFather | — (Bot API exposes none) |
| Threads | OAuth | Meta / Threads app | views, likes, replies, reposts, quotes |
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.
| Platform | Blocker | Flip when approved |
|---|---|---|
| Meta App Review + Business Verification | INSTAGRAM_APP_APPROVED=true |
|
| TikTok | Content Posting API audit | TIKTOK_APP_APPROVED=true |
| YouTube | Google OAuth verification (sensitive scopes) + quota | YOUTUBE_APP_APPROVED=true |
Until then these tools return an honest, specific "here's exactly what to submit" message — never a fake success.
The MCP tools
| Tool | What it does |
|---|---|
list_platforms |
Every platform, its status, the credentials it needs, and the analytics it returns. |
connect_account |
Start a connect. OAuth platforms return a URL to open in your browser; credential platforms (Bluesky, Nostr, Discord, Telegram) take the fields inline. |
list_accounts |
Show your connected accounts and their ids. |
post |
Publish text + optional media (local file path or URL) to an account. Per-platform settings (e.g. Reddit {subreddit, title}). |
get_analytics |
Normalized analytics for one post. A metric that's missing means the platform doesn't expose it — never a faked zero. |
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
postreturned) - "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.
- Register
http://localhost:8790/callbackas an authorized redirect URL in each OAuth app you create. - Call
connect_account→ it returns an authorize URL. - 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.
| Var | Purpose |
|---|---|
POSTLAYER_ENC_KEY |
Passphrase used to encrypt stored tokens (AES-256-GCM). Recommended. Generate with openssl rand -base64 32. If unset, a random key is generated once and saved (0600) in the data dir. |
POSTLAYER_DATA_DIR |
Where tokens + the key live. Default ~/.postlayer-connect. |
POSTLAYER_OAUTH_PORT / POSTLAYER_OAUTH_HOST |
Local OAuth redirect listener. Default localhost:8790. |
| Per-platform app keys | e.g. LINKEDIN_CLIENT_ID, X_API_KEY, REDDIT_CLIENT_ID, … (see .env.example). |
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.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.