Connect FlightSweeper to Hermes Agent
Connect Nous Research's Hermes Agent to FlightSweeper's bounded remote MCP server while keeping traveler identity and payment on FlightSweeper.
OAuth recommended · token fallback
Authorize with OAuth when the client environment supports it. Use a revocable 30-day personal token only as an advanced fallback; two 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. Respect my policy, ask before creating a booking intent, and return the hosted approval for the flight I choose.
Setup flow
Every client uses the same Streamable HTTP endpoint and documented public tool set. The primary book_flight action hides the internal intent and approval stages; approval and payment stay hosted.
OAuth access tokens expire after 10 minutes and refresh tokens rotate. If this environment requires the personal-token fallback, the secret is shown once, expires after 30 days, and can be revoked from Account → Integrations.
A personal token is a compatibility path for headless or restricted environments, not the recommended first setup.
Add https://flightsweeper.com/api/agent/mcp as a remote MCP server in ~/.hermes/config.yaml.
Authorize with FlightSweeper OAuth when the Hermes environment supports the browser flow.
Use a revocable personal token only if OAuth cannot run in that environment.
Confirm Hermes exposes only FlightSweeper's documented public tools.
Open booking approval 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.