Skip to content
AdminKit

Resource (MCP)

What is Resource (MCP)?

A resource, in the Model Context Protocol, is a piece of data -- a file, a database record, an API response -- a server exposes to a client by URI, distinct from a tool, which performs an action instead of returning data. AdminKit's guide to securing an MCP server covers why resources need the same scoping review as tools.

By AdminKit team, Netbase JSC · Updated

A resource in the Model Context Protocol — the protocol Anthropic introduced to standardize how applications connect context and tools to an LLM — is a piece of data or content — a file, a database record, an API response — that an MCP server exposes to a client by URI, for the client to read and feed into a model’s context window, as distinct from a tool, which performs an action rather than returning data for reference. A client typically lists a server’s available resources, then reads a specific one by its URI when it’s relevant to the current request, and a server can also notify a subscribed client when a resource’s contents change. Each resource is identified by a unique URI — common schemes include https://, file:// and git:// — and the specification requires any custom URI scheme to follow RFC 3986, the generic URI syntax standard. Because resources often carry the same files, records or internal API responses a tool call would also expose, a server’s resource list deserves the same deliberate scoping before deployment as its tool list does, not an assumption that only tools need reviewing.

Resource (MCP) is part of AdminKit’s AI agents & MCP cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

What distinguishes an MCP resource from a tool?

A resource returns data for a client to read by URI, while a tool performs an action instead of just returning data for reference.

How does a client typically use a server's resources?

It lists the server's available resources, then reads a specific one by its URI when relevant, and can subscribe to be notified when that resource's contents change.

Why do resources need the same scoping review as tools?

Resources often carry the same files, database records or internal API responses a tool call would also expose, so limiting review to tools alone misses that exposure.