AI client integration

Publish to social media from Codex with SocialClaw.

Add SocialClaw to the Codex CLI as an MCP server so Codex can connect accounts, schedule posts, and inspect delivery state from your terminal.

Start free View pricing

Why Codex works with SocialClaw

SocialClaw is the hosted publishing layer; Codex stays the place you think and write.

Transport Hosted MCP, zero install Connect to one hosted streamable-HTTP endpoint at getsocialclaw.com/mcp, or run the stdio server with npx socialclaw mcp.

Tools 17 publishing tools Codex can list accounts, check provider capabilities, upload media, validate, schedule, publish, retry, and pull analytics.

Auth One workspace API key Authenticate with a Bearer workspace key from the SocialClaw dashboard. No per-network OAuth to rebuild.

State Inspectable after publish Every scheduled or published post exposes run, attempt, and delivery state the client can read back.

Inputs and requirements

The data and checks that keep the workflow grounded in current provider rules.

A SocialClaw workspace API key (dashboard → Developers → Public API).
At least one connected social account in the workspace.
Post content, target account, timezone, and publish time.
Media uploaded to SocialClaw when the network requires it.
Validation run before apply so provider rules are checked first.

Connect Codex in a few steps

Connect once, then drive scheduling and publishing in plain language.

Step 1

Add SocialClaw to Codex

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.

Step 2

Connect a social account

Connect X, LinkedIn, Instagram, TikTok, or another supported network once in the SocialClaw dashboard so it can be reused across every request.

Step 3

Ask in plain language

Tell Codex what to publish — for example, "schedule this thread to X and LinkedIn tomorrow at 9am" — and it calls the matching SocialClaw tools.

Step 4

Validate before publishing

SocialClaw validates the payload against provider rules before apply, so bad media, missing fields, or limits are caught early.

Step 5

Inspect the result

Read back post state, attempts, and analytics from the same workspace to confirm delivery.

Constraints to know

Important guardrails to keep the page accurate.

Publishing requires an active SocialClaw plan; unauthenticated clients can still list tools but not publish.
Each network keeps its own rules — media type, account model, and limits still apply after the client hands off the request.

Related routes

Pages that reinforce the same product and platform intent.

MCP

SocialClaw MCP server Hosted and stdio MCP, tools, and auth

Docs

API documentation Endpoints, schemas, and examples

Use case

AI agent use case Agent-native publishing overview

API

Scheduling API Connect, validate, schedule, inspect

Frequently asked questions

How do I let Codex post to my social accounts?

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.

Does Codex support MCP servers?

Yes. The Codex CLI reads MCP server entries from its config. Add SocialClaw there and Codex can call its publishing tools.

Which networks are supported?

X, LinkedIn (profile and page), Instagram (business and standalone), Facebook Pages, TikTok, YouTube, Reddit, Pinterest, WordPress, Discord, and Telegram.

Use SocialClaw for Codex social media integration

Connect accounts once, validate provider-specific payloads, schedule or apply work, and inspect the result from one hosted workspace.

Start free Browse workflows