# Resources (https://docs.neuralisapp.com/package-system/resources)

A resource is an MCP resource entry — `uri`, `name`, and optional `id`,
`description` and `mimeType` — that the platform's MCP server advertises to
external protocol clients alongside the package's tools. Resources are declared
inline in the manifest:

```json
"resources": [
  {
    "uri": "acme://release-checklist",
    "name": "Release checklist",
    "description": "The steps every release goes through, in order.",
    "mimeType": "text/plain"
  }
]
```

- A client lists them with `resources/list` and reads one with
  `resources/read`. The read returns the entry's own `description` as its text
  content: a resource is static metadata the package ships, not a live file the
  platform fetches.
- A resource has no feature gate of its own. It is visible to a caller who can
  see the package — enabled, in scope, and past the package's
  [access feature](https://docs.neuralisapp.com/package-system/features.md#base-access-feature--gating-a-whole-package)
  when one is declared.
- `runtime.hosted.resources` (`all`, `selected` by `uri`, or `none`; see the
  [manifest](https://docs.neuralisapp.com/package-system/manifest.md)) decides whether they are hosted.
- Two packages declaring the same `uri` are reported as a collision, like tool
  names.

Content an agent should read inside Neuralis belongs in [docs](https://docs.neuralisapp.com/package-system/docs.md)
or a [skill](https://docs.neuralisapp.com/package-system/skills.md) reference instead; the MCP Apps `ui://`
resources that render as chat cards are a separate path
([app surfaces](https://docs.neuralisapp.com/package-system/app-surfaces.md)).
