Docs/Developers
Connect via MCP
Hermes ships a hosted MCP server, so any MCP-capable agent — claude.ai, Claude Code, Cursor, and others — can manage your triggers, connections, drafts, and analytics directly.
There is nothing to install or self-host: every client connects to the same URL.
https://tryhermes.dev/api/mcpAgents connected over MCP can pull Hermes reference pages on demand through
the built-in hermes_docs tool — the same agent-facing docs published at
docs.tryhermes.dev.
claude.ai
In claude.ai, go to Settings → Connectors → Add custom connector and paste the server URL. Claude walks you through an OAuth sign-in: log into your Hermes account and approve — the connection covers your whole account, every organization you belong to.
Claude Code
Add the server, then run /mcp inside Claude Code to complete the OAuth sign-in (same browser sign-in as claude.ai):
claude mcp add --transport http hermes https://tryhermes.dev/api/mcpPrefer a key over the browser flow (e.g. CI)? Create an API key under Settings → API keys in the dashboard and pass it as a header instead:
claude mcp add --transport http hermes https://tryhermes.dev/api/mcp --header "Authorization: Bearer hk_..."Cursor and other clients
Any client that speaks Streamable HTTP and supports custom headers works the same way: point it at the server URL and send your API key as a bearer token. In Cursor, for example, add this to your mcp.json:
{
"mcpServers": {
"hermes": {
"url": "https://tryhermes.dev/api/mcp",
"headers": { "Authorization": "Bearer hk_..." }
}
}
}What the agent can do
The server exposes the full Hermes control plane — the same operations as the dashboard, CLI, and API — as roughly 45 tools:
| Area | Tools |
|---|---|
| Connections | List, create, and delete data sources; inspect schemas; run read-only queries. |
| Triggers | Create, update, preview, run, pause, and delete campaigns. |
| Signals | List and triage signals; kick off and poll discovery runs. |
| Drafts | Review the queue; approve, reject, and bulk-approve drafts. |
| Emails | Sent history with per-email delivery and engagement timelines. |
| Templates | Create, AI-design, publish, and set default email templates. |
| Senders & domains | Manage sender identities, register domains, check DNS verification. |
| Analytics | Org-wide overview and per-campaign funnels. |
| Docs | hermes_docs serves Hermes reference pages to the agent; whoami reflects the current auth context. |
So you can say things like "look at yesterday's signals, turn the best one into a trigger in review mode, and show me the first three drafts" — entirely from your MCP client.
Tokens and security
| Topic | Details |
|---|---|
| Account-level access | An OAuth connection acts as you, across every organization you belong to. With one org everything defaults to it; with several, the agent picks per call. API keys stay pinned to a single org. |
| Revocable | OAuth connections are sessions named "Claude connector" tied to your account. Revoking the session signs the client out immediately; API keys are managed under Settings → API keys. |
| 90-day expiry | OAuth-minted tokens expire after 90 days. When that happens, just reconnect the connector to sign in again. |