MCP Resources
One of the three core capability types in the Model Context Protocol (MCP), representing static, read-only contextual content accessible directly via a URI. Resources do not trigger any logic execution and are used to supply background knowledge to AI models.
Timeline (last 90 days)
Even though dynamic resources can be dynamically accessed and a full resource list can be enumerated, decision-making authority remains at the application layer rather than being delegated to the LLM
Each MCP resource has a unique resource identifier (URI); for example, a refund policy can be represented as policy://refund/2026
The Resource workflow is application-driven: the application does not first go through the LLM but instead retrieves context first and then passes both the question and context to the model
The Resource mode is faster than the Tool mode because it eliminates the round-trip step of having the LLM first make a tool selection decision
The core of a tool is execute, while the core of a resource is read
The URI of a dynamic resource contains curly-brace placeholders—for example, customer://profile/{customer_id}—which are replaced with real values at request time
Placing document resources on an MCP server rather than locally ensures that all accessors receive the latest version and supports centralized updates
The core logic for mode selection is: choose Craft when requirements are clear and steps are simple, choose Plan for complex multi-step tasks, and choose Ask for read-only analysis and consulting needs.
All Facts (8)
Even though dynamic resources can be dynamically accessed and a full resource list can be enumerated, decision-making authority remains at the application layer rather than being delegated to the LLM
50%UnverifiedEach MCP resource has a unique resource identifier (URI); for example, a refund policy can be represented as policy://refund/2026
50%UnverifiedThe Resource workflow is application-driven: the application does not first go through the LLM but instead retrieves context first and then passes both the question and context to the model
50%UnverifiedThe Resource mode is faster than the Tool mode because it eliminates the round-trip step of having the LLM first make a tool selection decision
50%UnverifiedThe core of a tool is execute, while the core of a resource is read
50%UnverifiedThe URI of a dynamic resource contains curly-brace placeholders—for example, customer://profile/{customer_id}—which are replaced with real values at request time
50%UnverifiedPlacing document resources on an MCP server rather than locally ensures that all accessors receive the latest version and supports centralized updates
50%UnverifiedThe core logic for mode selection is: choose Craft when requirements are clear and steps are simple, choose Plan for complex multi-step tasks, and choose Ask for read-only analysis and consulting needs.
50%