X + Hermes Agent
How to connect X to Hermes Agent
Connect X to Hermes Agent through Agent200's MCP server: no separate key, ready-made tools and one API key.
On this page
Overview
This guide connects X to Hermes Agent through Agent200's MCP server. When you finish, Hermes Agent can search, read and act in X with the tools Agent200 provides, whenever a request needs them.
You add one MCP server to Hermes Agent with your Agent200 API key. X is reached with that key, so there is no separate X key to manage.
- Connector
- X
- Works with
- Hermes Agent ยท Agent app, through MCP
- Authentication
- Your Agent200 API key
- You need
- An Agent200 API key
- Tools
- 4 tools
- MCP server
https://api.agent200.com/mcp/
Before you start
- An Agent200 API key. Create one on the API keys page of the dashboard.
- X enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- Hermes Agent, with custom MCP servers allowed. Hermes Agent is open source and self-hosted: anyone running it can add MCP servers in its config file.
Connect X to Hermes Agent
-
1
Step 1: Create your Agent200 API key
Open the API keys page in the Agent200 dashboard and choose Create an API key. You add it to Hermes Agent in the next step, as "Authorization: Bearer <your key>". One key covers X and every other connector enabled for your project. Keep it out of chats and source control.
-
2
Step 2: Store your key in ~/.hermes/.env
Keep the key out of
config.yaml: Hermes reads it from~/.hermes/.env.~/.hermes/.envMCP: Hermes Agent key in ~/.hermes/.env AGENT200_API_KEY=your-agent200-api-key -
3
Step 3: Add the server to ~/.hermes/config.yaml
Add an entry under
mcp_serverswith the URL and the Authorization header. Do not settransport: sse: Agent200 serves streamable HTTP.~/.hermes/config.yamlMCP: Hermes Agent config.yaml entry mcp_servers: agent200: url: "https://api.agent200.com/mcp/" headers: Authorization: "Bearer ${AGENT200_API_KEY}" -
4
Step 4: Reload and test
In a running session, run
/reload-mcp, or restart Hermes. Then check what the server returned from a terminal.TerminalMCP: Hermes Agent reload and test # In a running Hermes session: /reload-mcp hermes mcp test agent200 hermes mcp list
Test your connection
Run one request to check everything is wired up.
Ask
What are people posting about our launch today
What should come back
- An answer built from X results.
-
Behind the scenes, Hermes Agent calls an Agent200 tool for X, such as
x_search_posts.
If Hermes Agent says it has no X tool, check that X is enabled for your project in the dashboard.
Get your API key
Create a key in the Agent200 dashboard. It reaches X and every other connector enabled for your project.
Instructions for AI agents
Using a coding agent? Paste this brief into it, or give it the address of this page. It lists what to do, in order, to connect X to Hermes Agent.
Goal: connect X to Hermes Agent with Agent200, through its MCP server. Guide: https://www.agent200.com/tools/x/framework/hermes-agent/ 1. The user needs an Agent200 API key. If they have none, send them to https://agent200.com/platform/apikeys/ to choose "Create an API key". They paste it into Hermes Agent's settings themselves: never ask for it in chat and never write it into files you share. 2. Make sure X is enabled for their project in the Agent200 dashboard (Connectors), with the tools the task needs. 3. Add Agent200's MCP server to Hermes Agent: URL https://api.agent200.com/mcp/, transport streamable HTTP, header "Authorization: Bearer <the user's Agent200 API key>". Follow the setup steps on the guide page for Hermes Agent's exact menus or commands. 4. Check it works with this request: "What are people posting about our launch today" What should come back: - An answer built from X results. - Behind the scenes, Hermes Agent calls an Agent200 tool for X, such as `x_search_posts`. 5. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /tools/x/framework/hermes-agent.md
X tools Hermes Agent can call
-
Search recent posts
Readx_search_postsFind posts from the last seven days that match a query.
-
Get a post
Readx_get_postRead a post with its author and engagement counts.
-
Get a user
Readx_get_userLook up an account by username: name, bio and follower counts.
-
List a user's posts
Readx_list_user_postsRead the most recent posts from an account.
No tool matches that search.
How it works
-
01
You ask Hermes Agent
In your own words, for something in X.
-
02
Hermes Agent picks a tool
It sees the X tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
It reaches X with your Agent200 API key, within the endpoints your project allows.
-
04
Hermes Agent answers
It gets the result back from the MCP server and uses it in its reply or its next step.
Permissions at every level. Your project settings decide which services and endpoints the agent may use.
Troubleshooting
The connection fails and names a missing variable
Add AGENT200_API_KEY to ~/.hermes/.env and run /reload-mcp.
The server answers 401 or 403
Check the key in ~/.hermes/.env and that the header reads exactly Bearer ${AGENT200_API_KEY}.
The initialize request fails with 400 or 405
That points to an SSE setting. Remove any transport: sse line from the entry and check the URL is exactly the Agent200 MCP server address.
The X tools do not appear
Run hermes mcp test agent200, check the entry is not disabled and no tools filter hides them, then /reload-mcp. Hermes names them mcp_agent200_....
A tool call is refused or returns less than expected
Agent200 runs only what your project allows. Check that X and the tools you need are enabled in the dashboard's Connectors settings.
The API key was pasted into a chat or committed
Create a new key on the API keys page, replace it in Hermes Agent's MCP settings, and stop using the old one. Paste the key only into Hermes Agent's settings, never into a chat.
