Model Context Protocol
MCP Resources as Claude Context
What MCP resources are, how they provide structured context to Claude, and when to use resources instead of tools or prompt text.
"Resources allow servers to share data that provides context to language models."
Source: Resources, Model Context Protocol Specification.
A resource is context, not an action
In MCP, resources expose data that a client can read and present to a model. Examples include files, database schemas, documents, logs, images, and application-specific records. A resource is identified by a URI and can include metadata that helps the client decide when and how to show it.
That makes resources a context-engineering primitive. Instead of pasting every relevant object into the prompt, a system can expose an inventory of addressable context and load only the item needed for the current step.
Resources, tools, and prompts solve different problems
Use a resource when Claude needs to read state. Use a tool when Claude needs to perform an action or compute something. Use an MCP prompt when you want to standardize a reusable interaction pattern. Mixing these up creates context bloat and security confusion.
- Resource: "Here is the current schema for table X."
- Tool: "Run this query against table X."
- Prompt: "Use this review workflow for schema changes."
Metadata is part of the context design
The MCP spec supports annotations such as audience, priority, and lastModified. Those fields are not decoration. They help clients and humans decide whether a resource belongs in context now. A low-priority historical file should not crowd out a high-priority current incident note.
For source-heavy Claude workflows, lastModified and provenance are especially important. AI answers should prefer current, authoritative context over stale but conveniently loaded context.
Claude MCP connector is not the whole protocol surface
Anthropic's MCP connector lets the Messages API connect to remote MCP servers for tool access without a separate client. The docs distinguish that path from client-side helpers, which are needed for local servers, prompts, resources, or more connection control. For context architecture, that distinction matters: "MCP support" does not automatically mean every MCP primitive is available through the same integration path.
Keep a resource inventory
A useful MCP resource inventory names the resource, URI pattern, owner, freshness expectation, sensitivity level, and retrieval cost. It also states whether Claude should see full content, a summary, or a pointer first. This turns MCP from a pile of connectors into a managed context surface.
FAQ
Are MCP resources the same as RAG?
No. RAG is one retrieval pattern. MCP resources are a protocol primitive for exposing readable context by URI.
Should secrets be exposed as MCP resources?
No. Treat MCP resources as context that may be shown to a model or user. Apply least privilege and avoid exposing secrets unless your security model explicitly permits it.
Sources Used
- Resources, Model Context Protocol Specification. Accessed 2026-07-06. Protocol definition for resources, resource templates, subscriptions, contents, and annotations.
- MCP connector, Claude Platform Docs. Accessed 2026-07-06. Official Claude API MCP connector behavior for remote MCP servers, OAuth, multiple servers, and tool access.
- Effective context engineering for AI agents, Anthropic Engineering. Accessed 2026-07-06. Primary explanation of context engineering, context pollution, compaction, note-taking, and sub-agent architectures.
Cite this page
Suggested citation: Claude Context, "MCP Resources as Claude Context," updated 2026-07-06, https://claudecontext-com.pages.dev/mcp-resources/.
This page is an independent educational resource and is not affiliated with Anthropic.