Pushwing for
Codex
Codex runs the tools from the CLI or the IDE extension; Pushwing holds the tokens. One command adds the server, one login connects it.
codex mcp add pushwing --url https://mcp.pushwing.com/mcp$ codex mcp add pushwing --url https://mcp.pushwing.com/mcp ✓ Added pushwing $ codex mcp login pushwing opens the browser… ✓ pushwing · logged in · 25 tools
Set up in three steps
Add the server
codex mcp add pushwing --url https://mcp.pushwing.com/mcpRun the command once. It writes the server to ~/.codex/config.toml.
Log in
Run codex mcp login pushwing. A browser tab opens for the Pushwing sign-in and consent screen.
Try it
Start Codex and ask: "List my connected accounts and today's publishing limits."
Codex note
The config.toml alternative: an [mcp_servers.pushwing] table with url = "https://mcp.pushwing.com/mcp". Publishing works on Codex; the ChatGPT plan caveat does not apply here.
Six prompts that work on day one
How it feels in Codex
Public actions come back as a preview. Codex shows it; you answer in the terminal.
Questions
Do I need an API key?
No. Your client signs in with OAuth. Keys exist for scripts and CI.
Can I use several channels?
Connect once per channel; Google's chooser lets you pick a different one each time.
Why are uploads private?
YouTube's rule for API projects that haven't passed its audit. Ours is pending.
How do I disconnect?
Dashboard → Connections → Disconnect; it revokes at Google.
Publish from Codex.
Join the waitlist. We’ll email you when your invitation is ready.