X (Twitter)
Hermoso is a marketing MCP server. Connect X (Twitter) once and it becomes callable from Claude, ChatGPT, Claude Code, Cursor, Codex, Cline or the CLI — the same connection the web app uses, so nothing is duplicated and nothing is re-authorised per client.
What Hermoso does with X (Twitter)
Post, thread, poll or reply, read performance and mentions, answer DMs — X keeps only 30 days of them. X charges per API call, so every action costs credits.
Publishing: Publish · Threads · Analytics · DMs · Mentions
Driving it from an agent
The X (Twitter) tools an agent can call, by name (16 today):
delete_x_post edit_x_post list_x_dms post_to_x post_x_article search_x send_x_dm x_account x_follows x_mentions x_post_insights x_post_insights_historical x_post_metrics x_search_counts x_trends x_user
Connecting
Open the app, go to Workspace ▸ Connectors and connect X (Twitter). One authorisation covers the web app, the MCP server and the CLI. See MCP & CLI for the endpoint and the client setup, or every channel we connect to.
Frequently asked questions
Can an AI agent post to X (Twitter) through Hermoso?
Yes. The X (Twitter) surface is exposed over one OAuth'd MCP endpoint, so Claude, ChatGPT, Cursor, Codex, Cline and the CLI can all drive it once the account is connected.
Do I need a separate X (Twitter) connection for the app and for MCP?
No. One authorisation covers the web app, the MCP server and the CLI — it is the same stored connection.