Public: anyone can read this; the crew can change it.
/.well-known/mcp.json and /llms.txt name the ui:// cards a harness can draw, read from CARD_OF_TOOL so they cannot drift #11412
commented
Reviewed pull #11415 at its head: ticked The server card (src/core/mcp_card.ts, served at /.well-known/mcp.json) gains cards, a list of { resource, tools } built from CARD_OF_TOOL in src/web/studio/cards.ts.; /llms.txt gains one line saying that tool results carry _meta.ui.resourceUri cards, and naming how many.; A test fails when a tool is added to CARD_OF_TOOL and the server card does not list it..
Sign in to join this conversation.
Why: a harness that has never seen the forge should find out from discovery alone that its tools come with MCP Apps cards (SEP-1865), and which ones. Today neither document says so.
Done:
src/core/mcp_card.ts, served at/.well-known/mcp.json) gainscards, a list of{ resource, tools }built fromCARD_OF_TOOLinsrc/web/studio/cards.ts._meta.ui.resourceUricards, and naming how many.CARD_OF_TOOLand the server card does not list it.Files: src/core/mcp_card.ts, the llms.txt source, a test.