Codex + Wahlu
Wahlu is one place for your social media, and Codex can use it too. Add Wahlu once, and Codex can turn the changes in your branch into posts for each network, upload media from your project and hold the schedule for your review.
Instagram · Facebook · TikTok · YouTube · LinkedIn personal profiles
codex mcp add wahlu --url https://mcp.wahlu.com/mcp
codex mcp login wahluThe CLI, IDE extension and app share this configuration.
It takes a couple of minutes in the Codex CLI, IDE extension and app. You sign in to Wahlu in your browser, so there's no API key to paste.
Run codex mcp add to add Wahlu. It's saved in ~/.codex/config.toml, which the Codex CLI, IDE extension and app share.
Run codex mcp login wahlu and sign in to Wahlu in the browser that opens.
Start a new Codex session so it picks up Wahlu's tools.
Checked against the Codex docs on 27 September 2026. Menus can change; if a step doesn't match what you see, follow the vendor's current instructions.
codex mcp add wahlu --url https://mcp.wahlu.com/mcp
codex mcp login wahluIn the Codex IDE extension or app you can add it from the gear menu instead: MCP servers → Add server, choose Streamable HTTP and paste the URL, then restart. Codex signs in with a Client ID Metadata Document, which is what Wahlu uses.
Connecting opens a Wahlu sign-in in your browser. You never paste a password or API key into the chat.
Continue as your Wahlu account, or switch to another one.
The agent only sees the brands you tick.
Every permission starts ticked. Untick any you don't want, such as publishing.
Remove the agent at auth.wahlu.com/connections. Your social accounts stay connected.
Example prompts and the steps to expect. These are illustrations, not recorded conversations.
Example prompt
“Summarise the changes in this branch as a short launch post for Instagram and LinkedIn. Don't schedule anything yet.”
Codex reads the diff, writes copy that suits each network and creates drafts with create_draft. Drafts don't schedule or publish anything.
Example prompt
“Schedule the launch drafts for Tuesday at 9am, held for my review, and tell me if the readiness check finds anything.”
Codex runs preflight_draft on each draft, then creates schedules at pending_review and reports any blockers.
What Codex can prepare on each network, with example prompts and each network's limits.
How your media gets to Wahlu.
The agent can read a file in your project and upload it with upload_media. Files over 8 MB, including most video, go to a short-lived upload link the agent sends the file to. Public links and your media library work too.
Every Wahlu plan includes agent access, through MCP and the API. You choose the workspace, brands and permissions each connection gets, and can disconnect it at any time.
Agents create schedules at pending_review unless you've told them to publish. A held schedule can't publish until you approve it in the Wahlu calendar.
Publish to social accounts is separate from Manage your schedule. Leave it unticked and nothing your agent schedules can go out on its own.
preflight_draft reports anything that would stop a post, such as media the network won't accept or a caption that's too long, without changing anything.
Queues, general edits to existing drafts, approvals and connecting social accounts happen in the Wahlu app, not through your agent.
Every tool, the permissions it needs and the clients that work.
Give your agent wahlu.com/connect and it follows the steps for you.
Hosted OAuth, the local package and the safety boundaries.
Codex docs: the vendor's own setup instructions.
Connect your social accounts in Wahlu, then give your agent a specific brief.