Machine-readable design data

Everything on the human-readable pages is also published for agents and programs. All 738 entries are available through a self-describing JSON API, production-ready Markdown design specs and rights-conscious image prompts. MCP remains an optional read-only adapter. Every result carries its source URL.

Start with HTTP

Service index: GET /api describes every endpoint, template, count and usage boundary.
JSON API: GET /api/styles?q=…&family=…&kind=… · GET /api/styles/{id}
Supporting terms: GET /api/terms?q=… returns methods, patterns and theories kept searchable but excluded from the independent-style count. The admission rules are at GET /standards.
Design spec: GET /styles/{id}/design.md returns the complete design document for one entry, in Markdown.
Image prompt: GET /styles/{id}/prompt.txt returns plain text, ready to pass to an image model.
AI index: GET /llms.txt · GET /sitemap.xml

Optional MCP server

Add it: claude mcp add --transport http design-styles https://indexstyle.org/mcp
Transport: Streamable HTTP. Read-only, no authentication.

Tools

search_styles: Search across names, cues, eras and families; also filterable by intent (tension, calm, celebration and so on).
get_style: One entry in full: essence, visual cues, composition recipe, cautions, related entries, source URLs and the image-prompt URL.
compare_styles: Place two or more styles side by side and return what they share and where they diverge.
compose_styles: Combine several styles and return the conflicts to resolve and the conditions that make the mix hold.
find_related_styles: Follow lineage and influence to neighbouring entries.

Prompts

image-prompt: An image-generation prompt for the style, written only from legally clean description, with no artist or brand names.
apply-style: A guide to applying the style in real production work.

Assumptions when you use it

Open data: Original IndexStyle text and structured data are CC BY 4.0. Credit IndexStyle and keep the source entry URL; reference images and quoted works are excluded.
Sources: Every result carries the URL of its page of record. When a style informs generated work, keep the trail back to that source intact.
Images: The API and MCP return text and source URLs. The reference images themselves live with their publishers; for rights, see Citations and reference images.
Growth: Entries are added continuously. Don’t hard-code the count.

Back to the dictionary