Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Draft, schedule, and publish social posts for your workspace straight from your AI.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://api.antwork.io/mcpRun this in your terminal
claude mcp add --transport http social https://api.antwork.io/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"social": {
"url": "https://api.antwork.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"social": {
"type": "http",
"url": "https://api.antwork.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://api.antwork.io/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain antwork.io (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.4) reached the registry 8 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, zanadir
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Find what a repository's CI is missing, and which security checks cannot fail the build.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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).
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 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").
| 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.
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" } } }
https://api.antwork.io/mcp as a custom connector. Step-by-step. For the calendar, campaign, analytics and audit workflows, add the claude.ai skill too..cursor-plugin/ and mcp.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).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.
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, an analytics report, and a scored audit. One router sends /antwork (or a plain request) to the right one.
| 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 | antwork-calendar | Plan and batch-schedule a content calendar. |
/antwork repurpose | antwork-repurpose | One piece → one post with a native version per platform. |
/antwork campaign | antwork-campaign | Sequence a multi-post campaign / launch week. |
/antwork ideas [topic] | antwork-ideas | Data-driven hooks grounded in what already performed. |
/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 ] | 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.
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% |
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).
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, 8 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.
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.
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.
Plugins are Claude Code only, so claude.ai gets the same skills as one upload:
antwork-claude-ai-skill.zip.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.
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 + 8 specialized skills, each with its own templates/ │ ├── antwork/ # router — /antwork │ ├── antwork-ship/ # commits / PRs / releases → posts │ ├── antwork-calendar/ ├── antwork-campaign/ │ ├── antwork-repurp
Only the beginning is shown; read the rest in the repo