Server facts
socialclaw MCP Server
Project
- Author
- ndesv21
- Repository
- github.com/ndesv21/socialclaw
- License
- Not specified
- Category
- Communication
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 96
- Last commit
- Data as of
Tags
- Youtube
- post
- schedule
- social media
- tiktok
- x
Overview
Connected accounts and provider-specific publishing rules shape SocialClaw's workflow. Agents can discover accounts, check allowed media and text limits, and begin connecting another account. Uploaded images and videos receive public URLs for use in schedules, while the media library lets agents locate assets already stored in the workspace. Publishing destinations include X, Instagram, LinkedIn profiles and pages, plus Reddit, WordPress, Discord, and Telegram.
Before posts are created, validate_schedule checks account state, media limits, provider rules, and publication times. preview_campaign shows the posts and steps a campaign would generate without creating them. Applying a schedule starts a publishing run, and idempotency keys help avoid duplicate runs when a request is retried. A person can review drafts and approve them ahead of publication. Agents can then examine run status, delivery details, and provider errors, retry failed posts, or cancel scheduled ones. Analytics snapshots cover posts, accounts, and runs; workspace tools report usage, plan consumption, and provider connection health.
socialclaw setup notes
- socialclaw records stdio only; confirm a network transport upstream before planning remote access.
- socialclaw has no recorded license; confirm reuse terms in its repository.