MCP resources are a primitive in the Model Context Protocol through which a server exposes readable data — files, database records, API responses — that a client can fetch and feed into a model's context.
Resources are MCP's answer to how a model sees data outside its training set. Each resource is identified by a URI, carries a MIME type, and can be either static (a fixed file) or dynamic (a templated URI that resolves based on parameters, like a specific ticket or a date range). A server lists its available resources, and the host decides which to actually pull into context, either automatically or by letting the user pick.
This is deliberately separate from tools: tools cause side effects such as sending an email or creating a record, while resources are meant to be read-only and safe to fetch repeatedly without changing state. That separation lets hosts apply looser trust rules to resource reads than to tool-call side effects, and lets servers cache resource content more aggressively since it isn't expected to be mutated by the read itself.
Servers can also push resource-update notifications so a host knows when previously-fetched content is stale, useful for things like a live log file or a frequently-changing dashboard the model is expected to reason over with current data.
A Neotask document-management skill exposes the tenant's knowledge base articles as MCP resources, so an agent answering a support question can pull the exact current article text into context rather than relying on a stale copy baked into a prompt.
$0/mo
Download without a card and start for free.
$50/mo
The full personal agent platform for one person.
$100/mo
One company workspace with room to add your team.
$200/mo
Multiple workspaces and capacity for larger teams.
Explore: Integrations · Skills · Solutions · Use cases · Examples · Comparisons · Templates · Blog · Docs