OMORO Style Library
Search, compare, and blend structured visual aesthetics, palettes, and creative directions.
Should I use this
Quality & Safety
Findings (1)
- LOWTool 'compare_styles' description lacks action verbin compare_styles
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"style-library": {
"url": "https://omoro.io/api/mcp"
}
}
}Remote endpoints
https://omoro.io/api/mcpstreamable-httpWhat it can do
Tool inventory
Tools (16)
🟢get_started
Show the Omoro MCP welcome guide: what is available, what each option does and which tool to use first.
Input Schema
{
"type": "object",
"properties": {}
}🟢list_styles(group, category, limit, offset)
List documented aesthetic styles. Optionally narrow by mood group or category. Returns the short listing: slug, name, url, group, a one-line summary and the five palette hex codes.
Input Schema
{
"type": "object",
"properties": {
"group": {
"type": "string",
"description": "Mood group to filter by.",
"enum": [
"retro",
"dark",
"bold",
"art",
"clean",
"organic",
"digital",
"architecture"
]
},
"category": {
"type": "string",
"enum": [
"traditional",
"design_language"
]
},
"limit": {
"type": "integer",
"minimum": 1,
"maximum": 200,
"default": 50
},
"offset": {
"type": "integer",
"minimum": 0,
"default": 0
}
}
}🟢get_style(slug)
The full record for one style: palette with named swatches, the eight-axis attribute profile, typography pairing, documented period and origin, visual markers, related styles, a canonical hero image, and the page's labelled visual gallery.
Input Schema
{
"type": "object",
"properties": {
"slug": {
"type": "string",
"description": "The style's slug, e.g. \"bauhaus\". Get one from list_styles or search_styles."
}
},
"required": [
"slug"
]
}🟢search_styles(query, limit)
Free-text search across style names and summaries. Use when you know roughly what you are looking for but not the slug. For finding styles by visual character rather than by name, find_styles_by_attributes is the better tool.
Input Schema
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "Words to look for, e.g. \"darkroom film grain\"."
},
"limit": {
"type": "integer",
"minimum": 1,
"maximum": 50,
"default": 10
}
},
"required": [
"query"
]
}🟢find_styles_by_attributes(minimal_maximal, analog_digital, expressive_restrained, warm_cool, futuristic_nostalgic, ...)
Rank styles by how closely they sit to a target visual position. Give only the axes you care about; the rest are ignored rather than assumed. Each axis runs -1 to 1. This answers questions prose cannot, such as which styles are simultaneously minimal, cool, geometric and digital.
Input Schema
{
"type": "object",
"properties": {
"minimal_maximal": {
"type": "number",
"minimum": -1,
"maximum": 1,
"description": "Target position on the minimal_maximal axis, -1 to 1."
},
"analog_digital": {
"type": "number",
"minimum": -1,
"maximum": 1,
"description": "Target position on the analog_digital axis, -1 to 1."
},
"expressive_restrained": {
"type": "number",
"minimum": -1,
"maximum": 1,
"description": "Target position on the expressive_restrained axis, -1 to 1."
},
"warm_cool": {
"type": "number",
"minimum": -1,
"maximum": 1,
"description": "Target position on the warm_cool axis, -1 to 1."
},
"futuristic_nostalgic": {
"type": "number",
"minimum": -1,
"maximum": 1,
"description": "Target position on the futuristic_nostalgic axis, -1 to 1."
},
"structured_chaotic": {
"type": "number",
"minimum": -1,
"maximum": 1,
"description": "Target position on the structured_chaotic axis, -1 to 1."
},
"light_dark": {
"type": "number",
"minimum": -1,
"maximum": 1,
"description": "Target position on the light_dark axis, -1 to 1."
},
"organic_geometric": {
"type": "number",
"minimum": -1,
"maximum": 1,
"description": "Target position on the organic_geometric axis, -1 to 1."
},
"limit": {
"type": "integer",
"minimum": 1,
"maximum": 50,
"default": 10
}
}
}⚪suggest_style_directions(taste_axes, brand_palette, avoid_styles, brand_context)
Return three distinct, Omoro-grounded brand routes for a user. First translate only supported personal taste signals into numeric taste_axes, include the exact known palette and known brand_context, then call this tool. Each route includes an automatically selected style blend, signature visuals, positioning and message framework, and voice guidance. Use Omoro for the page frame only; let each blend's defining features lead its route. Present all three as choices and do not invent missing brand facts or collapse the options into one generic style.
Input Schema
{
"type": "object",
"properties": {
"taste_axes": {
"type": "object",
"description": "Infer only axes supported by the user's known context. Each is -1 to 1. Poles: minimal_maximal (- minimal, + maximal); analog_digital (- analog, + digital); expressive_restrained (- restrained, + expressive); warm_cool (- cool, + warm); futuristic_nostalgic (- futuristic, + nostalgic); structured_chaotic (- structured, + chaotic); light_dark (- dark, + light); organic_geometric (- organic, + geometric).",
"properties": {
"minimal_maximal": {
"type": "number",
"minimum": -1,
"maximum": 1,
"description": "Target position on the minimal_maximal axis, -1 to 1."
},
"analog_digital": {
"type": "number",
"minimum": -1,
"maximum": 1,
"description": "Target position on the analog_digital axis, -1 to 1."
},
"expressive_restrained": {
"type": "number",
"minimum": -1,
"maximum": 1,
"description": "Target position on the expressive_restrained axis, -1 to 1."
},
"warm_cool": {
"type": "number",
"minimum": -1,
"maximum": 1,
"description": "Target position on the warm_cool axis, -1 to 1."
},
"futuristic_nostalgic": {
"type": "number",
"minimum": -1,
"maximum": 1,
"description": "Target position on the futuristic_nostalgic axis, -1 to 1."
},
"structured_chaotic": {
"type": "number",
"minimum": -1,
"maximum": 1,
"description": "Target position on the structured_chaotic axis, -1 to 1."
},
"light_dark": {
"type": "number",
"minimum": -1,
"maximum": 1,
"description": "Target position on the light_dark axis, -1 to 1."
},
"organic_geometric": {
"type": "number",
"minimum": -1,
"maximum": 1,
"description": "Target position on the organic_geometric axis, -1 to 1."
}
}
},
"brand_palette": {
"type": "array",
"description": "Exact brand colors as six-digit hex codes. When supplied, all three directions must stay within these colors.",
"items": {
"type": "string",
"pattern": "^#[0-9A-Fa-f]{6}$"
},
"maxItems": 12
},
"avoid_styles": {
"type": "array",
"description": "Style slugs the user or brand has rejected or already overuses.",
"items": {
"type": "string"
},
"maxItems": 50
},
"brand_context": {
"type": "object",
"description": "Known, user-provided brand facts Muse may use for positioning and messaging. Omit unknown fields; the tool will leave them as open inputs.",
"properties": {
"brand_name": {
"type": "string",
"maxLength": 120
},
"audience": {
"type": "string",
"maxLength": 240
},
"offer": {
"type": "string",
"maxLength": 240
},
"differentiator": {
"type": "string",
"maxLength": 240
},
"desired_perception": {
"type": "string",
"maxLength": 240
},
"audience_need": {
"type": "string",
"maxLength": 240
},
"proof_point": {
"type": "string",
"maxLength": 240
},
"call_to_action": {
"type": "string",
"maxLength": 240
},
"existing_voice": {
"type": "string",
"maxLength": 240
}
}
}
},
"required": [
"taste_axes"
]
}🟡compare_styles(a, b)
Put two styles side by side: their attribute profiles with the gap on each axis, their palettes, and their documented periods. Use it to explain how two visual languages actually differ.
Input Schema
{
"type": "object",
"properties": {
"a": {
"type": "string",
"description": "First style slug."
},
"b": {
"type": "string",
"description": "Second style slug."
}
},
"required": [
"a",
"b"
]
}🟡build_style_guide_output(format, style_slugs, use_case, brand_palette)
Create a separate Omoro-designed style guide, palette/type sheet, or application brief for one style or a user-selected blend. Its visual system is grounded in each style's documented rendering techniques, palette, typography, and composition. This does not change blend_styles' established hero plus two supporting mockups.
Input Schema
{
"type": "object",
"properties": {
"format": {
"type": "string",
"enum": [
"style_guide",
"palette_type_sheet",
"application_brief"
]
},
"style_slugs": {
"type": "array",
"minItems": 1,
"maxItems": 5,
"items": {
"type": "string",
"pattern": "^[a-z0-9]+(?:-[a-z0-9]+)*$"
},
"description": "One to five Omoro style slugs in influence order. The first style leads the composition."
},
"use_case": {
"type": "string",
"maxLength": 240,
"description": "Optional application or project context."
},
"brand_palette": {
"type": "array",
"maxItems": 12,
"items": {
"type": "string",
"pattern": "^#[0-9A-Fa-f]{6}$"
},
"description": "Optional client-supplied colors, clearly kept separate from documented style palettes."
}
},
"required": [
"format",
"style_slugs"
]
}Output Schema
{
"type": "object",
"properties": {
"artifactType": {
"type": "string",
"const": "omoro_visual_artifact"
},
"format": {
"type": "string",
"enum": [
"style_guide",
"palette_type_sheet",
"application_brief"
]
},
"title": {
"type": "string"
},
"theme": {
"type": "object"
},
"canvas": {
"type": "object"
},
"sections": {
"type": "array",
"items": {
"type": "object"
}
},
"sourceStyles": {
"type": "array",
"items": {
"type": "object"
}
},
"visualSystems": {
"type": "array",
"items": {
"type": "object"
}
},
"blendTreatment": {
"type": [
"object",
"null"
]
},
"presentationInstructions": {
"type": "array",
"items": {
"type": "string"
}
}
},
"required": [
"artifactType",
"format",
"title",
"theme",
"canvas",
"sections",
"sourceStyles",
"visualSystems",
"blendTreatment",
"presentationInstructions"
]
}⚪blend_styles(styles, mix)
Build an authentic multi-style blend from two to five Omoro styles. The first two styles anchor the visual direction; added styles are treated as influence layers. Returns defining rendering techniques, visible contribution requirements, fidelity checks, palette and three coordinated mockup prompts: one hero and two distinct supporting applications, presented as a large hero left and two stacked applications right.
Input Schema
{
"type": "object",
"properties": {
"styles": {
"type": "array",
"minItems": 2,
"maxItems": 5,
"items": {
"type": "string"
},
"description": "Two to five style slugs. The first two are the primary pair."
},
"mix": {
"type": "number",
"minimum": 0,
"maximum": 100,
"default": 50,
"description": "Percentage led by the second primary style."
}
},
"required": [
"styles"
]
}🟢list_palettes(style, limit, offset)
List Omoro's named colour palettes. Optionally narrow to a parent style. Each result includes a palette name, mood, parent style and five named hex swatches.
Input Schema
{
"type": "object",
"properties": {
"style": {
"type": "string",
"description": "Parent style slug, e.g. \"brutalism\" or \"cyberpunk\"."
},
"limit": {
"type": "integer",
"minimum": 1,
"maximum": 200,
"default": 50
},
"offset": {
"type": "integer",
"minimum": 0,
"default": 0
}
}
}🟢get_palette(slug)
Retrieve one named Omoro palette by slug, including its parent style, mood and five named hex swatches.
Input Schema
{
"type": "object",
"properties": {
"slug": {
"type": "string",
"description": "Palette slug, e.g. \"soft-club\" or \"raw-concrete\"."
}
},
"required": [
"slug"
]
}🟢search_palettes(query, limit)
Free-text search across palette names, parent styles and mood descriptions. Use this for queries such as "quiet warm studio" or "nightclub neon".
Input Schema
{
"type": "object",
"properties": {
"query": {
"type": "string",
"description": "Words to look for."
},
"limit": {
"type": "integer",
"minimum": 1,
"maximum": 50,
"default": 10
}
},
"required": [
"query"
]
}🟢find_palettes_by_color(hex, limit)
Rank palettes by their closest swatch to a supplied hex colour. Use when a user has a brand colour or image-derived hex and needs compatible Omoro palettes.
Input Schema
{
"type": "object",
"properties": {
"hex": {
"type": "string",
"description": "A six-digit hex colour, e.g. \"#FF6422\"."
},
"limit": {
"type": "integer",
"minimum": 1,
"maximum": 50,
"default": 10
}
},
"required": [
"hex"
]
}🟢list_ui_lab_options
List the product archetypes and visual languages supported by Omoro UI Lab. Use this before building a direction when you need to choose the right interface structure.
Input Schema
{
"type": "object",
"properties": {}
}⚪build_ui_direction(product, language, style, palette, clientBrief, ...)
Build a concrete UI Lab direction brief from a product archetype, visual language, Omoro style and optional palette. Returns layout geometry, palette roles, typography/material guidance, keep/avoid rules and a paste-ready prompt.
Input Schema
{
"type": "object",
"properties": {
"product": {
"type": "string",
"description": "UI Lab product key, for example creative, commerce, analytics or developer."
},
"language": {
"type": "string",
"description": "UI Lab visual language key, for example technical, swiss, industrial or cinematic."
},
"style": {
"type": "string",
"description": "Omoro style slug. Use search_styles or list_styles first."
},
"palette": {
"type": "string",
"description": "Optional Omoro palette slug. Use search_palettes or list_palettes first."
},
"clientBrief": {
"type": "string",
"description": "Optional client direction or project brief to incorporate into the prompt."
},
"promptMode": {
"type": "string",
"enum": [
"omoro",
"client",
"synthesis"
],
"description": "Prompt emphasis: Omoro system, client brief, or a synthesis of both. Defaults to synthesis when clientBrief is supplied."
}
},
"required": [
"product",
"language",
"style"
]
}⚪suggest_ui_landing(goal, audience, feeling, needsInteraction)
Suggest the simplest Omoro landing-page or WebGL direction for a user's goal. Returns a recommended layout, an optional interactive scene, and a few calibration questions before building.
Input Schema
{
"type": "object",
"properties": {
"goal": {
"type": "string",
"description": "What the landing page needs to accomplish, in plain language."
},
"audience": {
"type": "string",
"description": "Who the page is for."
},
"feeling": {
"type": "string",
"description": "The desired feeling or visual language."
},
"needsInteraction": {
"type": "boolean",
"description": "Whether the visual should respond to scroll, pointer or drag."
}
},
"required": [
"goal"
]
}Community
Evidence