Omoro MCP server

• Registry nameio.omoro/style-libraryverified in the MCP registry

The registry name sits under omoro.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-19
• Tools16
• Server calls itselfomoro-library
• Server version1.6.0
• Protocol version2025-06-18

On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 102 ms.

• Whether its tools do the product's job has not been judged yet.
• Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
• Answeredmeasuring3 of the 7 daily checks it takes to print a share
• Median first answer133 ms
• Space in an agent's context≈ 3,116 tokensthe definitions of all its tools (16), which an agent carries on every turn
• Tool definitionsB · 76 of 100
• Typed results16 of 16 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 7 of 16
• Not saying whether it only reads or can destroy: 16 of 16

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• get_started

  Show the Omoro MCP welcome guide: what is available, what each option does and which tool to use first.

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

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

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

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

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

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

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

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

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

• get_palette

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

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

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

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

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

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