Hermes Agent remote MCP setup

First prepare a Phasoric vault on Premium or higher. Only explicitly authorized internet-reachable mappings are exposed; local-only vaults remain outside hosted MCP.

Configure the owning profile

Hermes documents URL-based Streamable HTTP servers and OAuth. Merge this into the owning profile's existing configuration without replacing other entries:

mcp_servers:
  phasoric:
    url: https://phasoric.com/api/mcp
    auth: oauth
    trust: untrusted

Run hermes mcp login phasoric from that profile and host. Review Phasoric's requested scopes and start with read access. The untrusted setting asks Hermes to require approval for tools without a read-only annotation; Phasoric's authorization checks still apply independently.

The official MCP configuration reference, checked September 17, 2026, documents this transport, OAuth discovery and dynamic registration fallback. This configuration is a protocol-based inference, not a completed Hermes-to-Phasoric interoperability test.

Check the useful result

Ask: “List my Phasoric vaults, then read the project brief and cite its path. Do not change anything.” Use the returned mapping handle. Confirm the actual read; tool discovery alone does not prove access.

Remote hosts need a working authorization callback. Consult the vendor's remote-host OAuth guide for that setup.

To retain a reviewed outcome, follow Phasoric's write-preview checks. Conversations are not silently imported, and purchased hosted-intelligence credits do not unlock MCP.