# ihate.social — agent setup and availability

> Current status: invite-only beta. The MCP connector is live at https://ihate.social/mcp and signs in with OAuth.

## Setup destination

- Human-readable guide: https://ihate.social/agents
- These instructions: https://ihate.social/llms.txt
- Website workspace: https://ihate.social/studio
- Support: https://ihate.social/contact

Access is by invitation during the beta, and sign-ups are closed. If you encounter a sign-in gate, the user does not have access yet; tell them to ask for an invite at https://ihate.social/contact. Do not bypass the gate or copy browser cookies.

## Connection

MCP server URL: https://ihate.social/mcp
Authentication: OAuth. The user signs in to ihate.social and approves the connection in their browser. Your client discovers the rest from the server URL.
Verified MCP clients: Claude, Claude Code and ChatGPT.

Add the server URL as a remote MCP server (in Claude and ChatGPT, a custom connector). Use no API key, header or token. Do not invent other endpoints or client configuration. Do not request the user's social passwords or ihate.social's provider API keys. Do not represent browser endpoints as authenticated MCP tools.

## What the connector does

For now the connector does one thing: it helps the user reply well on X. Read the customer's saved voice, set up or refresh it with them, list the posts on X worth answering with the reason and talking points, look for new ones, draft a reply in their voice when they ask, note what they did with each, and review their comments and messages. These work for the user's connected X account. Reading the inbox needs the inbox permission, granted when the user connects.

The connector does not draft, schedule or publish posts, and offers no tools for them. It never sends a reply: the user posts every reply themselves. Do not write a post for the user through this connector.

The user can see and revoke connected assistants in their settings.