Social Media Api
Let your agent read and act on Facebook, Instagram, TikTok, and other networks through one SocialAPIs key instead of wiring each platform SDK by hand.
Overview
SocialAPIs social-media-api is a Grow-phase MCP server that connects AI agents to a unified Facebook, Instagram, TikTok, and multi-network API behind one API key.
What is this MCP server?
- Unified SocialAPIs surface for Facebook, Instagram, TikTok, and additional networks
- stdio npm package @socialapis/mcp with optional MCP_PROXY_URL defaulting to mcp.socialapis.io
- Required SOCIALAPIS_API_KEY from socialapis.io dashboard
- Built for AI agents that automate social workflows from the IDE
- Version 1.0.1 registry entry with GitHub source at SocialAPIsHub/mcp-server
- Registry version 1.0.1 for package @socialapis/mcp
- Required secret environment variable SOCIALAPIS_API_KEY
- Documented platforms include Facebook, Instagram, and TikTok with more via unified API
Community signal: 1 GitHub stars.
What problem does it solve?
Every social network wants its own OAuth app and SDK, which slows indie builders who just need one agent-driven path to post and read social data.
Who is it for?
Founders running multi-channel content, community tools, or growth automation who already use SocialAPIs and want MCP access from Claude Code or Cursor.
Skip if: Builders in pure research phase with no accounts, or teams that refuse third-party social API proxies and need only official single-platform APIs.
What do I get? / Deliverables
After you set SOCIALAPIS_API_KEY and register @socialapis/mcp, your agent can call SocialAPIs-backed tools for cross-platform social workflows from your dev environment.
- Agent-invokable unified social media API operations across supported networks
- Configurable proxy routing via MCP_PROXY_URL (default https://mcp.socialapis.io)
- Stdio MCP wiring ready for local agent sessions
Recommended MCP Servers
Journey fit
Social posting and cross-network ops sit in Grow because builders use it after launch to run content, engagement, and lifecycle automation. Content is the right shelf for a unified social API MCP aimed at publishing, monitoring, and multi-channel workflows.
How it compares
Unified social API MCP bridge, not a copywriting skill or SEO audit checklist.
Common Questions / FAQ
Who is SocialAPIs social-media-api for?
Solo builders and small teams automating Facebook, Instagram, TikTok, and related networks through AI agents with a single SocialAPIs subscription.
When should I use SocialAPIs MCP?
Use it in Grow when you are executing content, engagement, or lifecycle flows and want your coding agent to call social endpoints without hand-rolling each platform integration.
How do I add SocialAPIs to my agent?
Create an API key at socialapis.io/dashboard, set SOCIALAPIS_API_KEY (and optional MCP_PROXY_URL), then add the @socialapis/mcp stdio server to your MCP client config.