Add FlightQueue to Websites - #26
Open
jackculpan wants to merge 1 commit into
Open
jackculpan wants to merge 1 commit into
jackculpan wants to merge 1 commit into
Conversation
Member
|
Similarly here, would be good to see the developer-oriented WebMCP story. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds FlightQueue to the Websites section.
FlightQueue registers four tools on
navigator.modelContextfrom its airport pages:get_airport_security_wait— live checkpoint waits, by terminal and checkpointget_airport_crowd_reports— recent traveller-submitted waitsget_faa_delays— current US ground stops and delay programmessubmit_airport_wait_report— files a wait the traveller has just observedEach tool calls a same-origin endpoint with the visitor's own cookies, so an in-browser agent inherits exactly the entitlements of the signed-in user rather than needing a separate key.
The tool list is also declared statically at /.well-known/webmcp.json, so it is readable without a browser that has the API. The manifest and the page registration are generated from one source, so they cannot drift.