OMORO Style Library

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Search, compare, and blend structured visual aesthetics, palettes, and creative directions.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "OMORO Style Library": {
      "url": "https://omoro.io/api/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (17)

• get_started

  Show the Omoro MCP welcome guide, including how to search styles and palettes, build UI directions, and create an original character with the character builder.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_styles

  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.

  Parameters:

  • group — string — Mood group to filter by.
  • limit — integer
  • offset — integer
  • category — string

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• get_style

  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.

  Parameters:

  • slug (required) — string — The style's slug, e.g. "bauhaus". Get one from list_styles or search_styles.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• search_styles

  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.

  Parameters:

  • query (required) — string — Words to look for, e.g. "darkroom film grain".
  • limit — integer

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• find_styles_by_attributes

  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.

  Parameters:

  • limit — integer
  • warm_cool — number — Target position on the warm_cool axis, -1 to 1.
  • light_dark — number — Target position on the light_dark axis, -1 to 1.
  • analog_digital — number — Target position on the analog_digital axis, -1 to 1.
  • minimal_maximal — number — Target position on the minimal_maximal axis, -1 to 1.
  • organic_geometric — number — Target position on the organic_geometric axis, -1 to 1.
  • structured_chaotic — number — Target position on the structured_chaotic axis, -1 to 1.
  • futuristic_nostalgic — number — Target position on the futuristic_nostalgic axis, -1 to 1.
  • expressive_restrained — number — Target position on the expressive_restrained axis, -1 to 1.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• suggest_style_directions

  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.

  Parameters:

  • taste_axes (required) — object — 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).
  • avoid_styles — array — Style slugs the user or brand has rejected or already overuses.
  • brand_context — object — Known, user-provided brand facts Muse may use for positioning and messaging. Omit unknown fields; the tool will leave them as open inputs.
  • brand_palette — array — Exact brand colors as six-digit hex codes. When supplied, all three directions must stay within these colors.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• compare_styles

  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.

  Parameters:

  • a (required) — string — First style slug.
  • b (required) — string — Second style slug.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• build_style_guide_output

  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.

  Parameters:

  • format (required) — string
  • style_slugs (required) — array — One to five Omoro style slugs in influence order. The first style leads the composition.
  • use_case — string — Optional application or project context.
  • brand_palette — array — Optional client-supplied colors, clearly kept separate from documented style palettes.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• build_character

  Build an original character brief grounded in Omoro styles. Returns an Omoro Characters-compatible JSON file and a detailed image prompt; it does not generate images or save anything to an account. Import the JSON at omoro.io/characters to keep editing there.

  Parameters:

  • concept (required) — string — The character idea, personality, story or brief. Include what makes them distinct.
  • style_slugs (required) — array — One or two Omoro style slugs, with the lead style first. Find styles with search_styles or list_styles.
  • kind — string — Choose creature for a non-human or hybrid design.
  • name — string — Character name, if chosen.
  • role — string — Their role or place in the story.
  • gender — string
  • output — string — A single portrait or four-view reference sheet.
  • render — string
  • palette — array — Optional exact client colors. Otherwise the documented Omoro style palette is used.
  • setting — string — Optional scene or environment.
  • species — string — Species or ancestry, especially for original creatures and hybrids.
  • wardrobe — string — Clothing, silhouette and materials.
  • hairstyle — string — Optional signature hairstyle. Describe the exact silhouette and unusual construction, such as sculptural coils arranged as a crown, braided loops, asymmetry, or an unexpected shape. Make it personal to this character.
  • signature_item — string — A memorable accessory or visual identifier.
  • appearance_notes — string — Distinctive physical features and overall presence.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• blend_styles

  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.

  Parameters:

  • styles (required) — array — Two to five style slugs. The first two are the primary pair.
  • mix — number — Percentage led by the second primary style.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• list_palettes

  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.

  Parameters:

  • limit — integer
  • style — string — Parent style slug, e.g. "brutalism" or "cyberpunk".
  • offset — integer

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• get_palette

  Retrieve one named Omoro palette by slug, including its parent style, mood and five named hex swatches.

  Parameters:

  • slug (required) — string — Palette slug, e.g. "soft-club" or "raw-concrete".

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• search_palettes

  Free-text search across palette names, parent styles and mood descriptions. Use this for queries such as "quiet warm studio" or "nightclub neon".

  Parameters:

  • query (required) — string — Words to look for.
  • limit — integer

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• find_palettes_by_color

  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.

  Parameters:

  • hex (required) — string — A six-digit hex colour, e.g. "#FF6422".
  • limit — integer

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• 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.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• build_ui_direction

  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.

  Parameters:

  • product (required) — string — UI Lab product key, for example creative, commerce, analytics or developer.
  • language (required) — string — UI Lab visual language key, for example technical, swiss, industrial or cinematic.
  • style (required) — string — Omoro style slug. Use search_styles or list_styles first.
  • palette — string — Optional Omoro palette slug. Use search_palettes or list_palettes first.
  • promptMode — string — Prompt emphasis: Omoro system, client brief, or a synthesis of both. Defaults to synthesis when clientBrief is supplied.
  • clientBrief — string — Optional client direction or project brief to incorporate into the prompt.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

• suggest_ui_landing

  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.

  Parameters:

  • goal (required) — string — What the landing page needs to accomplish, in plain language.
  • feeling — string — The desired feeling or visual language.
  • audience — string — Who the page is for.
  • needsInteraction — boolean — Whether the visual should respond to scroll, pointer or drag.

  Hints: read-only not declared · destructive not declared · idempotent not declared · open-world not declared

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.