Webex + Hermes Agent
Connect Webex to Hermes Agent
Prepare a grounded team update briefing
Read space messages with Hermes Agent and Agent200. Prepare a team update briefing using the connected user’s own Webex account.
On this page
Overview
Inspect the Agent200 tools Hermes advertises after connection. Use discovered names and input schemas for the space message read, not guesses from catalogue labels.
Start with one identified space message. Preserve returned space, sender, message text and time; report missing data and keep the workflow read-only.
Provider reference: Webex API.
- Connector
- Webex
- Works with
- Hermes Agent · Agent app, through MCP
- Authentication
- Managed OAuth, per end user
- 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.
- Webex enabled for your project. In the dashboard's Connectors settings, with the endpoints and scopes your agent needs.
- An end user with a Webex account. They approve access once, on Webex's own page.
- 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 Webex 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 Webex 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 -
5
Step 5: Connect your Webex account
The first time you ask Hermes Agent for something in Webex, Agent200 returns an authorization link. Open it and approve access on Webex's own page. Agent200 stores the connection and keeps it working; your password never reaches Hermes Agent or Agent200.
Test your connection
Run one request to check everything is wired up.
Ask
Read recent messages from the Webex space I identify. Summarize the decisions and open questions from returned messages, naming the space and source messages. Ask if the space is ambiguous. Do not post or modify anything.
What should come back
- The selected space message is identified.
- Only returned space, sender, message text and time are reported.
- Access gaps and missing context are explicit; no source data is changed.
Check the selected space ID, connected user membership, read permissions and page scope. Report access errors or missing messages without inventing a conversation.
Get your API key
Create a key in the Agent200 dashboard. It reaches Webex 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 Webex to Hermes Agent.
Goal: connect Webex to Hermes Agent with Agent200, through its MCP server. Guide: https://www.agent200.com/connectors/webex/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 Webex 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. The first Webex request returns an authorization link if the user has not connected Webex yet: show it to them and continue once they have approved access on Webex's own page. 5. Check it works with this request: "Read recent messages from the Webex space I identify. Summarize the decisions and open questions from returned messages, naming the space and source messages. Ask if the space is ambiguous. Do not post or modify anything." What should come back: - The selected space message is identified. - Only returned space, sender, message text and time are reported. - Access gaps and missing context are explicit; no source data is changed. 6. If a tool is missing or a call is refused, check the project's Connectors settings in the dashboard and the access the user granted in Webex, then retry.
The whole guide is also available as Markdown, for agents and LLMs: /connectors/webex/framework/hermes-agent.md
Webex tools Hermes Agent can call
-
List spaces
Readwebex_list_spacesFind the spaces available to the connected user.
-
Read a space
Readwebex_get_spaceRetrieve details of one identified space.
-
List messages
Readwebex_list_messagesRead messages in a selected space within an explicit result scope.
-
Read a message
Readwebex_get_messageRetrieve one identified message and its available details.
No tool matches that search.
How it works
-
01
You ask Hermes Agent
In your own words, for something in Webex.
-
02
Hermes Agent picks a tool
It sees the Webex tools on the Agent200 MCP server and calls the one the request needs.
-
03
Agent200 runs the call
With your own Webex connection, within the tools and scopes 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.
Each user's own connection. Connections belong to individual end users. A request for one user never reaches another user's Webex account.
Permissions at every level. Your project settings decide what the agent may request, the end user decides what they authorize, and Webex enforces what its API grants.
Troubleshooting
The source cannot be read
Check the selected space ID, connected user membership, read permissions and page scope. Report access errors or missing messages without inventing a conversation.
FAQ
How do I verify this result?
Compare the named space message and returned space, sender, message text and time with the source. Treat missing information as missing, not as a fact.

