@alfe.ai/social-mcp
v0.2.26
Published
Social MCP server — post, engage, and read on connected social accounts (Bluesky today; X / Meta / Threads / LinkedIn / Pinterest / TikTok / Reddit / YouTube on the approval-gated roster) via Alfe Connect credentials (Pattern A multi-account, provider sel
Readme
@alfe.ai/social-mcp
Social MCP server — lets agents post, engage, and read on their connected social accounts (Bluesky today; X / Meta / Threads / LinkedIn / Pinterest / TikTok / Reddit / YouTube on the approval-gated roster) using Alfe Connect credentials. Pattern A multi-account; the platform is selected via --provider.
Part of Alfe — the operating system for AI agents: build, deploy, and run agents with persistent memory, identity, integrations, and channels. See the documentation to get started.
Install
npm install @alfe.ai/social-mcpUsage
npx @alfe.ai/social-mcp --provider blueskyThe server starts even when the agent has no connected Bluesky account, so
social_list_accounts can explain the empty state. Every other tool requires
an explicit account selector returned by that discovery call.
Runtime boundaries
- Provider selection accepts exactly
--provider bluesky,--provider=bluesky, or the positionalblueskyform. - Bluesky PDS endpoints must be clean HTTPS origins. The driver rejects IP literals and reserved hostnames, then resolves and rejects private or reserved addresses immediately before each request. XRPC redirects are rejected so bearer requests cannot escape the validated origin.
- Provider bodies and model-facing tool results have byte ceilings. Provider exception bodies are never returned to the model.
- Delete accepts only an exact
app.bsky.feed.postAT URI owned by the selected account; a foreign-author URI is rejected before the PDS call. - Importing the package is inert. Signal handlers are installed only while the executable is running and close the MCP server before the process exits.
Links
- 🌐 Website: https://alfe.ai
- 📚 Docs: https://docs.alfe.ai
