Skip to main content
Each app/resources/**/config.terse file defines one MCP resource surface. A resource folder can represent either:
  • a concrete resource (uri), or
  • a resource template (uri_template).

​
Full schema

app/resources/release-notes/config.terse
uri: memory://release-notes/latest
name: release-notes
title: Latest release notes
description: Markdown release notes for the current release.
mime_type: text/markdown
file: ./content/release-notes.md

​
Field reference

​
uri
string
Concrete resource URI. Use for fixed resources read via resources/read.
Exactly one of uri or uri_template must be defined.
​
uri_template
string
URI template (RFC 6570 style) for parameterized resources.
Exactly one of uri or uri_template must be defined.
​
name
string
Optional display name.Default: resource folder name (directory containing config.terse).
​
title
string
Optional human-friendly title.
​
description
string
Optional description surfaced in MCP resource metadata.
​
mime_type
string
Optional MIME type override for returned content.
​
text
string
Inline concrete content for uri resources.
For concrete resources, define one of text or file.
​
file
string
File path for concrete uri resources.Paths are resolved relative to the config.terse directory when not absolute.
For concrete resources, define one of text or file.
​
text_template
string
Inline template content for uri_template resources.Supports interpolation placeholders like {{ id }}.
For template resources, define one of text_template or file_template.
​
file_template
string
File path template for uri_template resources.Supports interpolation placeholders like ./docs/{{ id }}.md.Paths are resolved relative to the config.terse directory when not absolute.
For template resources, define one of text_template or file_template.
​
arguments
object
Optional map of URI template argument metadata keyed by argument name.

​
Validity rules

  • One of uri or uri_template is required.
  • uri + uri_template together is invalid.
  • For uri resources: one of text or file is required.
  • For uri_template resources: one of text_template or file_template is required.
  • Resource URIs must be unique across concrete resources.
  • URI templates must be unique across template resources.

​
Runtime mapping

  • Concrete resources appear in MCP resources/list.
  • Template resources appear in MCP resources/templates/list.
  • Both are resolved via MCP resources/read.
  • Template arguments.completion values are used by MCP completion/complete (ref/resource).
  • Resource updates on model reload emit MCP notifications (resources/list_changed, resources/updated).

​
JSON Schema

Editor validation: schema/resource.terse.schema.json. Associate with **/resources/**/config.terse. See Configuration schemas.