Antwork

Draft, schedule, and publish social posts for your workspace straight from your AI.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "antwork-2": {
      "command": "npx",
      "args": [
        "-y",
        "antwork-2"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

Antwork Skills

A toolkit of Agent Skills that turn Claude into a social-media command center on top of the Antwork MCP connector — an MCP-native social scheduler for solo founders and small teams.

One orchestrator routes /antwork <command> to specialized skills, each of which codifies the right sequence of Antwork's 43 MCP tools so the workflow runs correctly the first time — voice-aware drafting, the draft→publish/schedule two-step, per-platform character limits, campaign grouping, analytics, and a full audit.

Commands

Command	Skill	What it does
`/antwork setup`	`antwork-setup`	Connect accounts, set workspace timezone + posting times, brand identity. Run first.
`/antwork voice [account]`	`antwork-voice`	Build/refresh a per-account voice profile from real posts.
`/antwork post <idea>`	`antwork-poster`	Draft → schedule/publish a post (single account or multi-platform fan-out).
`/antwork calendar <theme>`	`antwork-calendar`	Plan and batch-schedule a content calendar.
`/antwork repurpose <source>`	`antwork-repurpose`	One piece → platform-native variants, grouped as a campaign.
`/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 analytics [range]`	`antwork-analytics`	Pull performance + engagement and synthesize a report.
`/antwork engage`	`antwork-engage`	Comment/reply (LinkedIn), retry failed posts, community work.
`/antwork media`	`antwork-media`	Upload, attach, and manage post media.
`/antwork audit`	`antwork-audit`	Full social-presence audit with 5 parallel agents + a 0-100 Social Health Score.

You don't have to type the command — describe the intent ("schedule a LinkedIn post for Tuesday", "how did last month do?") and the orchestrator routes to the right skill.

The audit's parallel agents

/antwork audit spawns five read-only subagents concurrently, then synthesizes a weighted score:

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 — connect Antwork

These skills call the Antwork MCP server, so you need it connected to Claude first. See antwork.io. A single OAuth token spans all your workspaces.

Once connected, the highest-value path for a new user is: setup → voice → ideas/calendar → post → analytics → audit.

Install

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 iker-gonzalez/antwork-skills
/plugin install antwork-skills@antwork

That's it — the antwork MCP server connects automatically (complete the OAuth prompt), and the orchestrator, 11 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):

Terminal

curl -fsSL https://raw.githubusercontent.com/iker-gonzalez/antwork-skills/main/install.sh | bash

Prefer to clone first? git clone … && cd antwork-skills && ./install.sh. Remove everything with ./uninstall.sh.

Claude.ai

Skills submitted to the Anthropic Skills Directory surface automatically when you mention something they cover — no install step. (Plugins are Claude-Code-only; the skills are the cross-surface format.)

Repository layout

Code

antwork-skills/
├── .claude-plugin/
│   ├── plugin.json           # plugin manifest
│   └── marketplace.json      # self-hosted marketplace (lists this plugin)
├── .mcp.json                 # Antwork MCP server — bundled & auto-connected
├── skills/                   # orchestrator + 11 specialized skills
│   ├── antwork/              # orchestrator — routes /antwork <command>
│   ├── antwork-setup/        ├── antwork-campaign/
│   ├── antwork-voice/        ├── antwork-ideas/
│   ├── antwork-poster/       ├── antwork-analytics/
│   ├── antwork-calendar/     ├── antwork-engage/
│   ├── antwork-repurpose/    ├── antwork-media/
│   └── antwork-audit/
├── agents/                   # 5 parallel audit subagents (auto-discovered)
├── templates/                # voice profile, calendar, campaign brief, launch week, report
├── 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

MIT

Related MCP Servers

View all in Developer Tools View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Antwork

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "antwork": { "command": "npx", "args": ["-y", "Antwork"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/antwork-2?style=directory)](https://allmcps.com/mcp/antwork-2)

HTML Embed

<a href="https://allmcps.com/mcp/antwork-2"><img src="https://allmcps.com/api/badge/antwork-2?style=directory" alt="Antwork on AllMCPs" /></a>

Technical Specs & Signals

CategoryDeveloper Tools

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 💻 Developer Tools →Best MCP servers for Developers →Alternatives to Antwork →Install in Claude Desktop Install in Cursor Install in VS Code