Lets an AI client draft, validate, schedule and publish social media posts across 14 networks and review their analytics.
Also known as iHatePostingOrg/iHatePosting-Agent, agent-skill
- Stars
- 2
- Tools
- 17
- Downloads, 30 days
- 2,159
- Latest version
- 0.13.0
- Last commit
- Nov 13, 2026
- License
- MIT
What is iHatePosting MCP?
iHatePosting lets an AI client draft, validate, schedule and publish social media posts across 14 networks and review their analytics. It exposes 17 tools, such as open_upload_widget, get_upload_ticket, whoami.
Summary generated from the project's README
About iHatePosting MCP server
Managing social media presence across multiple platforms is what iHatePosting enables for developers and AI agents. By connecting to an existing iHatePosting account through a browser-based sign-in, users can allow agents like Claude, Cursor, or Gemini CLI to draft, validate, schedule, and publish content across 14 different networks including X, LinkedIn, Instagram, and TikTok. The server provides 16 specialized tools to handle everything from media uploads to analytics retrieval without requiring manual API key management for each individual platform.
This hosted MCP server allows for sophisticated content management, such as creating platform-specific text for Threads or YouTube titles, and managing media libraries. Users can instruct an agent to check a post against specific network rules using the validate_post tool before anything is actually published. Because the system defaults to saving content as a draft, nothing is sent live unless specifically requested. This setup provides a centralized way to monitor performance and manage post histories through a single AI interface.
What you can do with it
- 1Cross-platform content draftingAsk your AI to create different versions of an announcement tailored for LinkedIn, Bluesky, and X.
- 2Pre-publication rule validationVerify that a post meets character limits and media requirements for specific networks before it is saved.
- 3Social media performance reviewRequest a summary of how your posts have performed across different channels over a specific timeframe.
- 4Automated media managementUpload an image with alt text and prepare an Instagram post using that media.
Written from the project's README. Every use case is checked against a quote from it.
How to install iHatePosting MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall iHatePosting MCP in Claude Code
$ claude mcp add --transport http agent-skill https://app.ihateposting.com/api/mcp/oauthInstall iHatePosting MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"agent-skill": {
"url": "https://app.ihateposting.com/api/mcp/oauth"
}
}
}Install iHatePosting MCP in VS Code
.vscode/mcp.json
{
"servers": {
"agent-skill": {
"type": "http",
"url": "https://app.ihateposting.com/api/mcp/oauth"
}
}
}Install iHatePosting MCP in VS Code CLI
$ code --add-mcp '{"name":"agent-skill","type":"http","url":"https://app.ihateposting.com/api/mcp/oauth"}'Install iHatePosting MCP in Codex
$ codex mcp add agent-skill --url https://app.ihateposting.com/api/mcp/oauthInstall iHatePosting MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.agent-skill] url = "https://app.ihateposting.com/api/mcp/oauth"
Install iHatePosting MCP in Gemini CLI
$ gemini mcp add -s user --transport http agent-skill https://app.ihateposting.com/api/mcp/oauthInstall iHatePosting MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"agent-skill": {
"url": "https://app.ihateposting.com/api/mcp/oauth",
"type": "http"
}
}
}iHatePosting MCP tools 17
Read from the server with tools/listopen_upload_widgetRead-onlyShow the person their iHatePosting media box: they can upload an image or video from their own device, browse what is already in their library with every file previewable, see how much storage their plan leaves them, pick a file to use, or delete one. THIS IS THE ANSWER WHENEVER SOMEONE NAMES A FILE ON THEIR OWN COMPUTER — a path like C:\clips\launch.mp4 or ~/Movies/clip.mov is not something any tool here can read, and explaining that is not an answer: open this instead, in the same reply, and they pick the file from a picker right in the conversation. Also use it for anything they pasted or attached here. Do NOT try to send those bytes yourself — they would travel as your own output and arrive cut short. If the file already has a public address, use upload_media with `url` instead.
get_upload_ticketActionInternal: issues a short-lived ticket (10 minutes, reused by the upload box for its own requests) that the upload box uses to list, preview, upload and delete files. The upload box calls this itself.
whoamiRead-onlyWhich iHatePosting login this connection acts for (email and account name), whether it connected by signing in or with an API key, and the account owner's timezone (`ownerTimezone`) — the zone every scheduledDate/scheduledTime you send is read in. Use this for any question about who the user is or which account is connected, and before working out a time like 'tomorrow at 9' or 'in two hours'. This is NOT a social media handle — the handles from list_accounts belong to the connected profiles, which may carry other people's names.
get_platform_rulesRead-onlyWhat each platform will and will not accept: character limit, whether media is required, how many images, video formats and length, and EVERY per-platform option it takes — `options` per platform, each with its exact key, type, allowed values, default when left out, and whether it is required (e.g. Pinterest needs boardId, YouTube needs ytTitle and ytMadeForKids; YouTube's privacy is ytPrivacy, Instagram's first comment is firstComment). Call this BEFORE writing a post — it is the difference between composing something that publishes and something the platform rejects.
validate_postRead-onlyCheck a post against every platform you plan to send it to, WITHOUT creating anything. Runs the same checks create_post runs, so the answer is what will really happen: platform rules ('X counts this as 1200/280 characters', 'YouTube needs a title', 'TikTok slideshows take JPEG or WebP photos'), whether each account is connected and signed in, AND the account's own limits — trial expiry, whether the plan includes X, and the monthly posting allowances. Pass the same `action`/`scheduledDate`/`scheduledTime` you will pass to create_post: a cap counts the month the post is DUE, so checking without them answers a different question — and with no action it checks what create_post would make of no action, a draft, which no limit applies to. scheduledDate/scheduledTime are the account owner's wall clock in their timezone (`ownerTimezone` from whoami), and a date with an action other than 'schedule' is refused, as create_post refuses it. Anything not tied to one platform comes back under the key "account". It takes create_post's own `platforms` (platform names or account ids — an id checks that one account), `options`, `overrides` and `mediaIds`, so hand it exactly what you will hand create_post. `ok` is false only when something would stop the post; an issue with severity 'warn' (an image that will be cropped, images past a platform's cap) is worth telling the user but does not. Free to call as often as you like; use it before create_post rather than discovering a problem after the post is spent.
create_postActionCreate a social post on iHatePosting. action 'draft' saves it (the default when no date is given, and the safe choice); 'schedule' needs scheduledDate (YYYY-MM-DD) + scheduledTime (e.g. '9:00 AM' or '21:00'), the account owner's wall clock in their timezone — `ownerTimezone` from whoami, not yours or the user's device; 'now' publishes immediately to a real audience. A date with any action but 'schedule', or with no action, is refused rather than dropped. Every `scheduledAt` in the reply is UTC (it ends in Z); `scheduledLocal` beside it is the same moment as the owner's date, time and timezone — tell the user that one. Platforms with requirements — Pinterest a board, YouTube a title, TikTok and Instagram media — are set through `options` and `mediaIds`; call get_platform_rules for what each one needs, and validate_post to check before you commit. The reply lists every send it created, each naming its account (handle, displayName, nickname) AND carrying its own `postId` — tell the user what it says rather than what you asked for; they are not always the same. Its `warnings` name anything the post will not carry (images past a platform's cap, a signed-out account, a Pro-only option) — pass them on. A SCHEDULED (or 'now') multi-platform post is stored as one post per send, so that `postId` is what cancels or reschedules a single platform later without touching the others. A draft keeps every platform on ONE postId (every send in the reply shows the same one) until it is scheduled with update_post — deleting that draft deletes it for every platform.
list_postsRead-onlyList posts with per-platform status (draft/scheduled/published/failed) and live URLs. Rows sharing a `batchId` are ONE submission the person made to several accounts — report them as one post going to N places, not as N posts. ALWAYS CHECK `total` IN THE REPLY: it is the number of rows matching your filter, and `returned` is how many you got. If they differ you are holding one page, not the answer — page on with `cursor` until `hasMore` is false before you count anything or tell anyone a number. `total` counts ROWS: a scheduled post to several accounts is one row per platform (sharing a `batchId`), while a draft is one row however many platforms it has — so `total` is the number of sends, and the number of posts the person made is the rows with distinct `batchId`s (a row without one is a post on its own). A post you move LATER while paging can come round again on a later page — skip ids you have already handled; none are skipped. Use `status` and `from`/`to` to ask the real question instead of counting a page: for "how many are scheduled" pass status 'scheduled' and read `total` (sends); for a month or a date range pass from/to, which match the SCHEDULED time — a bare date is that whole day on the account owner's calendar, in the owner's timezone (the reply's `timezone`, `ownerTimezone` from whoami). Each post's `scheduledAt` is UTC (it ends in Z); `scheduledLocal` is the same moment as the owner's date and time — report that one, and send it back unchanged to reschedule_post or update_post.
list_accountsRead-onlyList the connected social accounts (platform, handle, health) available for posting. The response also names the iHatePosting account this connection acts for — if the accounts listed are not the ones you expect, check that `account.email` is the right person before assuming anything is missing. `account.timezone` is the owner's timezone, the zone every scheduled time is read in. An empty `accounts` array means nothing is connected yet — nothing can be posted, scheduled or read until the user connects at least one account at https://ihateposting.com/accounts; tell them that rather than retrying or guessing a platform.
list_pinterest_boardsRead-onlyThe Pinterest boards you can pin to, with the `id` that create_post's `options.pinterest.boardId` requires. Pinterest REFUSES a pin without a board, and a board id is an opaque number you cannot guess — call this before creating any Pinterest post. If several Pinterest accounts are connected, pass `accountId` from list_accounts, because boards belong to one account and pinning to another account's board fails. An empty list with no error means the account is connected and simply has no boards yet — make one in Pinterest first.
get_analyticsActionHow the posts actually performed: impressions, engagement and follower numbers per connected channel, plus the top posts. Use this to answer 'how did that do', 'which platform is working' or 'what should I post more of' — it reports what iHatePosting collected from each network, not an estimate. Some platforms report nothing (they are named in `unmeasuredPlatforms`), so a zero there means 'not measurable', not 'no reach'. If a plan ever gates a range, the answer says so in a sentence with `locked: true` rather than returning silently empty numbers.
reschedule_postActionMove a SCHEDULED post to a different date and time. ONE SEND AT A TIME: a scheduled post going to several accounts is stored as one post per send, so this moves just that platform and leaves the others where they are (an older row can still carry several platforms, and moves them together). A draft is refused: schedule a draft with update_post with action 'schedule', which checks each platform first and gives each its own post. Takes the post id from list_posts, plus scheduledDate (YYYY-MM-DD) and scheduledTime (e.g. '9:00 AM') read in the ACCOUNT OWNER'S timezone (`ownerTimezone` from whoami), not yours or the user's device. A post's `scheduledAt` is UTC (it ends in Z) — never copy its digits as a time; work from `scheduledLocal` (the owner's date and time) that list_posts and get_post give beside it, so 'an hour later' is an hour later. The reply's `scheduledLocal` is where the post now is. A post that has already published cannot be moved — its time is a record of what happened — and one that is publishing right now is refused until it finishes. A FAILED post is not rescheduled either: there is no upcoming slot to move, and moving it would not re-send it. Send it again with retry_post, which re-queues only the sends that failed; reschedule_post is for a post that is still scheduled. Check `status` from list_posts before calling this — on 2026-10-15 one agent called it on ten failed posts in a minute and was refused ten times.
list_mediaRead-onlyThe images and videos already in the user's iHatePosting library, newest first, with the `id` that create_post's `mediaIds` wants. Call this whenever a platform needs a file — Instagram, Pinterest, TikTok and YouTube all do — to see whether what you need is already uploaded. Returns ids and dimensions only; there is no downloadable link, by design.
Show all 17 toolsShow fewer tools
upload_mediaActionPut an image or video into the library and get back an id for create_post. PREFER `url` — ALWAYS, including for a picture you just generated: we fetch it ourselves at full length, and it is the only thing that works for video or for anything more than a few kilobytes. We take whatever the link serves, so a CDN that will not name the type (application/octet-stream, as presigned S3, Drive and Dropbox links do) is fine. `base64` is a last resort for small files that exist at no address: it travels as your own output, a conversation truncates it, and the cut-off file is refused. Either way the API checks type, size and quota, then registers the file.
get_postRead-onlyEverything about ONE post: the shared text, each platform's own copy and options, the attached media, and per-send status with the live URL or the error. list_posts gives you the id; this explains what actually happened to it. Read it before update_post so you change what is there rather than overwriting it. Its `scheduledAt` is UTC (it ends in Z); `scheduledLocal` is the same moment as the owner's date, time and timezone — the values to send back as scheduledDate/scheduledTime to keep the time, and the ones to tell the user.
update_postActionRewrite a draft or scheduled post. THIS REPLACES THE WHOLE POST, so read it with get_post first and send back the complete set — anything you leave out is removed, including platforms and per-platform options. Note the shape differs from create_post: this one wants `accountIds` (the ids from list_accounts, NOT platform names) and it requires `action`. Two limits: a post that has already published cannot be rewritten at all, and a post that goes to several platforms and was saved as a group keeps the platforms it has — send back that row's own accountIds and everything else is editable, but adding or swapping an account is refused with a sentence saying so, because it would publish some platforms twice. To change which platforms a group posts to, delete it and create it again. A draft is not a group: to drop one platform from a draft, send it back without that account. SCHEDULING A DRAFT that goes to several platforms (action 'schedule' or 'now') turns it into one post per platform: the reply's `rows` lists every `postId` with its platforms, and the id you sent now names only its first platform — use the others' ids to move, cancel or retry them. A post that is being published right now cannot be edited; the answer says so — wait for it to finish. Like create_post, its reply's `warnings` name anything the post will not carry — pass them on. TIMES: scheduledDate/scheduledTime are the owner's wall clock (`ownerTimezone` from whoami); to keep a scheduled post's time, send back get_post's `scheduledLocal.date` and `scheduledLocal.time` — never the digits of its UTC `scheduledAt`. A date with an action other than 'schedule' is refused. The reply's `scheduledAt` (UTC) and `scheduledLocal` say when it now goes out.
retry_postActionSend a failed post again. ONE SEND AT A TIME, usually: a post to several accounts is stored as one post per send, so a post id normally names a single platform and retrying it touches only that one. (An older row, or a draft, can still carry several — without targetId every failed platform on that row is retried; with one, only that send.) Only a send that FAILED is retried — one that published is left alone. But a send marked failed can already be live (a timeout after the network took the post), so after a timeout check the platform before retrying. A send our own checks SKIPPED is not retried — the answer says why, and update_post is the fix. If the cause was the account rather than the post (a revoked or paused connection) the answer says so, and retrying will not help until the user reconnects. The reply's `retried` counts what went back on the queue and `skipped` names every send it left behind, with the reason.
delete_postActionDelete a post from iHatePosting. ONE SEND AT A TIME: a SCHEDULED post going to several accounts is stored as one post PER SEND, so deleting one cancels only that platform and leaves the rest scheduled — pass the `postId` that create_post returned on that particular send, or the id of the row list_posts shows for it. There is no need to cancel a whole multi-platform post to drop one platform from it. A DRAFT IS DIFFERENT: until it is scheduled, a draft is ONE post holding every platform it is aimed at (all its sends share one postId), so deleting it removes every platform — to drop one platform from a draft, use update_post with the remaining accountIds instead. The reply's `platformsRemoved` names every platform the delete took; for one send of a group, `stillScheduled` lists the sends still going out and `otherSends` the rest of the group (already published or failed), each with its status; their `scheduledAt` is UTC (it ends in Z) and `scheduledLocal` is the same moment in the account owner's timezone — report that one. THIS DOES NOT UNPUBLISH ANYTHING: a post that has already gone out stays live on the network, and deleting it here only removes iHatePosting's record of it. For that reason a published post is refused unless you pass force: true, and you should only do that after telling the user in words that the platform post will remain. A post that is publishing at this moment is never deletable, forced or not — the worker is mid-flight on it. Deleting a scheduled post stops it going out.
Automated checks
Ran Nov 16, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachableihatepostingorg/agent-skill is public and reachablegithub.com/ihatepostingorg/agent-skill ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-13github.com/ihatepostingorg/agent-skill ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from ihateposting-mcpPass
- No critical advisory in the package or its dependenciesthe package checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model17 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledDestructive tools carry destructiveHintPass
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubiHatePosting for AI agents
Let Claude, Claude Code, Cursor, Gemini CLI, Grok Build, Kimi Code or Qwen Code draft, check, schedule and publish posts on 14 social networks, using the accounts you have connected at ihateposting.com. This package gives each agent the hosted iHatePosting MCP server (16 tools) and a skill that teaches it to post safely. Every agent here signs in with your iHatePosting account; none of them needs an API key.
GitHub Copilot in VS Code uses the same hosted server: Install in VS Code, then sign in with your iHatePosting account in the browser. There is no API key to paste. The steps are under Install.
Set-up pages for every agent: Claude · Claude Code · Claude Cowork · ChatGPT · Codex · Cursor · Gemini CLI · Grok Build · VS Code and GitHub Copilot · OpenClaw · Hermes Agent · DeepSeek Harness · Perplexity Computer · Muse · NanoClaw · Paperclip · Antigravity CLI · Amp · Cline · Kilo Code · Zed · Warp · Devin Desktop · OpenHands CLI · Freebuff CLI · omp · all of them
Some of those pages add the server by hand, with an API key; for Claude, Claude Code, Cursor, Gemini CLI, Grok Build, Kimi Code and Qwen Code, the plugin in this repository signs in instead (Install).
Nothing goes out unless you say so. A new post is saved as a draft unless you ask for it to be published now or at a set time.
What your agent can do
- Draft, schedule or publish one post to several networks at once, either to every account you have on a network or to one account you pick. A time such as "9:00 AM" is read in the timezone set in your iHatePosting settings (Settings → Scheduling), not your computer's.
- Check a post before it exists.
validate_postruns the checks the publisher runs just before it posts, and creates nothing. It also tells you when a network has no connected account, or one that needs reconnecting. - Learn each network's rules: character limit, media rules and the options a network requires, such as a Pinterest board.
- Write per network: different text for one network, and that network's own settings. That covers threads on X, Bluesky, Threads and Mastodon, a first comment on Instagram, LinkedIn and Threads, Instagram Reels, Stories and carousels, Facebook Reels and Stories, TikTok photo posts and privacy, and a YouTube video's title, privacy and playlist.
- Attach media: upload an image or a short video with alt text, or reuse anything already in your media library.
- Manage what is already there: see what happened on each network, rewrite a draft, scheduled or failed post, move it to another time, resend only what failed, or delete it.
- Report results: per-channel numbers, follower counts, posting times and top posts, from 7 days back to everything recorded.
Every plan includes the API key that the MCP server, the REST API and the CLI use. Webhooks come with every plan too.
Tools
The hosted server offers these 16 tools, plus one the upload box uses by itself. The last column is what a tool does to your posts and accounts.
| Tool | What it does | Effect |
|---|---|---|
whoami |
Names the iHatePosting login this connection acts for (email and account name), whether it signed in or uses a key; not a social handle | Reads |
list_accounts |
Lists connected social accounts with platform, handle, status and id | Reads |
get_platform_rules |
Each network's character limit, media rules, video formats and length, and every option it takes, with the allowed values | Reads |
validate_post |
Checks a post against every network you name, without creating anything | Reads |
create_post |
Creates a post: a draft by default, or now or schedule when asked |
Creates; publishes with now or schedule |
list_posts |
Posts with each network's status and live URL — filter by status and a from/to scheduled-date range, page with cursor, and read total for the real count |
Reads |
get_post |
One post in full: text, per-network copy and options, media, and each send's result or error | Reads |
update_post |
Replaces a draft, scheduled or failed post with what you send | Changes; publishes with now or schedule |
reschedule_post |
Moves a scheduled post to a new date and time; refuses a draft | Publishes at the new time |
retry_post |
Sends again only what failed, on one network or all of them | Publishes |
delete_post |
Removes iHatePosting's record of a post; a published post needs force |
Deletes; never unpublishes |
list_media |
Your media library, newest first, with the ids posts attach | Reads |
upload_media |
Adds an image or video to the library and returns its id — from a url (preferred; up to 100 MB, images up to 25 MB) or as base64 (up to 8 MB) |
Creates a library file |
open_upload_widget |
Shows a file picker in the conversation so the person can upload from their own device | Creates a library file |
get_upload_ticket |
Internal — the upload box calls this itself for a one-time upload credential. Registered visibility: ["app"], so a host hides it from the model and it is not a tool an agent calls |
Issues a short-lived credential |
list_pinterest_boards |
The Pinterest boards you can pin to, with the board id a pin needs | Reads |
get_analytics |
How posts performed, per connected channel, over a range you choose | Reads |
Networks
All 14 networks work through the same tools. Name one in platforms
(bluesky, x, linkedin, facebook, threads, mastodon, telegram,
discord, tumblr, slack, instagram, pinterest, tiktok, youtube),
or pass an account id from list_accounts.
| Network | Text limit | Media | You must set | Also supports |
|---|---|---|---|---|
| Bluesky | 300 | Up to 4 images; video | Multi-post threads, alt text | |
| X | 280, weighted (a link counts 23) | Up to 4 images; video | Multi-post threads, reply settings | |
| 3,000 | Up to 20 images; video | Company Pages and personal profiles, first comment | ||
| 63,000 | Up to 10 images; video | Pages, Reels, Stories | ||
| 2,200 | Required: up to 10 images or videos | Reels, Stories, carousels, first comment, collaborators, tagged accounts | ||
| Threads | 500 | Up to 20 images or videos | Multi-post threads, carousels, first comment | |
| 800 | Required: an image or a video | A board | Pin title and destination link | |
| TikTok | 2,200 | Required: a video, or photos (up to 20 per post here) | Privacy, send to your TikTok inbox, AI-generated label, comment, duet and stitch settings | |
| YouTube | 5,000 (description) | Required: one video | A title, and made for kids yes or no | Privacy, playlist, tags, category, custom thumbnail |
| Mastodon | 500 | Up to 4 images; video | Multi-post threads, visibility, alt text | |
| Telegram | 4,096 (1,024 as a caption under media) | Up to 10 images; video | ||
| Discord | 2,000 | Up to 10 images; video | ||
| Tumblr | 4,096 | Up to 20 images per post; video | Title, tags | |
| Slack | 3,000 | Up to 5 images; video |
If you leave them out, create_post fills a YouTube title and a Pinterest
pin title from the first line of your text, a Pinterest link from the first
URL in it, and YouTube and Tumblr tags from its hashtags. validate_post does
not fill them in, so it reports a missing YouTube title as a problem.
What each network accepts, with its main options, is in docs/platforms.md. The option keys a post is likely to need, with their values and defaults, are in the reference the skill loads when it needs it (skills/ihateposting/references/platform-options.md). A post can attach at most 20 media items, whatever a network allows.
Example prompts
- "What is scheduled to go out this week, and did anything fail?"
- "Draft this announcement for LinkedIn, Bluesky and X. Give X a shorter version, and check all three before you save."
- "Turn these notes into a thread for X and Threads and save it as a draft."
- "Upload this photo with alt text and draft an Instagram post with it. Put the hashtags in the first comment."
- "Which of my Pinterest boards suits this recipe? Draft a pin to it."
- "Why did yesterday's LinkedIn post fail?"
- "How did my posts do over the last 30 days, and which network did well?"
examples/ has ready-made create_post payloads for threads,
Reels, carousels, YouTube, Pinterest, TikTok and more. Every one is a draft.
Install
Every agent below signs you in to your iHatePosting account in the browser. None of them needs an API key.
| Agent | How it installs | How it connects |
|---|---|---|
| Claude (claude.ai, desktop app, Cowork) | Customize → Plugins on a paid Claude plan, adding this repository as a marketplace | You sign in in the browser |
| Claude Code | /plugin install from this repository's marketplace |
You sign in in the browser |
| Cursor | Cursor Marketplace once listed, a local copy, or ~/.cursor/mcp.json |
You sign in in the browser |
| VS Code with GitHub Copilot | The Install in VS Code link, or .vscode/mcp.json |
You sign in in the browser |
| Gemini CLI | gemini extensions install |
You sign in in the browser |
| Grok Build | grok plugin install ... --trust |
You sign in in the browser |
| Kimi Code | /plugins install inside Kimi Code |
You sign in in the browser |
| Qwen Code | qwen extensions install |
You sign in in the browser |
| Any agent that reads skills | npx skills add (the skill only) |
Connect the server as that agent's page says |
| ChatGPT and others | Their own MCP settings | See the setup guide |
In Customize → Plugins, choose Add → Add marketplace, enter
https://github.com/iHatePostingOrg/agent-skill and install iHatePosting.
Then open the plugin's Connectors tab and connect iHatePosting: you sign
in to your iHatePosting account and press Allow. There is no key to paste.
Already added the iHatePosting connector from Claude's directory? The plugin uses the same address, so you get one set of tools, not two.
Plugins need a paid Claude plan (Pro, Max, Team or Enterprise). On the Free plan, add iHatePosting from Claude's connector directory instead: it signs in the same way and gives the same tools, without this plugin's skill.
/plugin marketplace add iHatePostingOrg/agent-skill
/plugin install ihateposting@ihateposting
Then run /mcp, pick the iHatePosting server and choose Authenticate. A
browser window opens: sign in to your iHatePosting account and press
Allow. There is no key to paste.
- Already added iHatePosting by hand? Remove that entry with
claude mcp remove ihateposting, or every tool shows up twice. - Coming from 0.3.x? Earlier versions asked for an API key. After the
update, authenticate once from
/mcpas above; the plugin no longer sends the key.
Once the plugin is listed in the Cursor Marketplace, open Customize in
Cursor's sidebar, find iHatePosting and choose Install, for one
project or for all of them. Cursor signs you in to your iHatePosting account
in the browser; press Allow. Each person on a Cursor team signs in as
themselves, so nobody posts from someone else's account. On a Cursor
Enterprise plan with an MCP allowlist, allow https://ihateposting.com/mcp/oauth.
Before the listing, install a local copy. Clone or copy this repository into
~/.cursor/plugins/local/ihateposting (on Windows,
%USERPROFILE%\.cursor\plugins\local\ihateposting). Cursor skips a symlink
there that points to a folder somewhere else, so copy the files. Then restart
Cursor or run Developer: Reload Window, and check under Customize
that the iHatePosting skill and MCP server are listed. On Teams and
Enterprise plans, an admin controls this with Allow Local Plugin
Imports, which is off by default on Enterprise. Once you install the
Marketplace version, it is used instead of the local copy.
If you already added the server by hand in ~/.cursor/mcp.json, remove that
entry when you install the plugin, so there is one iHatePosting server.
To add only the server by hand, put this in ~/.cursor/mcp.json and restart
Cursor:
{
"mcpServers": {
"ihateposting": {
"type": "http",
"url": "https://ihateposting.com/mcp/oauth"
}
}
}
Then open Customize, then MCPs, turn iHatePosting on and press Connect to sign in.
The same configuration as a one-click link:
cursor://anysphere.cursor-deeplink/mcp/install?name=ihateposting&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vaWhhdGVwb3N0aW5nLmNvbS9tY3Avb2F1dGgifQ==
Choose
Install in VS Code
(or VS Code Insiders),
or add the server to .vscode/mcp.json in your project:
{
"servers": {
"ihateposting": {
"type": "http",
"url": "https://ihateposting.com/mcp/oauth"
}
}
}
VS Code's file uses servers as its top-level key, not mcpServers like
most other editors, so a block copied from a Cursor setup will not load. The
file holds no secret and is safe to commit.
When the server first starts, VS Code asks you to sign in. A browser window opens: sign in to your iHatePosting account and press Allow. There is no key to paste. Then open Copilot Chat in agent mode, where the iHatePosting tools appear in the tools list, and ask it to draft a post.
On Copilot Business or Enterprise, your organization's admin may need to allow MCP servers in its Copilot policy first.
gemini extensions install https://github.com/iHatePostingOrg/agent-skill
No API key. The next time you start Gemini CLI, it connects to the server
and opens your browser: sign in to iHatePosting and press Allow. It keeps
the token in ~/.gemini/mcp-oauth-tokens.json and refreshes it as needed.
Sign in again later with /mcp auth ihateposting.
Gemini CLI could not have taken our key from a header anyway: it expands
${...} in MCP headers against a sanitized environment and blanks any
variable whose name contains KEY, TOKEN, SECRET or AUTH, so a header built
from our key variable would leave empty and every call would fail, with
nothing in Google's docs to warn you. Signing in avoids the problem rather
than working around it.
The extension uses url with type: "http", the form Gemini CLI 0.21 and
later reads as Streamable HTTP.
grok plugin install iHatePostingOrg/agent-skill --trust
A plugin's MCP server stays off until the plugin is trusted, which is what
--trust does. Then start grok, open /mcps, select ihateposting and
press i: Grok Build opens your browser, you sign in to your iHatePosting
account and press Allow. The tools appear once you have signed in. To
sign in again later, do the same.
Inside Kimi Code:
/plugins install https://github.com/iHatePostingOrg/agent-skill
Kimi Code installs this repository's latest release and reads its
.kimi-plugin/plugin.json, which adds the server and the skill. When the
server first says it needs a sign-in, Kimi Code offers an authenticate
step: approve it, and your browser opens; sign in to iHatePosting and press
Allow. You can also run /mcp to see the server's name and then
/mcp-config login with that name. There is no key to paste. Kimi Code keeps
the token under ~/.kimi-code/credentials/mcp/.
Kimi Code's manifest names the server inline rather than in a separate file,
with transport set to http (Streamable HTTP). This was read from Kimi
Code's source (release 2.1.1); it has not yet been run in Kimi Code itself.
qwen extensions install iHatePostingOrg/agent-skill:ihateposting
Then open /mcp in Qwen Code, select iHatePosting and choose
Authenticate. A browser window opens: sign in to your iHatePosting account
and press Allow. There is no key to paste. Qwen Code keeps the token in
~/.qwen/mcp-oauth-tokens.json and refreshes it as needed; to sign in again
later, choose Re-authenticate in the same place.
The :ihateposting at the end names the plugin, so Qwen Code does not ask
which one to install. It reads this repository's own qwen-extension.json,
which adds the server and the skill. That file sets httpUrl rather than
url, because Qwen Code reads a bare url as the older SSE transport, which
this server does not speak.
ChatGPT, Codex, OpenClaw, Hermes Agent, DeepSeek Harness, Perplexity Computer, Zed, Cline and more connect to the same server without this package. Each has a set-up page (the list at the top of this README), and the setup guide covers them all.
OpenClaw's documentation says it reads a package with a .cursor-plugin/
folder as a Cursor bundle, so installing this repository there is not
expected to add the MCP server. Use OpenClaw's own MCP setup from its page
instead.
The skill is listed on skills.sh, so an agent that reads skills can take it from there:
npx skills add https://github.com/ihatepostingorg/agent-skill --skill ihateposting
That copies the skill only. It does not connect the iHatePosting server:
connect that as your agent's set-up page describes. The skill works through
the server's tools; the ihateposting command line
(below) is a separate tool with its own
instructions (ihateposting skill --print).
Get an API key
None of the agents above needs one. A key is for the ihateposting command
line, the local npm server, the REST API, and agents that cannot sign in.
Sign in at ihateposting.com, open Settings →
Developers and create a key. It starts with pk_live_, and you can show it
again later from the same page (a key made before keys could be shown again,
in late September 2026, cannot be; the page says so, and regenerating gives
you one that can). There is one key per account:
regenerating switches the old one off everywhere it is used. The key can post
on your behalf, so keep it out of chats, screenshots and shared files.
iHatePosting MCP questions
How do I add iHatePosting MCP to Claude Code?
Run claude mcp add --transport http agent-skill https://app.ihateposting.com/api/mcp/oauth in your terminal. Add --scope user to make it available in every project.
How do I add iHatePosting MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does iHatePosting MCP provide?
It exposes 17 tools, including open_upload_widget, get_upload_ticket, whoami, get_platform_rules, validate_post.
Which social networks can iHatePosting post to?
It supports 14 networks, including Bluesky, X, LinkedIn, Facebook, Threads, Instagram, Pinterest, TikTok, YouTube, Mastodon, Telegram, Discord, Tumblr and Slack.
Are posts published immediately or saved as drafts?
Posts are saved as drafts by default; publishing happens only when you ask for it now or at a scheduled time.
Do I need an API key to connect iHatePosting?
No, the plugin signs you in to your iHatePosting account in the browser. Some setup pages add the server by hand with an API key instead.
Can an agent check a post without creating it?
Yes, the validate_post tool runs the same checks the publisher uses and creates nothing.
What media can be attached to a post?
You can upload images or short videos with alt text, or reuse items already in your media library.