Connect Codex to SocialClaw, connect your social accounts once in the SocialClaw dashboard, then ask Codex to schedule or publish. SocialClaw handles the provider-specific publish, validation, and delivery state.
Add SocialClaw to the Codex CLI as an MCP server so Codex can connect accounts, schedule posts, and inspect delivery state from your terminal.
Add SocialClaw to the Codex CLI as an MCP server so Codex can connect accounts, schedule posts, and inspect delivery state from your terminal.
SocialClaw is the hosted publishing layer; Codex stays the place you think and write.
Connect to one hosted streamable-HTTP endpoint at getsocialclaw.com/mcp, or run the stdio server with npx socialclaw mcp.
Codex can list accounts, check provider capabilities, upload media, validate, schedule, publish, retry, and pull analytics.
Authenticate with a Bearer workspace key from the SocialClaw dashboard. No per-network OAuth to rebuild.
Every scheduled or published post exposes run, attempt, and delivery state the client can read back.
The data and checks that keep the workflow grounded in current provider rules.
Connect once, then drive scheduling and publishing in plain language.
Add an MCP server entry in your Codex config (for example [mcp_servers.socialclaw]) running npx -y socialclaw mcp with SOCIALCLAW_API_KEY set, or point it at the hosted https://getsocialclaw.com/mcp endpoint.
Connect X, LinkedIn, Instagram, TikTok, or another supported network once in the SocialClaw dashboard so it can be reused across every request.
Tell Codex what to publish — for example, "schedule this thread to X and LinkedIn tomorrow at 9am" — and it calls the matching SocialClaw tools.
SocialClaw validates the payload against provider rules before apply, so bad media, missing fields, or limits are caught early.
Read back post state, attempts, and analytics from the same workspace to confirm delivery.
Important guardrails to keep the page accurate.
Pages that reinforce the same product and platform intent.
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.
Connect Codex to SocialClaw, connect your social accounts once in the SocialClaw dashboard, then ask Codex to schedule or publish. SocialClaw handles the provider-specific publish, validation, and delivery state.
Yes. The Codex CLI reads MCP server entries from its config. Add SocialClaw there and Codex can call its publishing tools.
X, LinkedIn (profile and page), Instagram (business and standalone), Facebook Pages, TikTok, YouTube, Reddit, Pinterest, WordPress, Discord, and Telegram.
Connect accounts once, validate provider specific payloads, schedule or apply work, and inspect the result from one hosted workspace.