Resources & prompts
Beyond tools, the StyleRef MCP server exposes resources (read-only data addressable by URI) and prompts (reusable interaction templates). This page lists both.
Resources
Resources are cheaper than tools for hosts that support them, and they give agents a browseable surface.
| URI | Returns | MIME |
|---|---|---|
styleref://gallery/{slug} | A public gallery style compiled to the default (prose) spec | text/plain |
styleref://gallery/{slug}/style.md | The same style as a STYLE.md file body | text/markdown |
styleref://schema | The StyleRef style schema — sections and block types | application/json |
Read styleref://schema before authoring a style with create_style — it’s the source of truth for valid block types. See Tools reference.
The gallery resource template lists featured and recent styles (capped at 20), so a host can enumerate what’s available.
Own styles
When you’re connected with an account, your own private styles resolve anywhere a ref is accepted — including get_style, update_style, and publish_style — by their share slug or id. list_my_styles returns the ref to use for each, so you never have to construct one.
styleref:// URIs address the resources above, not styles — a tool’s ref parameter takes a share slug, a /share URL, or your own style’s id. The two are deliberately separate namespaces.
Interactive style cards
Hosts that support MCP Apps / mcp-ui get a rendered style card alongside the text, so a style arrives as a visual card with its palette rather than a wall of prose. Four tools attach one:
| Tool | Card |
|---|---|
get_style | A full style card — palette, essence, attribution |
search_styles | A compact list of the matches |
list_my_styles | A compact list of your library |
check_extraction_status | A card for the extracted draft |
The card is a self-contained HTML document embedded in the tool result under a ui://styleref/… URI with mime type text/html, plus _meta markers (openai/outputTemplate, mcpui.dev/ui-resource) for host discovery.
The plain text always comes first. A host without the Apps extension sees exactly the text result it would have seen anyway, so nothing depends on card support — it’s additive.
Prompts
Prompts emit instruction messages that steer the model to the right tools.
use-style
Generate something while strictly following a chosen style.
| Argument | Notes |
|---|---|
ref | The style to apply. |
request | What to generate (for example “a landing page hero headline”). |
It instructs the agent to call get_style with a fitting format, then produce the request following the returned spec as a hard constraint.
pick-a-style
A guided discovery flow.
| Argument | Notes |
|---|---|
discipline | Creative discipline (for example “poster design”). Optional. |
mood | Desired mood (for example “warm, editorial, calm”). Optional. |
It asks a short question if discipline or mood is missing, calls search_styles, presents the top three candidates, and calls get_style on your choice.
setup-style-md
A coding-agent flow for pinning a project’s style.
| Argument | Notes |
|---|---|
ref | The style to write into the repo. |
It instructs the agent to call get_style_md, write the result to STYLE.md in the project root, and add a reference line to AGENTS.md. See Add STYLE.md to a project.
Next steps
- Tools reference — the tools these prompts drive.
- Authentication & scopes — resolve your own styles.