Fensory connection guide
Connect Hermes Agent to Fensory
Hermes connects to Fensory as an OAuth-authenticated remote HTTP MCP server. Add the endpoint with one CLI command, complete the browser authorization and test the saved connection before using it in a session.
Hermes stores the OAuth token separately from its main config and refreshes it automatically. Fensory is not available to US persons.
What you need
A current Hermes Agent installation and an eligible Fensory account.
Connect Hermes
Use the remote Fensory server and complete OAuth with the account you want the assistant to reach.
hermes mcp add --url https://mcp.fensory.com/mcp --auth oauth fensory
hermes mcp test fensory- 01
Add the remote server
Run the command above. Hermes writes a fensory entry under mcp_servers with the URL and OAuth authentication mode.
- 02
Complete browser authorization
On first connection Hermes discovers the OAuth endpoints, opens a browser and waits for you to authorize the Fensory account.
- 03
Test the connection
Run hermes mcp test fensory. If the session was already open, use /reload-mcp before asking Hermes to list the available tools.
- 04
Start with a read-only prompt
Ask for account status, limits or available markets before enabling agentic trading. This verifies the account and instrument naming without creating an order.
Connect an agent
Server URL
https://mcp.fensory.com/mcpOne endpoint for every client. Sign in to Fensory once for this connection.
- 1
Run this in your terminal.
hermes mcp add --url https://mcp.fensory.com/mcp --auth oauth fensory - 2
Complete browser authorization, then run hermes mcp test fensory.
- 3
Try a read-only question.
“What can you do on Fensory?”
Example prompts for Hermes
Use these examples to check the connection, account and instrument before any order is submitted. Adapt the amount and market to your own account controls.
Show my account status, enabled markets and current trading limits. Do not place or cancel any order.
Account checkShow my open positions, open orders and current exposure. Do not change anything.
Risk checkInspect a supported perpetual future and draft a small limit order with every parameter shown. Do not submit it.
Order previewSet account limits before the first order
Fensory enforces three controls on the account: a kill-switch, a market allow-list and a per-order cap.
See the controls
What to know about Hermes
OAuth tokens live outside config.yaml
Hermes stores them under its mcp-tokens directory rather than writing the token into the server configuration. Refresh is automatic until re-authorization is required.
A remote host may need the paste-back flow
If Hermes runs on a different machine from the browser, use the redirect paste-back, device-code or SSH forwarding flow documented by Hermes rather than exposing a token in config.
Tool filters still apply
Hermes can include or exclude tools per server. A connection that succeeds can still hide a tool because of the saved filter, so check the server entry if a known tool is missing.
Questions people ask
- Do I put a Fensory token in config.yaml?
- No. Set auth to OAuth. Hermes completes the browser flow and stores tokens in its separate token directory.
- How do I check whether Hermes can reach Fensory?
- Run hermes mcp test fensory, then ask Hermes to list the tools available from the Fensory server. Reload MCP if you added the entry during an existing session.
- Can I limit the tools Hermes sees?
- Yes. Hermes supports include and exclude filters on an MCP server. Client-side filtering is additional to the limits enforced by the Fensory account.
- Does a successful login prove trading works?
- No. It proves OAuth completed. Test a read call, then confirm agentic trading and the account controls in Fensory before attempting an order.
- Can the Hermes connection withdraw funds?
- No. On the current MCP path, the Hyperliquid agent key can sign trades and cannot withdraw, transfer or bridge funds.