Resources (MCP Resources)

Resources are the "nouns" of the MCP ecosystem. They represent raw data or content that an AI agent can read to gain more context about a query.

Resources vs. Tools

While Tools are actions that perform work, Resources are generally static or periodically updated data objects.

Examples of Resources:

• Documentation: A README.md file from a repository.
• Audit Logs: A CSV file containing recent system events.
• User Profile: A JSON object describing a user's preferences.

Resources are accessed via a unique URI (Uniform Resource Identifier) provided by the MCP server.

Questions & Answers

What are "MCP Resources," and how do they function?

Resources are the "nouns" of the MCP ecosystem. They represent raw data or static content—such as files, logs, or database records—that an AI agent can read to gain context. They are typically accessed via a unique URI.

What is the key difference between an "MCP Resource" and an "MCP Tool"?

While tools represent actions that perform work (e.g., sending an email), resources represent static or periodically updated data objects (e.g., a README file) that provides context without modifying the system state.

Name three typical examples of resources found in an MCP server.

Common examples include project documentation (like README files), system audit logs (in CSV or plain text), and JSON-formatted user profile data describing preferences or settings.