Antwork MCP server
Commit Nov 13, 2026Draft, schedule, and publish social media posts to platforms like LinkedIn, X, and Instagram directly through an AI assistant.
Also known as polynode-co/antwork
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.0.4
- Last commit
- Nov 13, 2026
- License
- MIT
What is Antwork MCP?
Antwork is an MCP server. Draft, schedule, and publish social media posts to platforms like LinkedIn, X, and Instagram directly through an AI assistant.
Summary generated from the project's README
About Antwork MCP server
Antwork provides a bridge between AI assistants and social media platforms, allowing users to draft, schedule, and publish content without leaving their chat interface. It supports a wide range of services including LinkedIn, X, Instagram, Facebook Pages, Threads, TikTok, YouTube, and Pinterest. The server uses OAuth 2.1 for authentication, meaning users sign in through a browser rather than managing manual API keys.
This tool is designed for developers and creators using MCP-compatible clients like Claude Desktop, Cursor, ChatGPT, and VS Code with GitHub Copilot. It offers specialized workflows through various skills, such as repurposing content across platforms or generating a content calendar. While the first two social accounts are free, additional connections require a monthly subscription. Users can manage media libraries, view performance analytics like impressions and reach, and even turn software commits into social posts using the ship command.
What you can do with it
- 1Repurpose existing contentTake a single piece of content and transform it into native posts for multiple different platforms.
- 2Perform social presence auditsAnalyze your social media health using multiple specialized agents to receive a performance score.
- 3Plan content calendarsGenerate and batch-schedule a themed content plan for your social media accounts.
Written from the project's README. Every use case is checked against a quote from it.
How to install Antwork MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Antwork MCP in Claude Code
$ claude mcp add --transport http antwork https://api.antwork.io/mcpInstall Antwork MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"antwork": {
"url": "https://api.antwork.io/mcp"
}
}
}Install Antwork MCP in VS Code
.vscode/mcp.json
{
"servers": {
"antwork": {
"type": "http",
"url": "https://api.antwork.io/mcp"
}
}
}Install Antwork MCP in VS Code CLI
$ code --add-mcp '{"name":"antwork","type":"http","url":"https://api.antwork.io/mcp"}'Install Antwork MCP in Codex
$ codex mcp add antwork --url https://api.antwork.io/mcpInstall Antwork MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.antwork] url = "https://api.antwork.io/mcp"
Install Antwork MCP in Gemini CLI
$ gemini mcp add -s user --transport http antwork https://api.antwork.io/mcpInstall Antwork MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"antwork": {
"url": "https://api.antwork.io/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablepolynode-co/antwork is public and reachablegithub.com/polynode-co/antwork ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-13github.com/polynode-co/antwork ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubAntwork: post to LinkedIn, X, Instagram and more from your AI
AI assistants have no built-in connector for posting to social media. To let your assistant draft, schedule and publish posts, you connect it to an MCP server that holds the platform permissions. Antwork is that server: connect https://api.antwork.io/mcp once, sign in with OAuth, and your assistant can post to your connected accounts on LinkedIn (personal profile or company page), X, Instagram, Facebook Pages, Threads, TikTok, YouTube and Pinterest. Posts stay drafts until you ask it to schedule or publish them.
It works in VS Code (GitHub Copilot chat), Claude, ChatGPT, Cursor and any other client that speaks MCP. Two social accounts are free, then $5 a month each (pricing).
Install in one line
Pick your agent. Each line adds the Antwork skills (including /antwork ship, which turns your commits and releases into posts); the plugin lines also connect the MCP server.
| Agent | Command |
|---|---|
| Claude Code (plugin: skills, audit agents and MCP server) | /plugin marketplace add polynode-co/antwork then /plugin install antwork@antwork |
| Codex (plugin: skills and MCP server) | codex plugin marketplace add polynode-co/antwork && codex plugin add antwork@antwork && codex mcp login antwork |
| Any agent, skills only (skills CLI: Claude Code, Codex, Cursor and others) | npx skills add polynode-co/antwork |
The skills CLI installs skills, not MCP servers, so connect the server once yourself:
# Claude Code
claude mcp add --transport http antwork https://api.antwork.io/mcp
# Codex
codex mcp add antwork --url https://api.antwork.io/mcp && codex mcp login antwork
Or in Codex's ~/.codex/config.toml:
[mcp_servers.antwork]
url = "https://api.antwork.io/mcp"
Then, from inside a repo: /antwork ship (or just "post about what I shipped this week").
Connect
| Server URL | https://api.antwork.io/mcp |
| Server name | antwork |
| Transport | Streamable HTTP |
| Auth | OAuth 2.1 with dynamic client registration. No API key to create or store. |
The first tool call opens a consent screen in your browser. After that, ask your assistant to connect a social account and it returns a connect link for each platform.
VS Code
Install Antwork from the MCP servers gallery, or add it in one click. MCP servers in VS Code run through GitHub Copilot, so the Copilot extension must be installed and signed in. To add it by hand, put this in .vscode/mcp.json:
{
"servers": {
"antwork": {
"type": "http",
"url": "https://api.antwork.io/mcp"
}
}
}
Other clients
- Claude.ai or Claude Desktop: add
https://api.antwork.io/mcpas a custom connector. Step-by-step. For the calendar, campaign, analytics and audit workflows, add the claude.ai skill too. - Claude Code: install the plugin below, which connects the server and adds the skills in one step.
- ChatGPT: setup guide.
- Cursor, and Grok Bot through Cursor's catalog: this repo is also a Cursor plugin (
.cursor-plugin/andmcp.json: the server plus the skills). Until it is listed in the Cursor Marketplace, use the setup guide, or give Grok Bot the server URL (guide). - Anything else: point it at the server URL above. Full MCP docs.
What your assistant can do
- Draft a post in each account's own voice. It reads that account's recent posts first.
- Schedule or publish, per account or as a campaign across several accounts.
- Attach images, video and PDFs, and manage the media library.
- See the calendar, list and search posts, and retry a failed one.
- Report performance per post and per account: impressions or views, likes, comments, shares and reach, plus saves, link clicks, profile visits, follows and watch time where the platform reports them, and daily follower counts per connected account. A metric a platform doesn't report shows as blank, never as zero.
Each platform's own rules apply: Instagram and Pinterest need an image or video, TikTok and YouTube need a video, and Instagram needs a Creator or Business account. Tool reference.
Antwork Skills for Claude Code and claude.ai
This repo also adds Agent Skills on top of the connector. The connector alone handles single steps: drafting, scheduling, publishing, media, connections. The skills cover the multi-step workflows: a content calendar planned around what's already scheduled, one piece repurposed across platforms, a campaign arc, ideas grounded in what performed, variations on what went viral in your niche, an analytics report, and a scored audit. One router sends /antwork <command> (or a plain request) to the right one.
Commands
| Command | Skill | What it does |
|---|---|---|
/antwork voice [account] |
antwork-voice |
Read an account's voice from its real posts, or capture one from samples. |
/antwork calendar <theme> |
antwork-calendar |
Plan and batch-schedule a content calendar. |
/antwork repurpose <source> |
antwork-repurpose |
One piece → one post with a native version per platform. |
/antwork campaign <goal> |
antwork-campaign |
Sequence a multi-post campaign / launch week. |
/antwork ideas [topic] |
antwork-ideas |
Data-driven hooks grounded in what already performed. |
/antwork viral <niche or @creator> |
antwork-viral |
Study what went viral in a niche or for a creator, name the patterns, write variations in your voice. |
/antwork analytics [range] |
antwork-analytics |
Pull performance + engagement and synthesize a report. |
/antwork audit |
antwork-audit |
Full social-presence audit with 5 parallel agents + a 0-100 Social Health Score. |
/antwork ship [--since …] [--release <tag>] |
antwork-ship |
Turn the current repo's commits, merged PRs or a release into build-in-public posts, per account, in each account's voice. |
You don't have to type the command — describe the intent ("plan next week", "how did last month do?") and the router picks the skill. A single post, connecting an account and media need no skill: the connector's own instructions cover them.
The audit's parallel agents
In Claude Code, /antwork audit spawns five read-only subagents concurrently, then synthesizes a weighted score. On claude.ai, which has no subagents, the same five dimensions run one after another:
| Agent | Dimension | Weight |
|---|---|---|
antwork-performance |
Engagement & top/bottom posts | 30% |
antwork-voice-analyst |
Voice consistency across accounts | 20% |
antwork-cadence |
Posting cadence & timing | 20% |
antwork-content |
Content quality (hooks, CTAs, fit) | 20% |
antwork-growth |
Platform coverage & growth | 10% |
Prerequisite
The skills call the Antwork MCP server, so it has to be connected (see Connect). The plugin does that for you. A single OAuth token spans all your workspaces.
Once connected, a good first run is audit (where you stand), then ideas or calendar (what to post next).
Install the skills
Claude Code plugin (recommended)
This repo is also a Claude Code plugin marketplace. Installing the plugin wires up the Antwork MCP server and all skills + agents in one step:
/plugin marketplace add polynode-co/antwork
/plugin install antwork@antwork
That's it — the antwork MCP server connects automatically (complete the OAuth prompt), and the router, 9 skills, and 5 audit agents load. Why the plugin over loose skills: the skills are useless until Antwork's MCP is connected, and the plugin ships that config bundled, so there's no separate connector setup.
Script install (no plugin)
If you'd rather not use the plugin system, the script copies the skills + agents straight into ~/.claude/ (you still connect the Antwork MCP yourself):
curl -fsSL https://raw.githubusercontent.com/polynode-co/antwork/main/install.sh | bash
Prefer to clone first? git clone … && cd antwork-skills && ./install.sh. Remove everything with ./uninstall.sh.
OpenClaw
clawhub/antwork/ is a self-contained skill for OpenClaw. A ClawHub listing is coming soon; it is not published there yet, so clawhub install won't find it. Until then, install it by hand: copy the folder into your OpenClaw skills directory and connect the server.
git clone https://github.com/polynode-co/antwork.git
cp -r antwork-skills/clawhub/antwork ~/.openclaw/skills/antwork
mcporter config add antwork --url https://api.antwork.io/mcp --auth oauth
It is deliberately not the router above. ClawHub publishes one folder, so a skill that routes to 8 siblings that were never installed would be broken — this one inlines the setup, the drafting protocol, the character limits and the draft→publish two-step in a single file.
claude.ai
Plugins are Claude Code only, so claude.ai gets the same skills as one upload:
- Download
antwork-claude-ai-skill.zip. - In claude.ai, open Settings, find Skills, and upload the ZIP.
- Connect the Antwork connector (see Connect) if you haven't.
It is one skill named antwork: the router, with every other skill and audit dimension inside it as a reference file it reads when needed. claude-ai/build.sh generates it from skills/ (each skill with its templates, and the audit's agents), and a workflow republishes it on every change, so it never drifts from the plugin. Posting itself needs no skill on claude.ai either: the connector sends its drafting rules when it connects.
Repository layout
antwork-skills/
├── .claude-plugin/
│ ├── plugin.json # plugin manifest
│ └── marketplace.json # self-hosted marketplace (lists this plugin)
├── .mcp.json # Antwork MCP server — bundled & auto-connected
├── .cursor-plugin/ # Cursor plugin manifest + single-plugin marketplace
├── mcp.json # the same server, for the Cursor plugin
├── skills/ # router + 9 specialized skills, each with its own templates/
│ ├── antwork/ # router — /antwork <command>
│ ├── antwork-ship/ # commits / PRs / releases → posts
│ ├── antwork-calendar/ ├── antwork-campaign/
│ ├── antwork-repurpose/ ├── antwork-ideas/
│ ├── antwork-voice/ ├── antwork-analytics/
│ ├── antwork-viral/
│ └── antwork-audit/ # + agents/: the 5 parallel audit subagents
├── claude-ai/build.sh # builds the claude.ai ZIP from skills/
├── clawhub/ # self-contained OpenClaw skill (ClawHub listing coming soon)
├── install.sh / uninstall.sh # script-install fallback
└── README.md / LICENSE
Contributing
Each skill lives in skills/<name>/SKILL.md with YAML frontmatter (name, description) followed by markdown instructions. Keep description: specific — it determines when Claude auto-loads the skill. Use only real Antwork MCP tools and never invent tool arguments; the server rejects unknown fields.
License
Antwork MCP questions
How do I add Antwork MCP to Claude Code?
Run claude mcp add --transport http antwork https://api.antwork.io/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Antwork MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Which social media platforms does Antwork support?
Antwork supports LinkedIn (personal and company), X, Instagram, Facebook Pages, Threads, TikTok, YouTube, and Pinterest.
How much does Antwork cost?
Two social accounts are provided for free, after which it costs $5 per month for each additional account.
Can I use Antwork with Claude or ChatGPT?
Yes, it works with Claude (including Claude Desktop and Claude Code), ChatGPT, Cursor, and any other MCP-compatible client.