"Bearer token required" / 401 on every call
The MCP client hasn't completed OAuth or its refresh token has been revoked. In claude.ai: Settings → Connectors → Antwork → Disconnect, then reconnect. In Claude Code: /mcp → pick antwork → Re-authenticate.
Publish failed on one platform but succeeded on others
publish_post returns per-platform status. The most common cause is a social account whose token expired or was revoked from the platform side. Run list_social_accounts to find unhealthy accounts and reconnect them via the consent URL returned by get_connection_urls, then call retry_failed_post.
"Post stays as DRAFT after I asked to schedule it"
create_post only creates a draft. Your assistant must follow up with schedule_post(post_id, scheduled_for) or publish_post(post_id). The companion Antwork Poster Skill (github.com/iker-gonzalez/antwork-skills) codifies this two-step so Claude doesn't skip it.
The wrong account got the post (multiple accounts per platform)
A post is bound to one account: create_post takes an account_id, and passing it is how you choose between two LinkedIn pages. Omit it and Antwork resolves the first healthy account on that platform. list_social_accounts returns the ids, and every workspace-scoped tool result already carries them in workspaceAccounts.
Media upload silently drops the file
attach_media requires a Firebase Storage URL — pass external URLs through upload_media first so they get staged into your workspace storage. The publisher refuses non-storage URLs.
Rate limits
Antwork does not rate-limit tool calls. The limits you can hit are the platforms' own — LinkedIn allows roughly 150 posts a day and X roughly 300 per 3 hours, and both refuse the request rather than queue it, so the post lands as failed with the platform's reason on it.
Origin blocked / CORS error in browser-based clients
The server validates the Origin header on Streamable HTTP per the MCP spec. Allowed origins are first-party Antwork hosts, claude.ai, claude.com, console.anthropic.com, and localhost. If you're hosting a custom client on a different origin, contact us to whitelist it.
Contact
Questions, integration help, or bugs? Reach out.