Resources

The previous chapter ended with the ticketing server's create_ticket returning a link, ticket://INC-4131, instead of the ticket itself. The host now holds an address. It can read the record, show it to the user, attach it to the model's context, watch it for changes, or ignore it. The model does not decide which. That division of labour is what MCP resources are for: addressable content that the application chooses to bring into a conversation, as opposed to actions the model chooses to take.