Connect SnitchFeed to Hermes Agent (MCP setup)
Add the SnitchFeed MCP server to Hermes Agent with one command, sign in once, then let your agent work with mentions and listeners.
Last updated
Connect SnitchFeed to Hermes Agent and your agent can read your mentions, listeners and usage, and act on them. Hermes talks to SnitchFeed through the SnitchFeed MCP server.
Before you start
- A SnitchFeed account.
- Hermes Agent installed, with MCP support turned on.
Add SnitchFeed to Hermes
Run this command:
hermes mcp add --url https://api.snitchfeed.com/mcp --auth oauth snitchfeedThis writes the server to ~/.hermes/config.yaml.
Your browser opens a SnitchFeed sign-in page. Sign in and grant access. Hermes keeps the sign-in in ~/.hermes/mcp-tokens/ and refreshes it on its own.
Test the connection:
hermes mcp test snitchfeedIn a running session, type /reload-mcp so Hermes picks up the new tools.
Prefer editing the config yourself? Add this to ~/.hermes/config.yaml, then run /reload-mcp:
mcp_servers:
snitchfeed:
url: "https://api.snitchfeed.com/mcp"
auth: oauthCheck that it works
Ask Hermes: "How many keywords am I using in SnitchFeed?" It should answer with your keyword, listener and credit usage.
In SnitchFeed, Integrations → MCP lists Hermes under Connected agents. Click Disconnect there to remove its access.
If something goes wrong
| Problem | Fix |
|---|---|
| "invalid_client" when connecting | Run hermes mcp remove snitchfeed, delete the SnitchFeed files in ~/.hermes/mcp-tokens/, then add it again. |
| Sign-in fails on a remote server | The sign-in returns to the machine running Hermes. Run the first sign-in where your browser can reach it. |
| Hermes asks you to sign in again | Sign-ins last 30 days. Remove the server and add it again. |
Next steps
- MCP use cases: prompts to try first
- MCP tools reference: every tool and what it costs