

Let your agent publish to Discord. Connect the hosted MCP server once, then ask Claude, ChatGPT, or Cursor to schedule the post for you.
claude mcp add socialclaw \
--env SOCIALCLAW_API_KEY=sc_live_your_key \
-- npx -y socialclaw mcp
{
"mcpServers": {
"socialclaw": {
"command": "npx",
"args": ["-y", "socialclaw", "mcp"],
"env": {
"SOCIALCLAW_API_KEY": "sc_live_your_key"
}
}
}
}
Claude, ChatGPT, or Cursor can list your accounts, upload media, validate a schedule, and publish it, all through the same MCP tools your dashboard uses.
list_accountsList connected social accounts, optionally filtered by provider.
upload_assetUpload a local image or video; returns a hosted media URL.
validate_scheduleValidate a schedule against provider rules before publishing.
apply_scheduleCreate a publishing run with idempotency-key deduplication.
get_postInspect one post's delivery state and provider identifiers.
retry_postRetry a failed post.
Simply install the skill with this command




Every post lands in the same place a person scheduling by hand would use.
Upload an image or a video once and reuse it across every scheduled Discord post. SocialClaw hosts it for you, so Discord always has what it needs the moment your post goes out.
Same workspace, same connected account, on whichever surface fits what you are building.
Schedule and manage Discord posts visually. No code required.
Use with APIPublish to Discord from your own backend with a workspace key. Full reference for request payloads, media, and error handling.
Use with CLISchedule Discord posts from a terminal, a cron job, or CI with npx socialclaw.
Real quotes from Reddit, G2, Trustpilot, and Instagram.
“I can prepare the content once and let SocialClaw handle the distribution.”
“If SocialClaw sees this just know you changed my entire workflow girl.”
“Since I try market my iOS apps, definitely SocialClaw… because then Claude can post to social media for me.”
“Most schedulers still feel like old calendar tools with an AI caption button added on top. SocialClaw feels more built around the newer AI era.”
“SocialClaw if you want to schedule posts to social media.”
“SocialClaw handles the repetitive publishing work: uploading media, managing connected accounts, scheduling posts, publishing them, and retrying when something fails.”
“I used to use stuff like Buffer etc, but I use SocialClaw with my AI agent. I just tell it to schedule like 100 videos for the next month.”
“It has an OpenClaw skill, or use it via API, CLI, or even the web dashboard.”
“I have it install the SocialClaw skill, linked my social media accounts, and it actually has approval to post on my socials for me.”
Connect once, then schedule and publish everywhere from the same workspace.
List your connected accounts, upload media, validate a schedule against Discord's rules, publish it, and check whether it actually went live, all through tool calls instead of a chat message you have to interpret yourself.
Create a workspace API key in your dashboard, then add SocialClaw as a connector. On claude.ai that means Settings, Connectors, Add custom connector, with the key in the server URL. In Claude Code, one command with the key as an environment variable does it.
No. The toolset is validation first. An agent calls validate_schedule before apply_schedule, so a badly formed post gets caught before anything is scheduled, not after.
Any MCP client. Claude on claude.ai, Claude Code, Claude Desktop, ChatGPT, and Cursor all connect the same way, over the hosted server or a local one from the socialclaw npm package.
Yes. The agent uses the same workspace and the same connected accounts as your dashboard, so you can schedule a post yourself one day and hand it to an agent the next, with nothing to keep in sync.
SocialClaw retries automatically when the failure is temporary. If it still cannot go out, it shows up flagged, and the agent, or you, can call retry_post once the cause is fixed.
Every tool, parameter, and client setup snippet is documented at /docs/mcp, generated from the same tool registry the server itself exposes.