Use your own Monthly account. Keep accounts:read and posts:read selected; leave drafting/media and scheduling/cancellation off. Select only your intended accounts.
03
Check your connection
Ask Codex to list the accounts this Monthly connection can access. The result should match your selection. No post needs to be created or published.
No API token or shared client secret is needed for this OAuth flow.
Detailed setup & compatibility notes
Use your installed Codex CLI and your existing Monthly account. OAuth opens Monthly in your browser; no API token or shared client secret is needed.
Run the commands above. If monthly already exists, inspect it with codex mcp get monthly instead of adding a duplicate. The login command pins this connection to the two read permissions.
02
Keep the connection read-only
Sign in to your own Monthly account. On the consent page, keep the two read permissions selected and choose only your own accounts that you intend to share. Allow selected access, then return to the terminal. You do not need access to Monthly’s test account.
03
Save the read-only defaults
In ~/.codex/config.toml, merge the fields below into the existing monthly entry. Preserve other servers. The tool allowlist adds a client-side limit; Monthly enforces the OAuth scope and selected accounts.
04
Verify in Codex
Start a fresh Codex session and inspect /mcp. Send the read-only check below. The result must show only your selected account. No draft, upload or schedule is part of this setup.
Leave the advanced OAuth resource override unset so Codex uses Monthly’s discovery. If using --no-browser, paste the complete return URL only into your own waiting Codex terminal, never into a conversation or configuration file.
Client instructions checked October 26, 2026. Codex MCP documentation. Production Codex OAuth and four direct read-tool checks passed on October 26 through the installed client, with only @TryMonthly and accounts:read/posts:read. No model turn or write tool was used. Drafting, scheduling and client revocation/reconnection remain unverified.
A conversation starter
Things you can ask Codex
Copy a prompt after connecting Monthly, or open it in Codex with one click — automatically typed in, waiting for you to press Enter. Opens the desktop app. Install it and connect Monthly there first; your browser may ask you to confirm opening it.
Your accounts, at a glance.
See exactly which accounts this connection can access.
Use Monthly to show the social accounts I’ve allowed this connection to access and which are ready to publish. Read only; don’t create or schedule anything.
Yes. Connect your social accounts in Monthly, then sign in to your own Monthly account during your agent’s OAuth flow. Each customer gets their own scoped connection; you never use another customer’s login or social credentials.
What can my agent see?
Only the accounts you select during consent and the permissions you allow. Post reads are limited to posts created by that same connection. Your social access tokens and passwords stay in Monthly.
Can it publish without my approval?
The read-only setup on this page cannot create or schedule posts. If you later grant drafting and scheduling permissions, every exact draft revision still needs your approval inside Monthly before it can be scheduled. Editing a draft clears its approval.
Do I need an API key?
Compatible MCP clients use OAuth sign-in and automatic client registration. You do not need to copy a Monthly API token or a shared client secret. Your agent’s account or subscription requirements are separate.
Why does the agent need me to sign in again?
A client may need to renew authorization or reconnect an expired account. Use the normal sign-in flow and check the permissions again. Never disable authentication or share a social password with an agent.
How do I disconnect an agent?
Open Monthly Settings → AI agents & API and revoke that connection. Revocation stops further agent actions. It does not cancel posts already in your queue; review those separately.