Hookpost

Hookpost MCP server, CLI and n8n node

Hookpost by Hookstep. A social media scheduler you can drive from Claude, Cursor, VS Code, Gemini CLI and other AI assistants. (Not related to the Shopify Flow app called HookPost.)

Website: https://hookpost.hookstep.in · Setup guide: https://hookpost.hookstep.in/mcp

What it does

Hookpost runs a hosted MCP server. Connect your AI assistant to it once, and the assistant can:

• list the social channels connected to your Hookpost workspace
• read each network's rules: character limits, media rules and the settings a post needs
• save posts to your Hookpost calendar as drafts, as scheduled posts, or publish them now
• list what is scheduled between two dates, and change the network settings of a post that has not gone out yet
• import an image or video from a public URL into your media library

Posts from an assistant land in the same calendar as posts written in the app, with an MCP badge, and go through the same checks as the editor. If a post breaks a network's rules, the assistant gets the reason back. There is no delete tool: deleting, and editing the text or date of an existing post, stay in the app.

There is nothing to install for the MCP server. It is one URL:

https://hookpost.hookstep.in/api/mcp

Your workspace API key goes in an Authorization: Bearer header. Copy the key from Settings → Developers in Hookpost. For a client that cannot send headers, put the key in the path instead: https://hookpost.hookstep.in/api/mcp/YOUR_API_KEY.

Behind a gateway that keeps the Authorization header for itself, such as Smithery, send the key as x-hookpost-api-key: YOUR_API_KEY instead (the raw key; a Bearer prefix is also accepted). If a request carries both headers, Authorization wins.

Treat the key like a password. It gives full access to your workspace's channels and posts, so keep it out of shared configs and public repos.

Set it up in your assistant

Claude Code

claude mcp add --transport http hookpost https://hookpost.hookstep.in/api/mcp \

--header "Authorization: Bearer YOUR_API_KEY"

Check it with claude mcp list.

Or install the Hookpost plugin, which adds the server plus a skill that tells Claude to check each network's rules and save drafts first. Claude Code asks for your API key once and keeps it in your system's credential store:

/plugin marketplace add jatinder14/hookpost-mcp

/plugin install hookpost@hookpost

Claude (claude.ai and Claude Desktop)

Go to Customize → Connectors → + Add → Add custom connector, paste the URL with your key in the path, and choose no sign-in:

https://hookpost.hookstep.in/api/mcp/YOUR_API_KEY

Claude adds remote servers as connectors, not through claude_desktop_config.json. On Claude's free plan you get one custom connector. If Claude Desktop can't connect that way, use the mcp-remote bridge in claude_desktop_config.json (it needs Node.js):

{

"mcpServers": { "hookpost": { "command": "npx", "args": ["-y", "mcp-remote", "https://hookpost.hookstep.in/api/mcp/YOUR_API_KEY"] } } }

mcp-remote is a third-party bridge that runs on your machine and forwards to the hosted server.

ChatGPT

A Hookpost app for ChatGPT is not available yet. Until it is, draft in ChatGPT and paste into the Hookpost editor, or use one of the clients on this page.

Cursor

Click Add to Cursor at the top of this page, then set HOOKPOST_API_KEY in your environment (Cursor reads ${env:HOOKPOST_API_KEY} from it). Or add it by hand in .cursor/mcp.json in a project, or ~/.cursor/mcp.json for all projects:

{

"mcpServers": { "hookpost": { "url": "https://hookpost.hookstep.in/api/mcp", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } }

VS Code (Copilot agent mode)

Click Install in VS Code at the top of this page. VS Code asks for your API key once and stores it as a secret. Or add it by hand in .vscode/mcp.json in your workspace:

{

"servers": { "hookpost": { "type": "http", "url": "https://hookpost.hookstep.in/api/mcp", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } }

Gemini CLI

Install this repo as an extension. It asks for your API key once and keeps it in your system keychain:

gemini extensions install https://github.com/jatinder14/hookpost-mcp

Or add the server by hand to ~/.gemini/settings.json. Use httpUrl, not url (in Gemini CLI, url means an SSE server):

{

"mcpServers": { "hookpost": { "httpUrl": "https://hookpost.hookstep.in/api/mcp", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } }

Codex CLI

~/.codex/config.toml. Codex reads the key from the HOOKPOST_API_KEY environment variable, so it never sits in the file:

[mcp_servers.hookpost]

url = "https://hookpost.hookstep.in/api/mcp" bearer_token_env_var = "HOOKPOST_API_KEY"

Kiro

Install the Hookpost power: in the Powers panel, choose Add Custom Power → Import power from GitHub and enter https://github.com/jatinder14/hookpost-mcp/tree/main/powers/hookpost. It signs in with OAuth, so there is no key to copy.

Grok

Grok adds remote MCP servers as custom connectors: open grok.com/connectors, click New Connector → Custom, enter https://hookpost.hookstep.in/mcp-oauth and sign in with your Hookpost account. For Grok Build, the grok/hookpost/ plugin installs the same server with the hookpost skill.

Windsurf

Open Windsurf's MCP settings, choose View raw config to open mcp_config.json, and add the hookpost entry from windsurf/mcp_config.json:

{

"mcpServers": { "hookpost": { "serverUrl": "https://hookpost.hookstep.in/api/mcp", "headers": { "Authorization": "Bearer ${env:HOOKPOST_API_KEY}" } } } }

Windsurf reads HOOKPOST_API_KEY from your environment, so the key stays out of the file. On macOS an app opened from the Dock doesn't see variables set in .zshrc: open Windsurf from a terminal, or put the key in the file in place of ${env:HOOKPOST_API_KEY}. Windsurf takes serverUrl for remote servers, not url. Restart Cascade after saving.

Microsoft Copilot Studio

In your agent, go to Tools → Add a tool → New tool → Model Context Protocol. Enter https://hookpost.hookstep.in/api/mcp as the server URL, choose API key authentication with type Header and header name x-hookpost-api-key, then paste your key (without Bearer) when you create the connection. A ready-to-import custom connector and the Microsoft 365 Copilot package are in microsoft/.

Other clients: see https://hookpost.hookstep.in/mcp.

Tools

Prompts to try

• "List my Hookpost channels. Write a launch post for LinkedIn and a shorter one for Threads, check both against the network limits, and save them as drafts for tomorrow 9:00."
• "Summarise the blog post at this URL as a LinkedIn post and save it as a draft in Hookpost."
• "List my Hookpost posts for the next 14 days and tell me which days have nothing scheduled on LinkedIn."

Command line

The hookpost CLI uses the same API key. It needs Node.js 18 or later.

npm install -g hookpost

hookpost auth login hookpost channels hookpost post "Hello" --channel abc123

With no --at, a post goes into the next free slot in your posting schedule. Add --at with an ISO date for an exact time, --now to publish straight away, or --draft to save a draft. In CI, set HOOKPOST_API_KEY instead of signing in. Source: cli/.

n8n

The n8n-nodes-hookpost community node creates, lists and deletes posts, lists channels, finds the next free slot and uploads media from a URL. In n8n, go to Settings → Community Nodes → Install and enter n8n-nodes-hookpost. Source: n8n-node/.

Plans and pricing

The MCP server, CLI and REST API come with Hookpost's Standard and Pro plans. New workspaces get 3 free posts with no card needed; then Standard is $19/month (₹599 in India) or Pro $29/month (₹1,999 in India). Current prices are at https://hookpost.hookstep.in/pricing.

What's in this repo

| server.json | The server's entry in the [official MCP Registry](https