Schedule social media posts from Claude Code

The setup in four steps

1. Connect your channels and copy your API key. In Hookpost, connect the networks you want to post to, then open Settings > Developers and copy the API key. The Developers tab is on Standard (₹599 a month) and Pro; the Free plan has no API key.
2. Add Hookpost to Claude Code. Run: claude mcp add --transport http hookpost https://hookpost.hookstep.in/api/mcp --header "Authorization: Bearer YOUR_API_KEY". Then run claude mcp list to check that the server connects.
3. Ask for drafts first. Start claude in your project and ask it to list your Hookpost channels, then to save posts as drafts rather than schedule them. Review the drafts in the Hookpost calendar before anything goes out.
4. Schedule when you trust the output. Ask Claude to schedule posts for a date and time instead of saving drafts. Hookpost stores them and publishes at that time, whether or not your terminal is open.

Each step in detail below.

Step 1: add the server

Run this in your terminal with your own key in place of YOUR_API_KEY. It adds a server called hookpost for you, in every project:

claude mcp add --transport http hookpost https://hookpost.hookstep.in/api/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Check it with claude mcp list. The hosted endpoint speaks Streamable HTTP and needs nothing installed on your machine.

Share it with your team (optional)

Add --scope project and Claude Code writes the server to .mcp.json at the root of the repo, so everyone who clones it gets the same setup. Keep the key out of git by referencing an environment variable; Claude Code expands it in the URL and headers. Note the single quotes, which stop your shell from writing the key itself into the file:

claude mcp add --transport http hookpost https://hookpost.hookstep.in/api/mcp \
  --scope project \
  --header 'Authorization: Bearer ${HOOKPOST_API_KEY}'

{
  "mcpServers": {
    "hookpost": {
      "type": "http",
      "url": "https://hookpost.hookstep.in/api/mcp",
      "headers": { "Authorization": "Bearer ${HOOKPOST_API_KEY}" }
    }
  }
}

Each person sets HOOKPOST_API_KEY in their own shell. Claude Code asks for approval the first time it sees a project-scoped server.

Step 2: ask for drafts first

Start claude in your project and give it a job. Asking for drafts means nothing is published until you have read it:

List my Hookpost channels. Then read CHANGELOG.md, write a short post about
the newest release for LinkedIn and a shorter one for X, and save both as
drafts in Hookpost. Don't schedule anything yet.

What happens next, tool by tool:

1. integrationList returns your connected channels with their ids.
2. integrationSchema returns each network's rules: 3,000 characters on LinkedIn, 280 on X (4,000 on a Premium account), and any settings the post needs.
3. integrationSchedulePostTool creates the posts with type: "draft". Hookpost runs the same checks as its own editor, and if something is wrong the tool returns the error so Claude can fix it and try again.

Claude Code asks your permission before it calls a tool unless you have already allowed it. When the drafts look right, ask Claude to schedule them for a date and time instead, or open them in Hookpost and schedule them there.

Where the posts go

• Into the calendar you already use. Drafts show as "Draft:" on their day, and scheduled posts sit next to the ones your team wrote in the browser. Open one and the editor header shows an MCP badge, so you can tell which posts an agent wrote.
• Edit, move or delete in the app. Drag a post to another day, change its text, or delete it. Claude can change a pending post's network settings, but not its text or date, and it cannot delete anything.
• Published by Hookpost, not by your terminal. Scheduled posts are stored on the server and go out at their time with Claude Code closed.
• Failures are visible. A post a network rejects turns red in the calendar with the error, you get an in-app notification, and members who keep failure emails on get an email.

Prompts that work well from a repo

Posting the same news to several networks? The limits table for every network shows what breaks when one text goes everywhere. Publishing full articles to Dev.to, Hashnode or WordPress is covered in cross-posting dev articles.

Unattended runs and CI

claude -p runs one prompt without the interactive session. MCP tools are named mcp__hookpost__<tool>, and listing them in --allowedTools lets the run call them without stopping to ask. The schedule tool can still publish straight away if the prompt asks for it, so ask for drafts in jobs nobody watches:

claude -p "Read CHANGELOG.md and save a LinkedIn draft in Hookpost about the newest release" \
  --allowedTools "Read,mcp__hookpost__integrationList,mcp__hookpost__integrationSchema,mcp__hookpost__integrationSchedulePostTool"

Or skip MCP and use the CLI

If a script already knows the text, the hookpost CLI on npm (version 0.1.1) talks to the same account without a model in the loop. Claude Code can run it too.

npm install -g hookpost
export HOOKPOST_API_KEY="your_key"     # or: hookpost auth login

hookpost channels                      # ids of your connected channels
hookpost post "v2.3 is out: faster exports and a new CSV importer." \
  --channel abc123,def456 --draft      # one post, two channels
hookpost posts --days 7                # what is queued for the next week

Leave out --at and the post takes the next free slot in your posting schedule. More on the CLI, the REST API and the Node SDK: social media scheduling API.

If it does not connect

401 Missing Authorization header

The --header part did not make it into the config. Run claude mcp remove hookpost and add it again with the header.

401 Invalid API Key or OAuth token

The key is wrong or was rotated. Copy it again from Settings → Developers. With the project setup, check that HOOKPOST_API_KEY is set in the shell you started Claude Code from.

No Developers tab in Settings

The workspace is on the Free plan. The key and MCP come with Standard and Pro.

A channel is missing from the list

Connect it in Hookpost first; the list only holds channels the workspace has connected. A channel that needs reconnecting shows up but cannot publish until you reconnect it in the app.