Book flights from Hermes Agent
Connect Nous Research's Hermes Agent to FlightSweeper's bounded remote MCP server while keeping traveler identity and payment on FlightSweeper.
Bearer-token connection available
Authorize with OAuth when supported, or create a revocable 30-day personal token and copy the generated client configuration. Two personal tokens may overlap during rotation.
Hermes users who want persistent, tool-driven flight planning with an explicit transaction boundary.
Use FlightSweeper to compare fresh round-trip options for my saved goal. Respect my flexibility rules, ask before creating a watch, and return the hosted checkout for the flight I choose.
Setup flow
Every client uses the same Streamable HTTP endpoint and the same ten public tools. Checkout links return directly; persistent watch creation keeps hosted approval.
Personal-token secrets are shown once, expire after 30 days, and can be revoked from Account → Integrations. OAuth access tokens expire after 10 minutes and refresh tokens rotate.
Create a FlightSweeper account, then open Account → Integrations.
Create a Hermes Agent token and store it as FLIGHTSWEEPER_AGENT_TOKEN in Hermes' environment file.
Copy the generated remote-server YAML into ~/.hermes/config.yaml.
Confirm Hermes exposes only FlightSweeper's exact ten public tools.
Open watch-approval and checkout URLs on FlightSweeper; never give Hermes passenger or card data.
Tool permissions
Every client should keep the same transaction boundary: search can happen in the agent, but booking happens after the traveler confirms a hosted checkout page.