8 live
Automate

Automate your socials with Gemini CLI

Gemini CLI adds Antwork over HTTP with one command, then authorizes with its own slash command. Two lines and you are posting from the terminal.

Platforms8API keys0To startfree
One command
$ gemini mcp add --transport http antwork https://api.antwork.io/mcp

Connect it

  1. 01Authorize with /mcp authRun /mcp auth antwork inside the Gemini CLI. It opens an OAuth consent screen in your browser; there is no key to paste into a config file.
  2. 02Connect the social accountAsk it to connect your account and it returns a connect link per platform. Authorize once and Antwork refreshes that token for you.
  3. 03Draft, then publish as a second stepDrafting and publishing are separate tool calls. The agent writes first and only publishes when you say so, which matters more in a terminal where there is no card to review.

Server details

Server URL
https://api.antwork.io/mcp
Server name
antwork

The server speaks Streamable HTTP and authenticates with OAuth 2.1, using dynamic client registration and PKCE. Gemini CLI handles the token exchange for you — all you see is a browser consent screen.

If it does not work

The three things that go wrong most often when connecting Gemini CLI:

  • Antwork's tools do not appear — restart Gemini CLI after installing. Most clients only read their MCP configuration at startup.
  • The consent screen keeps reappearing — the session expired or the grant was revoked. Approve it once more; grants last 30 days and refresh silently while you keep using them.
  • The tools answer but report no accounts — the workspace exists, but no social account is connected to it yet. Connect one in the Antwork web app first.

Your agent already writes. Let it post.

One command, one consent screen, and every connected account is something you can just ask for.

Connect your AI