Post to social media from OpenClaw
Give your OpenClaw agent iHatePosting and it can draft, check and schedule posts across 14 networks as part of its work — once one line of its config is right.
Set it up
1. Create an iHatePosting API key
Sign in, open Settings → Developers and create a key. It starts with pk_live_ and is shown in full only once, so copy it before you leave the page.
2. Add iHatePosting to OpenClaw
Add to ~/.openclaw/openclaw.json on the machine that runs the OpenClaw Gateway. The file is JSON5, so comments and trailing commas are fine. Replace YOUR_API_KEY with your key.
{ "mcp": { "servers": { "ihateposting": { "url": "https://ihateposting.com/mcp", "transport": "streamable-http", "enabled": true, "headers": { "Authorization": "Bearer YOUR_API_KEY" } } } } }3. Ask it to post
Tell OpenClaw what you want to say and where. It saves a draft in iHatePosting unless you ask for the post to go out now or at a set time.
What is different about OpenClaw
- The transport line is not optional. OpenClaw treats a bare url as an SSE server by default, and ours serves only Streamable HTTP — without transport set to streamable-http the server never connects, and nothing in the config says why.
- The block nests under mcp, then servers — not a bare mcpServers root.
- openclaw.json is JSON5, so comments and trailing commas are fine, and the Gateway reloads the file as soon as you save it.
- OpenClaw expands environment variables in headers, but one that is not set is sent literally, so writing the key is the reliable choice.
- From the command line (OpenClaw 2026.6.1 or later), openclaw mcp add ihateposting --url https://ihateposting.com/mcp --transport streamable-http --header "Authorization=Bearer YOUR_API_KEY" writes the same entry, so use it instead of editing the file, not as well: it refuses a name that already exists. Note the = between the header name and value. It connects before saving, but our server answers without a valid key, so that proves the address, not the key; ask your agent to run whoami for that. openclaw mcp doctor ihateposting --probe checks it later, and warns that the header holds a literal secret, which is expected when the key is written in.
Limits. Streamable HTTP needs OpenClaw 2026.3.31 or later. Adding a server from Settings or the composer needs administrator access, and its quick form has no header field: add the Authorization header in the config editor on the same Settings page, or the server connects but every tool says there is no API key.
OpenClaw's own documentation: OpenClaw MCP
Nothing goes out unless you say so
Every post OpenClaw writes is saved as a draft in iHatePosting unless you ask for it to be published now or at a set time. Publishing, rescheduling, retrying and deleting are marked as actions that change things, so clients that honour those markings ask you before they run them. Deleting a post in iHatePosting never removes one that is already live on a network.
Frequently asked questions
Why does OpenClaw never connect to iHatePosting?
The transport line is missing. OpenClaw treats a bare url as an SSE server by default, and ours serves only Streamable HTTP, so set transport to streamable-http. Streamable HTTP needs OpenClaw 2026.3.31 or later.
Where does the block go in openclaw.json?
Under mcp, then servers, not a bare mcpServers root. The file is JSON5, so comments and trailing commas are fine, and the Gateway reloads it as soon as you save.
Is there a command instead of editing the file?
Yes, on OpenClaw 2026.6.1 or later: openclaw mcp add with --url, --transport streamable-http and the Authorization header writes the same entry. It proves the address, not the key, so ask your agent to run whoami afterwards.
Ready to post everywhere from OpenClaw?
Start your 90-day free trial — no credit card, about a minute to your first post.
Sign Up
