Connect an Agent
Hermes Agent
Add MoraWP to Nous Research's Hermes Agent as a remote MCP server with OAuth.
Hermes Agent from Nous Research reads its MCP servers from
~/.hermes/config.yaml. It handles MoraWP's OAuth sign-in and registration
itself, so you never paste a key.
Add MoraWP
- Close any running Hermes session. Editing the file while a session runs reloads MCP with a timeout too short for a browser sign-in.
- Add MoraWP under
mcp_serversin~/.hermes/config.yaml, keeping any servers already there:YAMLmcp_servers: morawp: url: "https://mcp.morawp.com/mcp" auth: oauth - Sign in:Terminal
hermes mcp login morawp
Hermes prints an address and opens your browser. Sign in and approve access in MoraWP. On a computer without a browser, usehermes mcp login morawp --flow device. - Check the connection:Terminal
hermes mcp test morawp
Expected result: Hermes reports MoraWP's tools.
In a session that was already open, run /reload-mcp to pick up MoraWP.
Approve and check access
First connect a WordPress website in MoraWP. When sign-in opens, review the Workspace, websites, and Ability access before approving.
Then ask Hermes:
Use MoraWP to list the websites this connection can access.
Do not create, edit, delete, or publish anything.
Check: the intended website appears. Then read one page to check WordPress access.
If it does not work
| What you see | Next step |
|---|---|
| Sign-in times out | Close the session, then run hermes mcp login morawp from a terminal. |
| Sign-in keeps failing after a reinstall | Run hermes mcp remove morawp, delete its file under ~/.hermes/mcp-tokens/, then add it again. |
| No MoraWP tools in a session | Run /reload-mcp, then see Missing Abilities. |
To stop access, disconnect the Agent in MoraWP and remove the
morawp entry from config.yaml. Removing it locally alone does not revoke MoraWP access.
Official references
Hermes Agent MCP documentation
Vendor instructions reviewed November 4, 2026. Client interfaces and account policies may change.