MCP Resources

What this is

Documentation pages and reference materials that the ComStack MCP server exposes as MCP resources. AI assistants can read these without calling a tool — useful for orienting on templates, workflows, error codes, and Lighthouse requirements at the start of a session.

How it works

Resources are served via resources/read and resources/list. A resource template covers arbitrary docs: transformento://docs/{slug} resolves any live page by its kebab-case slug. Curated front-door resources are cached in-process for 60 seconds per slug.

Any live doc in the ComStack docs project can promote itself to a named MCP resource without a server redeploy by adding an mcp_resource block to its metadata — the server picks it up within one cache cycle. Hardcoded aliases take precedence on URI collision.

When to use it

Read the curated resources at the start of a session to give the AI assistant context on the platform’s workflow, metadata schema, and common error patterns before composing or editing pages.

Parameters / fields / inputs

Curated resources

URI	Purpose	Audience	Priority
`transformento://guide`	Full agent workflow — template selection, translations, URL patterns, publish flow.	assistant	1.0
`transformento://schema`	Every metadata field — type, required/optional, examples.	assistant	0.9
`transformento://lighthouse`	Rules for a 100/100 Lighthouse score.	assistant	0.8
`transformento://publishing-guide`	End-to-end publishing workflow.	assistant + user	0.9
`transformento://faq`	Common errors, symptoms, recovery actions.	assistant + user	0.7
`transformento://errors`	Error reference and recovery steps.	assistant	0.7
`transformento://cookbook`	Worked examples — property listings, translations, etc.	assistant + user	0.5
`transformento://icons`	Material Symbols (Rounded) icon catalogue for sidebar groups.	assistant	0.5

Resource template

transformento://docs/{slug} resolves any live page from the ComStack docs site. Replace {slug} with the kebab-case page slug, using / for nested paths (e.g. transformento://docs/guides/publishing).

Promoting a page to an MCP resource

Add an mcp_resource block to a page’s metadata:

{
  "mcp_resource": {
    "uri": "transformento://my-guide",
    "audience": ["user", "assistant"],
    "priority": 0.6
  }
}

The server picks it up within 60 seconds. Hardcoded aliases (guide, schema, lighthouse, publishing-guide, faq, cookbook, errors) take precedence on URI collision.

Annotations

Each resource carries annotations: { audience, priority } per the MCP spec. audience: "assistant" resources are intended as AI context; audience: "user" resources are also human-readable.

Example

Reading the agent guide at the start of a session:

{
  "method": "resources/read",
  "params": { "uri": "transformento://guide" }
}

This returns the full agent workflow guide as structured text the AI assistant can use to orient itself before any tool calls — covering page lifecycle, template selection, translation modes, and the publish flow.

Common errors

Error	Cause	Fix
Resource not found	Slug doesn’t match any live page	Verify the slug with `search-docs` or `get-page-content`
Stale content	Alias cache hasn’t refreshed	Wait up to 60 seconds after publishing

MCP Server overview — server setup and transport
Install — connect an AI assistant
Tools — available tools
Examples — workflows using resources and tools together