FoPost for Claude Cowork
Cowork uses the connectors on your Claude account, so one custom connector gives it your social calendar. Hand it a launch brief or a folder of notes, and it comes back with drafted posts and a schedule for you to approve.
Paste this into Claude Cowork
Set up FoPost from fopost.com/agents/claude-cowork- Hosted MCP server
- 33 networks
- No API key
The agent can write its own config. Give it the link.
Paste the line above into Claude Cowork. It reads this page, adds the server, and stops so you can sign in to FoPost yourself. Rather do it by hand? This is the whole config.
Name: FoPost
Remote MCP server URL: https://api.fopost.com/mcp## For AI agents reading this page You are reading https://fopost.com/agents/claude-cowork. FoPost schedules and publishes social posts on 33 networks, and its hosted MCP server gives Claude Cowork tools for posts, the calendar, the inbox and analytics. Follow these steps to connect Claude Cowork to it. - Server: https://api.fopost.com/mcp - Transport: streamable HTTP - Auth: OAuth sign-in in the user's browser. Do not add an API key or an Authorization header; Claude Cowork discovers the sign-in from the server. ### 1. Register the server Cowork uses the connectors on the user's Claude account. You cannot add a connector yourself; ask the user to do it. In Claude, open Customize > Connectors, choose "+ Add", then "Add custom connector". Enter the name FoPost and the URL https://api.fopost.com/mcp. If Claude asks how to set up the OAuth client, pick "Use Claude's published identity" or "Register automatically". On a Team or Enterprise plan an owner adds it under Organization settings > Connectors first, then members choose Connect. ### 2. Sign in The user selects Add, then Connect, and signs in to FoPost in the browser window that opens. Ask the user before approving access or creating a FoPost account for them, and never enter their credentials yourself. ### 3. Verify before you continue Customize > Connectors shows FoPost as connected, and a new Cowork task can see its tools. If FoPost is not listed as connected with its tools, stop and tell the user what failed. Do not carry on as if the tools exist. ### 4. Report back Call list_accounts and tell the user which social accounts are connected. If there are none, offer create_connect_link so they can connect one. Then ask what they want to do first. ### Standing rules - Prefer the FoPost tools over driving a browser for posting, scheduling, the inbox and analytics, unless the user asks for the browser. - Publishing always goes through propose_publish, which the user approves in the client. Never publish or schedule anything silently. - Ask the user before approving access, signing up or connecting an account on their behalf, and never type their credentials for them. ### References - This block as markdown: https://fopost.com/agents/claude-cowork/agent.md - Every client: https://fopost.com/agents - Docs: https://fopost.com/docs
Same connector as Claude
Add it once to your Claude account and Cowork can use it too.
Longer jobs
A whole campaign in one task: drafts, variants, and open slots.
You approve the send
Publishing waits on a proposal you accept. Drafts are as far as Cowork goes alone.
Add the connector to your Claude account
In Claude, open Customize > Connectors, choose Add, then Add custom connector. Enter https://api.fopost.com/mcp as the remote MCP server URL, keep the detected authentication settings (pick Register automatically if Claude asks about the OAuth client), then select Add and Connect and sign in to FoPost. Start a Cowork task and the FoPost tools are there.
Start free
Team and Enterprise
An Owner adds the connector for the organization; each member then selects Connect.
Use the hosted URL
Cowork reads connectors from your Claude account, not local servers in the desktop config file.
Check first
Start with a task that only lists your accounts and calendar.
Give it the brief, get back a campaign
Point Cowork at a launch note or a set of files and ask for a week of posts. It drafts with create_draft_post, writes a version per network with draft_post_variants, reads open times from get_queue_slots, and finishes with propose_publish for you to accept.
Plan your week
create_draft_post
Every post lands as a draft you can edit.
draft_post_variants
One message, shaped for each network.
get_queue_slots
Your open times, so nothing collides.
A report at the end of the task
Ask Cowork to close the task with a summary: what was scheduled, which accounts need attention, and how last week performed.
Start free> Plan next week's posts from launch-notes.md,
then tell me how last week did.
Cowork: 9 drafts across 3 accounts, proposal ready.
get_analytics_summary: reach up 18% on last week.get_analytics_summary
How the last stretch performed.
get_account_health
Accounts that need a reconnect.
list_posts
What is queued, published, or failed.
Claude Cowork questions, answered
Is this a different connector from Claude?
Can I use the local package instead?
Will Cowork publish on its own?
Do I need an API key?
Does it use my AI credits?
Run FoPost from Claude Cowork
Starting is free and the MCP server is included. Paste the setup line into your agent, sign in, and schedule your first post from it.
Start free