Configure OfflineCreator MCP in Hermes

Add the OAuth server to Hermes YAML

Edit `~/.hermes/config.yaml` and add OfflineCreator under the top-level `mcp_servers` mapping. Use the public Streamable HTTP endpoint and set `auth: oauth`; Hermes' current documentation requires that field to enable its OAuth 2.1 flow for a URL-based server.

OfflineCreator's current package README gives remote clients a generic URL-only example, while Hermes' client schema requires `auth: oauth` to enable OAuth for a URL-based server. This draft therefore adds the Hermes-specific authentication field and does not add a fixed Authorization header or an API key.

Configuration file

~/.hermes/config.yamlHermes reads MCP entries from the top-level `mcp_servers` mapping.

Recommended YAML

mcp_servers: offlinecreator: url: "https://mcp.offlinecreatorstudio.com/mcp" auth: oauthThe URL comes from OfflineCreator's live metadata and package; `auth: oauth` comes from the current Hermes schema.

Complete browser authentication from a fresh terminal

After saving the entry, run `hermes mcp login offlinecreator` from a fresh terminal. Hermes warns that the automatic reload triggered by editing `config.yaml` uses a short connection window that may expire before an interactive OAuth round trip finishes; the explicit login path allows the browser flow more time.

Hermes documents metadata discovery, dynamic client registration, PKCE, token exchange, and refresh for `auth: oauth` servers. OfflineCreator's live authorization metadata currently advertises dynamic registration, authorization-code and refresh-token grants, and S256 PKCE. These compatible declarations support attempting the flow, but they do not prove that this research pass completed authorization in Hermes.

Login command

hermes mcp login offlinecreatorRun outside the active Hermes chat so browser authorization is not constrained by the config auto-reload window.

Expected boundary

Browser consent followed by a cached OAuth tokenA reachable server or visible tool list alone is not equivalent to a completed OAuth grant.

Reload and verify the discovered tools

Use `/reload-mcp` inside Hermes after configuration changes. The current Hermes MCP documentation says this reconnects configured servers and refreshes the available tool list. A server can also send a `notifications/tools/list_changed` notification, which Hermes handles by fetching the tool list again without a manual reload.

Verify three separate states: the server is configured, browser authorization completed, and OfflineCreator-backed tools are available. Hermes' practical guide recommends checking the MCP banner or status and asking which MCP tools are available. The published OfflineCreator package documents nine tools, but this research pass did not run Hermes and therefore does not claim that all nine appeared under this OAuth grant.

Current first-party Hermes pages also disagree on registered tool naming: the main MCP guide shows `mcp_<server>_<tool>`, while the config reference shows `mcp__<server>__<tool>`. Treat both forms as documentation evidence only; neither is acceptance-verified for OfflineCreator until a dated Hermes run records the actual registry.

Reload command

/reload-mcpReloads MCP servers from config and refreshes the available tool list.

Verification prompt

Tell me which MCP-backed tools are available right now.Use the response as a discovery check, not as proof that a generation or credit-spending call succeeds.

Documentation naming conflict

Main guide: mcp_<server>_<tool>; config reference: mcp__<server>__<tool>Current first-party pages disagree. Do not rely on either form until a dated Hermes acceptance test records the names actually registered.

Continue with the right client task

Return to the MCP client directory for another host, compare client capabilities before moving a configuration, or use the Cline guide when testing another agent client.

Page boundary

This page owns only the OfflineCreator connection path in Hermes. It does not generalize Hermes configuration to other clients, promise compatibility with every Hermes build, or claim that documentation matching equals successful authentication, tool discovery, media generation, or account access.