antworkDOCS

Troubleshooting

What you see when connecting your AI, signing in, connecting accounts or publishing goes wrong, and how to fix it.

Using ChatGPT? Follow the setup guide

Connecting your AI

ChatGPT: I pasted the setup prompt and nothing connected

The setup prompt is for agents that can change their own setup, like Claude Code, Codex or Cursor. ChatGPT can't: it connects only through its own settings. On chatgpt.com in a browser (not the phone app), open Settings → Security and login and switch on Developer mode, then open Plugins, click +, choose Create app, then Create MCP App, and paste https://api.antwork.io/mcp into Connection. The ChatGPT setup guide shows each step in a short video.

ChatGPT: there's no + on the Plugins page

The + only appears once Developer mode is on. In ChatGPT open Settings → Security and login and switch on Developer mode. OpenAI offers it on the web, not in the ChatGPT phone apps, so do this on chatgpt.com from a computer; on a work account your admin may have to allow it. Then open Plugins, click +, choose Create app, then Create MCP App.

I opened the MCP URL and landed on these docs

https://api.antwork.io/mcp is an address for your AI client, not a web page, so opening it in a browser tab sends you here. Paste it into your client instead: the Connection field of the new app in ChatGPT, or MCP server URL in Claude's Add custom connector dialog.

Codex: "malformed response", or it keeps retrying without asking you to sign in

Some Codex builds don't start the sign-in on their own, so the server stays unauthorized. Run the login yourself and approve it in your browser; until you do, codex mcp list shows Antwork as Not logged in. If Antwork isn't added to Codex yet, the add command below adds it and signs you in in one go.

Run in your terminal
codex mcp login antwork
Run in your terminal
codex mcp add antwork --url https://api.antwork.io/mcp

Gemini CLI: "added to project settings", or Antwork shows as Disabled

Without --scope user the server is saved only for the folder you ran the command in, and from your home folder it isn't saved at all. Gemini also disables MCP servers in folders you haven't trusted. Run the command below, start gemini, trust the folder when asked, then run /mcp auth antwork and approve the sign-in.

Run in your terminal
gemini mcp add --scope user --transport http antwork https://api.antwork.io/mcp --skip-trust

"This request timed out."

A connection request stays valid for 10 minutes, and this one ran out before it was approved. Nothing was connected and nothing on your account changed. Start the connection again from your AI client and approve it right away.

Connected, but the AI never uses Antwork

Connecting only makes Antwork's tools available. Coding tools such as Cursor, Codex, VS Code and Gemini CLI load them quietly and won't use them until you ask, so ask directly, for example: "Draft a post about the project I'm working on right now". Claude sets Antwork's tools to ask before each use, so approve the first call.

Claude: I can't add a custom connector

The free Claude plan allows one custom connector, so if you already have one, remove it first or upgrade to Pro, Max, Team or Enterprise. In claude.ai open Customize, then Connectors, then Add, then Add custom connector. On a Team or Enterprise account, an owner may have to allow custom connectors first.

Signing in

"Google sign-in is not available in this browser"

Links opened inside Instagram, Facebook, LinkedIn, X, TikTok and similar apps load in the app's own browser, where Google sign-in doesn't work. Tap the button to open the page in Safari or Chrome. If nothing happens, use the app's ⋯ or share menu and choose Open in browser, or sign in with an email link instead.

"Can't reach Antwork right now"

You're signed in, but the app couldn't load your account. It's usually a brief connection hiccup, often a network, VPN or browser extension blocking the connection. Press Try again; if it keeps happening, try another network or allow antwork.io in your blocker.

Social accounts

Instagram or Facebook connected the wrong account

Instagram and Facebook connect whichever account is logged in in that browser. Open the account's menu on Connections and choose Use a different account; the platform then asks you to log in. Reconnecting within 15 minutes of disconnecting does the same automatically. Threads can't be switched this way: change account on threads.net first, then connect again.

"No Facebook pages found"

Antwork posts to Facebook Pages, not personal profiles, and you need to be an admin of the Page, not an editor or moderator. Check your role in the Page's settings. If the Page belongs to a Meta Business portfolio, choose Try with business access so Antwork can see it.

LinkedIn added my profile and my company page

One LinkedIn sign-in can bring in your personal profile and the pages you manage, and each one you connect counts as an account. Your first 2 accounts are free, and the picker only ticks what fits, so untick anything you don't want before confirming. You can disconnect an account from Connections at any time.

"YouTube didn't accept that sign-in" (or another platform)

The sign-in the platform hands back can only be used once, so it's refused if it expired or was already used, for example after going back or reloading. Connect again from Connections and finish the platform's screens in one go.

Publishing

"Pinterest requires a board"

Every pin goes to a board, so the Pinterest account needs at least one. Create one with Create Board in the Compose sidebar, by asking your AI, or on Pinterest, and pick it before scheduling. If you don't pick one, Antwork uses the account's first board.

Instagram, Pinterest, TikTok or YouTube won't publish without media

These platforms need media: an image or video for Instagram and Pinterest, a video for TikTok and YouTube. If your AI can't upload a file you attached in the chat, open the post's mediaUrl: it opens the post in the Antwork composer with the media picker open, where you upload the file from your device and it attaches.

For developers

"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 a status for each post. 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 publish_post on the failed post to retry it.

"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/polynode-co/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 sets a post's media from Firebase Storage URLs in your workspace. Pass an external URL to add_media with url instead: it stores the file in your workspace storage and attaches it. The publisher refuses non-storage URLs.

Rate limits

Antwork does not meter tool calls. What limits posting is each account's daily maximum and its queue of scheduled posts (refused with daily_cap_reached and schedule_queue_full; get_post_context reports the account's dailyPostCap), the spacing and duplicate checks on X and Threads (posting_too_close, duplicate_post), and the platforms' own limits, which refuse the request rather than queue it, so the post lands as failed with the platform's reason on it. The figures are on the limits page.

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.