Claude Code + MonthlyBring your Monthly accounts, publishing formats and post status into Claude Code. One connection. Only the access you choose.
Claude Code 
MonthlyWhich of my connected accounts are ready for my next post?
Your selected X account is ready.
Connect your social accounts in Monthly first. Then add Monthly to the agent you already use.
Run the commands below in PowerShell, Bash or zsh. They request only account and connection-created post reads. Your Claude Code account access is separate from Monthly.
https://app.monthly.so/mcpclaude mcp add-json --scope user monthly '{"type":"http","url":"https://app.monthly.so/mcp","oauth":{"scopes":"accounts:read posts:read"}}'
claude mcp login monthlyUse your own Monthly account. Keep accounts:read and posts:read selected; leave drafting/media and scheduling/cancellation off. Select only your intended accounts.
Ask Claude Code to list the accounts this Monthly connection can access. The result should match your selection. No post needs to be created or published.
Claude Code testing is paused. The pilot account requires Max or Pro for a model conversation; Monthly’s MCP connection itself is already healthy.
Claude Code is a separate connection from Claude on the web. Use an installed Claude Code CLI and sign in to the Claude account your organization permits. Model access and any client subscription are separate from Monthly.
https://app.monthly.so/mcpclaude mcp add-json --scope user monthly '{"type":"http","url":"https://app.monthly.so/mcp","oauth":{"scopes":"accounts:read posts:read"}}'
claude mcp login monthlyRun the commands above in your terminal. The single-quoted JSON works in PowerShell, Bash and zsh. If monthly already exists, inspect it first rather than replacing other MCP servers. User scope keeps the entry outside your repository.
The oauth.scopes value requests accounts:read and posts:read only. Sign in to your own Monthly account, keep those two reads and select only your own accounts that you intend to share. Monthly’s test account is not part of your setup.
Choose Allow selected access and return to Claude Code. For a headless terminal, use claude mcp login monthly --no-browser and paste the complete return URL only into that waiting terminal.
Open /mcp in Claude Code and confirm Monthly is connected. Run the read-only check below and approve only the read tools. Do not approve drafting, media, scheduling or cancellation tools for this setup.
Client instructions checked October 26, 2026. Claude Code MCP documentation. Production Claude Code OAuth passed on October 26 with only @TryMonthly and accounts:read/posts:read. Claude Code’s own MCP health check reports Connected. A model-driven read-tool conversation remains unverified: Anthropic’s sign-in page requires Max or Pro for the current pilot account. No subscription upgrade or API billing was started.
Claude CodeCopy a prompt after connecting Monthly, or open it in Claude Code 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.
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.
Know what needs reconnecting before you begin.
Check my selected Monthly accounts for connection issues. Tell me which need reconnecting and what to do next. Don’t change anything.
Check text lengths, image limits and supported formats.
Which formats can my selected Monthly accounts use? Show text lengths, image limits and file sizes. Read only; don’t upload or create anything.
Bring connection-created drafts back into view.
Show drafts created by this Monthly connection with their review links and approval status. Don’t edit, approve or schedule anything.
Read actual delivery status, without guessing.
Did posts created by this Monthly connection publish? Show their observed status and any delivery receipt IDs. Don’t retry or cancel anything.
Keep the agent’s access easy to understand.
What is this Monthly connection allowed to do, and which accounts can it access? Read only; don’t request or change any permissions.
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.
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.
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.
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.
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.
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.
Get started in minutes.
