Antwork

- ›Draft posts on-brand using your stored voice profile per platform.
- ›Schedule or publish to LinkedIn, X, Threads, Facebook, Instagram, YouTube, TikTok, and Pinterest.
- ›Read engagement metrics, post history, and per-day timeseries for any post.
- ›Manage drafts, scheduled posts, and the media library.
- ›Connect / disconnect social accounts and inspect their health.

Every supported MCP client follows the same shape: register the server URL, then approve OAuth in your browser when prompted. The exact install affordance differs per client.

Pick your client for step-by-step setup:

The Antwork MCP server implements OAuth 2.1 with PKCE and dynamic client registration (RFC 7591), so MCP clients can connect without you pre-registering each one. Tokens are scoped, revocable, and issued per-client.

Each tool requires one of four scopes. The consent screen lists the scopes a client is requesting so you can approve or deny them granularly.

- ›Access tokens are short-lived JWTs (5 minute TTL).
- ›Refresh tokens are long-lived and stored server-side. Standardrefresh_tokengrant.
- ›Revoke via the standard/oauth/revokeendpoint (RFC 7009) or from Settings → Connected AIs in your Antwork dashboard. Revocation invalidates the refresh token immediately.
- ›Each MCP client (Claude desktop, Claude Code, Cursor, …) gets its own token. Revoking one client does not affect others.

- ›GET /.well-known/oauth-protected-resource— RFC 9728 resource metadata.
- ›GET /.well-known/oauth-authorization-server— RFC 8414 authorization server metadata.
- ›POST /oauth/register— RFC 7591 dynamic client registration.
- ›POST /oauth/token— authorization-code and refresh-token grants. PKCE S256 required.
- ›POST /oauth/revoke— RFC 7009 token revocation.

Antwork exposes 35 MCP tools across seven categories. Read-only tools never mutate state; destructive tools (publish, delete, disconnect) trigger explicit confirmation in clients that honordestructiveHintannotations.

!Tool argument schemas are introspected from the server live — connect a client and call tools/list to see the canonical JSON Schemas with required fields and types.

- ›list_posts,search_posts→posts-table: filterable list with inline detail modal that edits + publishes without leaving chat.
- ›get_post,create_post,update_post,duplicate_post→post-preview: full post card with per-platform tabs, inline editor, schedule/publish actions, an Add media picker (uploads + library reuse), and per-account "View on X" links once published.
- ›get_calendar→calendar: month / week views of scheduled + published posts.
- ›list_social_accounts,get_connection_urls,disconnect_social_account→connections-panel: per-account health, reconnect, disconnect; workspace switching via the header propagates to every other iframe.
- ›list_media,get_media→media-gallery: thumbnail grid of the workspace library — reuse media across posts without re-uploading.

Clients that don't support MCP Apps still get the raw tool output — the UI is purely a presentation layer.

"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→ pickantwork→ Re-authenticate.

Publish failed on one platform but succeeded on others

publish_postreturns per-platform status. The most common cause is a social account whose token expired or was revoked from the platform side. Runlist_social_accountsto find unhealthy accounts and reconnect them via the consent URL returned byget_connection_urls, then callretry_failed_post.

"Post stays as DRAFT after I asked to schedule it"

create_postonly creates a draft. Your assistant must follow up withschedule_post(post_id, scheduled_for)orpublish_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)

When a workspace has more than one connected account on a platform (e.g. two LinkedIn pages), Antwork picks the first healthy account by default. To target a specific account, pass itsaccountIdin the post'splatformsarray rather than the platform name. The Antwork Poster Skill also prompts the assistant to confirm before publishing.

attach_mediarequires a Firebase Storage URL — pass external URLs throughupload_mediafirst so they get staged into your workspace storage. The publisher refuses non-storage URLs.

Antwork applies a soft rate limit of 60 tool calls / minute / workspace. Hitting the limit returns HTTP 429 with aRetry-Afterheader. Publish operations are not rate-limited at the MCP layer but downstream platforms have their own limits (LinkedIn ~150 posts/day, X ~300 posts/3h).

Origin blocked / CORS error in browser-based clients

The server validates theOriginheader 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.

- ›Tool calls: 60 / minute / workspace (soft limit; HTTP 429 withRetry-After).
- ›Media upload: 25 MB per file. Images, video (mp4/mov/webm), PDFs accepted.
- ›Posts: no Antwork-side cap; downstream platforms enforce their own (LinkedIn ~150/day, X ~300/3h, others vary).
- ›Scheduled posts: 1 year max horizon.
- ›OAuth tokens: access token 5 min TTL, refresh token revocable any time.

Initial public release alongside Anthropic connector directory submission.

- ›35 MCP tools across identity, social accounts, voice profiles, posts, publishing, analytics, and media.
- ›Four MCP Apps: posts-table, post-preview, calendar, connections-panel.
- ›OAuth 2.1 with PKCE, dynamic client registration (RFC 7591), token revocation (RFC 7009).
- ›Per-platformaccountResultsreturned frompublish_postandget_postso multi-account workspaces show the correct publishing account in UI.

Questions, integration help, or bugs? Reach out.

Free MCP that drives an audit of your marketing. Your AI connects, adsOS digs through your ads, email and site, and hands back a growth plan you can run today.

Create, schedule, and publish social media posts to 9 platforms from Claude, Cursor, or any AI agent. Hosted server with OAuth or API key auth.

Let any AI agent post to TikTok, Instagram, YouTube, X, LinkedIn, Bluesky, Telegram, Mastodon & Discord via one MCP tool.

Bulk publish to multiple social media at once.

Publish, schedule, and manage social media across 11 platforms with media uploads and analytics tracking.

Transforms any blog/article URL into ready-to-post social media content for Twitter/X, LinkedIn, Instagram, Facebook, and email. Hosted on Apify, zero setup, pay-per-event ($0.07).

HuiMei — Social Media Automation MCP Server

AI-native social media automation platform — publish content to 12+ platforms (Douyin, XHS/Xiaohongshu, Bilibili, Kuaishou, Weibo, Zhihu, TikTok, Toutiao, WeChat Channels & more) with a single MCP tool call. Supports video, image, and article publishing with full account management.

AI-powered multi-platform content publishing. 25 tools to create posts, run automations, manage RSS feeds, generate hashtags, search images, and publish to Instagram, Facebook, LinkedIn, X, Threads, Telegram, Discord, WordPress, YouTube, TikTok, and more.

Connect your social media workflows directly to your AI agent to draft, schedule, publish, and analyze social content using natural language.

Connect AI assistants to SocialBu to create, schedule, publish, and analyze social media content from chat.