How to connect X (Twitter) to Hermes Agent
Connect X (Twitter) to Hermes with ClawLink: paste your X (Twitter) key once and 84 tools work from chat. No MCP server to run, nothing stored on your machine.
X (Twitter)OAUTH2MCPPost tweets, manage lists, search content, and analyze engagement. Once connected, Hermes Agent can read and act on X (Twitter) from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent X (Twitter) access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical X (Twitter) setup: pair once in the browser and your always-on Hermes agent can act on X (Twitter) for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect Hermes to X (Twitter).
- 1
Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable - 2
Connect X (Twitter)
Enter your account details in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with X (Twitter)?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin # prints an approval link — open it and approve
hermes clawlink finish # after approving in the browser
hermes clawlink testThen connect X (Twitter) in the ClawLink dashboard — enter your X (Twitter) account details once.
Verify the connection by asking Hermes:
Use X (Twitter) to bookmarks by user and walk me through the result in plain English.
Using a different agent?
The Hermes plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once X (Twitter) is connected in the dashboard, that agent calls the same 84 X (Twitter) tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
X (Twitter) MCP for Hermes
Looking for a X (Twitter) MCP server for Hermes Agent? ClawLink connects X (Twitter) to Hermes Agent and exposes 84 X (Twitter) tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw X (Twitter) integration works the same way.
What the Hermes Agent X (Twitter) integration can do
84 X (Twitter) tools are ready for Hermes Agent once the account is connected. The 30 below are the ones people reach for most; your agent can call all 84.
30 of 84 X (Twitter) tools for Hermes
| Tool | What it does |
|---|---|
Bookmarks by user twitter_bookmarks_by_user | List your X bookmarks |
Creation of a post twitter_creation_of_a_post | Post or reply on X |
Follow user twitter_follow_user | Follow a user on X |
Followers by user ID twitter_followers_by_user_id | List followers of an X user |
Recent search twitter_recent_search | Search recent X posts |
Retweet post twitter_retweet_post | Repost an X post |
Send a new message to a user twitter_send_a_new_message_to_a_user | Send a direct message on X |
Upload media twitter_upload_media | Upload an image for an X post |
User home timeline by user ID twitter_user_home_timeline_by_user_id | Read your X home timeline |
User like post twitter_user_like_post | Like an X post |
User lookup by username twitter_user_lookup_by_username | Look up an X user by username |
Following by user ID twitter_following_by_user_id | Retrieves users followed by a specific Twitter user, allowing pagination and customization of |
Full archive search twitter_full_archive_search | Searches the full archive of public Tweets from March 2006 onwards; use 'start_time' and |
Get blocked users twitter_get_blocked_users | Retrieves the authenticated user's own block list |
Get compliance job twitter_get_compliance_job | Retrieves status, download/upload URLs, and other details for an existing Twitter compliance |
Get compliance jobs twitter_get_compliance_jobs | Returns a list of recent compliance jobs, filtered by type (tweets or users) and optionally by |
Get dm conversation events twitter_get_dm_conversation_events | Fetches Direct Message (DM) events for a one-on-one conversation with a specified participant |
Get dm event twitter_get_dm_event | Fetches a specific Direct Message (DM) event by its unique ID, allowing optional expansion of |
Get list twitter_get_list | Returns metadata for a specific Twitter List, identified by its ID; does not return list |
Get list followers twitter_get_list_followers | Fetches a list of users who follow a specific Twitter List, identified by its ID; ensure the |
Get list members twitter_get_list_members | Fetches members of a specific Twitter List, identified by its unique ID |
Get media upload status twitter_get_media_upload_status | Get the processing status of uploaded media (videos/GIFs) on X/Twitter |
Get muted users twitter_get_muted_users | Returns user objects muted by the X user identified by the id path parameter |
Get openapi spec twitter_get_openapi_spec | Fetches the OpenAPI specification (JSON) for Twitter's API v2, used to programmatically |
Get post analytics twitter_get_post_analytics | Retrieve analytics data for specified Posts within a defined time range |
Get post retweeters action twitter_get_post_retweeters_action | Retrieves users who publicly retweeted a specified public Post ID, excluding Quote Tweets and |
Get post retweets twitter_get_post_retweets | Retrieves Tweets that Retweeted a specified public or authenticated-user-accessible Tweet ID |
Get post usage twitter_get_post_usage | Fetches Tweet usage statistics for a Project (e.g., consumption, caps, daily breakdowns for |
Get recent dm events twitter_get_recent_dm_events | Returns recent Direct Message events for the authenticated user, such as new messages or |
Get space by ID twitter_get_space_by_id | Retrieves details for a Twitter Space by its ID, allowing for customization and expansion of |
Try it: find the X (Twitter) tool you need
Browse the 30 X (Twitter) tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use X (Twitter) to bookmarks by user and walk me through the result in plain English.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual integration setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want X (Twitter) working from chat.
| Manual | ClawLink | |
|---|---|---|
| Setup flow | Collect and store the right X (Twitter) credentials yourself, then keep the account mapping and request format correct. | ClawLink keeps the setup in one hosted flow so non-technical users can link X (Twitter) without custom integration screens. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for X (Twitter). | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right X (Twitter) actions to the runtime in a format your agent can reliably use. | 84 tools for X (Twitter) are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes X (Twitter) to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Hermes Agent users instead. You install the plugin once, connect X (Twitter) in the browser, and the 84 tools above work from chat. There is no SDK and no config file, and the X (Twitter) key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
Hermes paired but still can't use X (Twitter)
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
Connection succeeds but no tools appear
Reconnect X (Twitter) from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling X (Twitter) tools
X (Twitter) tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every X (Twitter) call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
X (Twitter) returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
The setup form accepts credentials but calls still fail
Re-enter the credentials carefully and verify the account-level permissions for X (Twitter). Basic and token-based integrations tend to fail on formatting mistakes or limited account roles.
FAQ
Is there a Hermes Agent X (Twitter) integration?
Yes. ClawLink is the fastest way to connect Hermes to X (Twitter): link your X (Twitter) account once in the browser and Hermes Agent can call the X (Twitter) API through 84 ready-made tools — no custom code or token handling.
How do I connect X (Twitter) to Hermes with ClawLink?
Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect X (Twitter) in the dashboard and Hermes can use it from the next message — no config files, and the X (Twitter) key you paste is stored server-side instead of in your environment.
How long does it take to connect X (Twitter) to Hermes Agent?
About two minutes. Sign in, click Connect next to X (Twitter) in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring X (Twitter) up myself?
The alternative to ClawLink is usually manual integration setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want X (Twitter) working from chat.
Hermes paired but still can't use X (Twitter)
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
