Social Media
ihateposting.com
MCP server for iHatePosting that validates, creates, and lists social media posts across multiple platforms.
ENDPOINT 1
https://ihateposting.com/api/mcp
MCP server metadata
- Name
- ihateposting
- Version
- 0.3.0
Known tools 6
whoamiWho the API key belongs to: the iHatePosting login (email and account name).
Potential side effectsget_platform_rulesWhat each platform will and will not accept: character limit, whether media is required, how many images, video formats and length, and which per-platform options are MANDATORY (e.
Inferred read-onlyvalidate_postCheck a post against every platform you plan to send it to, WITHOUT creating anything.
Potential side effectslist_postsList the 50 most recent iHatePosting posts with per-platform status (draft/scheduled/published/failed) and live URLs.
Inferred read-onlylist_accountsList the connected social accounts (platform, handle, health) available for posting.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.ihateposting]
url = "https://ihateposting.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"ihateposting": {
"type": "http",
"url": "https://ihateposting.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: ihateposting
Remote MCP URL: https://ihateposting.com/api/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"ihateposting": {
"url": "https://ihateposting.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"ihateposting": {
"type": "http",
"url": "https://ihateposting.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "ihateposting",
"transport": "streamable-http",
"url": "https://ihateposting.com/api/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.