Social media publishing
for Claude Cowork.
Create drafts, work with media and schedule posts through MCP. Keep your channels, calendar and approvals together in PostDelegate.
Public preview · Hosted connections are not open yet. Launch statusBring your agent into the workflow.
Add your workspace’s MCP URL to a compatible remote connector, then authorize access. Follow the setup guide below for permissions and prerequisites.
https://YOUR-WORKSPACE-HOST/api/v1/mcpUse the server address from your PostDelegate workspace.
Turn a brief into a saved post.
Send content from your agent to the workspace. Review it before choosing when it goes live.
Plan the next week of content.
Schedule prepared posts and check each channel’s result from the same workflow.
Keep the final say.
Choose which accounts your agent can use and keep required approvals in place.
Start with a real publishing task.
Your AI client prepares the content. PostDelegate handles the draft and scheduling workflow.
“Create a draft from my launch notes. Use the LinkedIn account I choose and leave the post ready for review.”
list_accounts→create_draft→get_postConnect Claude Cowork, step by step.
01Before you connect
These guides describe the implemented workspace protocols. Customer access and live platform publishing remain subject to launch availability. Use the endpoint from your own PostDelegate workspace, not the public marketing website. Examples use a placeholder origin.
02Add a remote connector
Claude’s official documentation describes custom remote MCP connectors for Claude and Cowork. Use the custom-connector flow available to your account and supply the workspace MCP URL. Team policies can affect whether you can add a connector. Exact screens and availability may change; this guide does not claim a tested PostDelegate listing or installation.
https://YOUR-WORKSPACE-HOST/api/v1/mcp03Authorize the right workspace
When offered, complete PostDelegate OAuth in the browser and inspect the authorization before continuing. The connection uses the signed-in user’s permissions. A request to “only draft” is an instruction, not a replacement for a restricted account or grant.
- Claude’s remote connector reaches the server from Anthropic infrastructure. A loopback URL on your laptop is not a reachable remote deployment.
- Do not paste API keys, social tokens or passwords into the task conversation.
- Confirm that the client can discover list_accounts and create_draft before requesting a write.
04Start with one draft
Use list_accounts to discover the connected accounts your client can access. If the list is empty, connect a supported account in the web workspace first.
List the accounts I can access and their capabilities. Ask which one to use. Turn my brief into one draft using create_draft. Do not schedule or publish. Return the post ID so I can review it in PostDelegate.05Review, then schedule the same post
Complete required approval stages in the web workspace. Scheduling requires both create_posts and publish_directly. An approval requirement still applies when the actor has scheduling permission.
- Use schedule_draft with the existing post_id and an ISO 8601 scheduled_at timestamp, including its timezone offset or Z for UTC.
- schedule_post creates a new scheduled post. Do not use it as a substitute for scheduling an existing draft.
- Use get_post to inspect per-channel results. Scheduled means queued, not published.
- If the social platform’s outcome is uncertain, review the account before making another publishing attempt.
06If connection or creation fails
Check endpoint reachability, account authorization and discovered tools. If create_draft loses its response, inspect the workspace before repeating it. Do not invent an idempotency_key argument for this MCP tool. Content generation uses your Claude tools; PostDelegate supplies the publishing workspace.
Your agent does the legwork.
Your workspace keeps it organized.
Explore the app, review the connection steps and start with a draft.
View launch status ↗More agent guides →