Blender integration through the Model Context Protocol
Nothing to run from here
OMORO Style Library is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
16
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Search, compare, and blend structured visual aesthetics, palettes, and creative directions.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http omoro-style-library-mcp https://omoro.io/api/mcp
# 2 — ask your agent for something these tools do
# get_started, list_styles, get_style and 13 more
OMORO Style Library costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
OMAll 1 server
omoro1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http omoro-style-library-mcp https://omoro.io/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
16 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Show the Omoro MCP welcome guide: what is available, what each option does and which tool to use first.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| group | string | no | Mood group to filter by. |
| category | string | no | — |
| limit | integer | no | — |
| offset | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | The style's slug, e.g. "bauhaus". Get one from list_styles or 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Words to look for, e.g. "darkroom film grain". |
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| minimal_maximal | number | no | Target position on the minimal_maximal axis, -1 to 1. |
| analog_digital | number | no | Target position on the analog_digital axis, -1 to 1. |
| expressive_restrained | number | no | Target position on the expressive_restrained axis, -1 to 1. |
| warm_cool | number | no | Target position on the warm_cool axis, -1 to 1. |
| futuristic_nostalgic | number | no | Target position on the futuristic_nostalgic axis, -1 to 1. |
| structured_chaotic | number | no | Target position on the structured_chaotic axis, -1 to 1. |
| light_dark | number | no | Target position on the light_dark axis, -1 to 1. |
| organic_geometric | number | no | Target position on the organic_geometric axis, -1 to 1. |
| limit | integer | no | — |
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 ble
| Parameter | Type | Required | Notes |
|---|---|---|---|
| taste_axes | object | yes | 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, + expr |
| brand_palette | array | no | Exact brand colors as six-digit hex codes. When supplied, all three directions must stay within these colors. |
| avoid_styles | array | no | Style slugs the user or brand has rejected or already overuses. |
| brand_context | object | no | Known, user-provided brand facts Muse may use for positioning and messaging. Omit unknown fields; the tool will leave them as open inputs. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| a | string | yes | First style slug. |
| b | string | yes | Second style slug. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| format | string | yes | — |
| style_slugs | array | yes | One to five Omoro style slugs in influence order. The first style leads the composition. |
| use_case | string | no | Optional application or project context. |
| brand_palette | array | no | Optional client-supplied colors, clearly kept separate from documented style palettes. |
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 a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| styles | array | yes | Two to five style slugs. The first two are the primary pair. |
| mix | number | no | Percentage led by the second primary style. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| style | string | no | Parent style slug, e.g. "brutalism" or "cyberpunk". |
| limit | integer | no | — |
| offset | integer | no | — |
Retrieve one named Omoro palette by slug, including its parent style, mood and five named hex swatches.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Palette slug, e.g. "soft-club" or "raw-concrete". |
Free-text search across palette names, parent styles and mood descriptions. Use this for queries such as "quiet warm studio" or "nightclub neon".
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Words to look for. |
| limit | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| hex | string | yes | A six-digit hex colour, e.g. "#FF6422". |
| limit | integer | no | — |
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.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| product | string | yes | UI Lab product key, for example creative, commerce, analytics or developer. |
| language | string | yes | UI Lab visual language key, for example technical, swiss, industrial or cinematic. |
| style | string | yes | Omoro style slug. Use search_styles or list_styles first. |
| palette | string | no | Optional Omoro palette slug. Use search_palettes or list_palettes first. |
| clientBrief | string | no | Optional client direction or project brief to incorporate into the prompt. |
| promptMode | string | no | Prompt emphasis: Omoro system, client brief, or a synthesis of both. Defaults to synthesis when clientBrief is supplied. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| goal | string | yes | What the landing page needs to accomplish, in plain language. |
| audience | string | no | Who the page is for. |
| feeling | string | no | The desired feeling or visual language. |
| needsInteraction | boolean | no | Whether the visual should respond to scroll, pointer or drag. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install OMORO Style Library or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.6.2.
1.6.2
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish OMORO Style Library can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.