Louis Studios
REMOTE · STUDIOS.LOU15.COM
Designs React sites with animated components fitted to your brand, then checks each page.
Available components
Last scanned (21 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Design and Media
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 6600 tokens (~286/item across 23 items; 23 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 23 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “review_page” rewrote its description, which is the text the model reads security
- Server version: 2.0.1 → 2.0.2 functional
- Server version: 2.0.0 → 2.0.1 functional
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 12 Nov 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://studios.lou15.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lou15.com | CN=WE1,O=Google Trust Services,C=US | 23 Oct 2026 | 21 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 5dc2f86579d4a71213079b3784d2edd3 |
| SANs: lou15.com, *.lou15.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of studios.lou15.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| lou15.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://studios.lou15.com/mcp | Verified | 200 | |
| http (plaintext) | http://studios.lou15.com/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
account_status Account ~36
The account behind the key, its plan, the coins it has left and the components it has unlocked (each stays open 30 days).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
adjust_direction Adjust the direction ~425
Call this whenever the user wants the look changed after a direction exists, before composing or fitting anything again. Say the change in plain words in "tweak" ("square corners", "slower", "serif headings", "no glow", "more air", "compact", "glass", "grain off", "darker", "warmer", "accent teal", "luxury + sakura", "less playful") or set explicit knobs. Works on any direction_id, including ones made by create_direction. Returns what changed, anything it did not understand, the new description and the new theme CSS to replace the saved file; compose and fit again afterwards so everything follows.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | What the site or app is and does, in a sentence or two. |
| audience | string | – | Who it is for. |
| avoid | string | – | What the user does not want, for example "playful" or "glow". |
| blend | string | – | A second world mixed in, or "none". |
| brand | string | – | Brand or product name. |
| colors | array | – | Brand colours as hex or names, most important first. Kept exact. Leave out to let the designer choose. |
| cta | string | – | The call to action label. |
| direction_id | string | yes | The direction_id from set_direction or create_direction. |
| headline | string | – | The main headline. |
| knobs | object | – | Explicit settings that override the world. Every one can also be said in plain words through "tweak". |
| mood | string | – | How it should feel, in the user's words. Naming worlds works too: "luxury + sakura", "brutalist", "Y2K". |
| subline | string | – | One supporting sentence. |
| theme | string | – | The default theme. Leave out to let the world decide; both themes are always made. |
| tweak | string | – | The change in plain words. |
| world | string | – | Force a world instead of letting the brief choose. |
No output schema declared.
No examples provided.
browse_rooms Browse the rooms ~150
Every room of the studio: the library, the Island Room, the Sakura Collection, the Icon Room, the Dot Room and the Logo Room, with what each is for and how many items it holds. Pass a room (and words to look for) to search inside it. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Icon Room or Dot Room only: a category, for example "finance" or "Health". |
| limit | integer | – | How many results (default 12). |
| query | string | – | Words to look for, for example "timer", "weather", "neon", "heart rate". |
| room | string | – | Search inside this room. Leave out to list the rooms. |
No output schema declared.
No examples provided.
compose_block Compose a block ~422
Designs one block as a finished TSX file in the direction's world: nav, hero, features, stats, cta, loading, footer, pricing, faq, testimonials, logos, gallery, timeline, contact, feature-icons, split, banner. Pass variant to choose its layout, component to build around a particular piece. Returns the file, the site layer CSS it relies on and the components to install with fit_component.
| Name | Type | Req | Description |
|---|---|---|---|
| brief | object | – | Used when there is no direction_id yet: brand, app (required), audience, mood, colors, theme, headline, subline, cta, avoid, and optionally world. |
| component | string | – | Optional slug to build the block around. |
| content | object | – | The site's real content, in the user's words. Blocks that need facts (numbers, quotes, prices, names) are only planned when they are given here; nothing is invented. |
| copy | object | – | Override the brief's headline, subline or call to action here. |
| direction_id | string | – | The direction_id from set_direction (or create_direction). |
| kind | string | yes | – |
| target | string | – | next: Next.js app router files (default). vite: Vite React files. |
| title | string | – | The section title. |
| variant | string | – | Layout variant. nav: bar, float, masthead; hero: backdrop, split, poster, frame, masthead, kinetic, page; features: rows, columns, bento, sticky; stats: band, inline, boxed; cta: panel, type, quiet;… |
No output schema declared.
No examples provided.
compose_page Compose a page ~308
Designs one page as finished TSX files: the page file, one file per block (nav, hero, sections, footer) and the site layer CSS, laid out for the direction's world, responsive from phone to desktop, accessible, tokens only, real copy. Returns the files, the components to install with fit_component, the copy to confirm, and a short page summary. Check the page with review_page before you show it.
| Name | Type | Req | Description |
|---|---|---|---|
| blocks | array | – | Optional: your own block order instead of the plan's. |
| brief | object | – | Used when there is no direction_id yet: brand, app (required), audience, mood, colors, theme, headline, subline, cta, avoid, and optionally world. |
| content | object | – | The site's real content, in the user's words. Blocks that need facts (numbers, quotes, prices, names) are only planned when they are given here; nothing is invented. |
| copy | object | – | Override the brief's headline, subline or call to action here. |
| direction_id | string | – | The direction_id from set_direction (or create_direction). |
| page | string | – | Which page of the plan, by slug ("" or "home" for the home page, "pricing", "about"...). |
| target | string | – | next: Next.js app router files (default). vite: Vite React files. |
| type | string | – | The site type from plan_site (default landing). |
No output schema declared.
No examples provided.
compose_section Compose a section ~187
Designs one finished section of the app (hero, nav, features, stats, cta or loading) around Louis Studios components tailored to the direction: colours, copy, speed and layout set for this user. Returns a ready TSX file and the components to install for it.
| Name | Type | Req | Description |
|---|---|---|---|
| button | string | – | Optional slug of a Louis Studios button for the call to action. |
| component | string | – | Optional slug to build the section around instead of the designer's pick. |
| copy | object | – | Text for this part, in the user's words. |
| direction_id | string | yes | The direction_id from create_direction. |
| import_base | string | – | Where installed components live, as the import path (default "@/components/ui"). |
| items | array | – | Cards for features or stats: a title (or number) and one line each. |
| kind | string | yes | Which section. |
No output schema declared.
No examples provided.
create_direction Design a direction ~250
Start here. Turns what the user wants into a design direction for the app: a palette built from their colours or mood, type, radius, motion and layout. Returns a direction_id for the other tools and a theme CSS file of tokens to save in the project.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | What the app is and does, in a sentence or two. |
| audience | string | – | Who it is for. |
| avoid | string | – | Things the user does not want, for example "playful". |
| brand | string | – | Brand or product name. |
| colors | array | – | Brand colours as hex ("#ff5a1f") or names ("teal"), most important first. Leave out to let the designer choose. |
| cta | string | – | The call to action label. |
| headline | string | – | The main headline. |
| mood | string | – | How it should feel, in the user's words: "calm and premium", "loud and sporty", "playful", "editorial"... |
| subline | string | – | One supporting sentence. |
| theme | string | – | Force a dark or light theme. Leave out to let the mood decide. |
No output schema declared.
No examples provided.
design_options Show three directions ~374
Call this first, before any page or component work on a new site, once you know what the site is (ask for the brand, what it does, who it is for, the mood and any brand colours if you cannot read them from the project). Returns three clearly different design directions for the brief (different world, palette, type and shape), each with its palette in light and dark and its type. Saves nothing. Show the user the three in a few lines each and ask which one, then call set_direction with the same brief and the chosen option number.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | What the site or app is and does, in a sentence or two. |
| audience | string | – | Who it is for. |
| avoid | string | – | What the user does not want, for example "playful" or "glow". |
| blend | string | – | A second world mixed in, or "none". |
| brand | string | – | Brand or product name. |
| colors | array | – | Brand colours as hex or names, most important first. Kept exact. Leave out to let the designer choose. |
| cta | string | – | The call to action label. |
| headline | string | – | The main headline. |
| knobs | object | – | Explicit settings that override the world. Every one can also be said in plain words through "tweak". |
| mood | string | – | How it should feel, in the user's words. Naming worlds works too: "luxury + sakura", "brutalist", "Y2K". |
| subline | string | – | One supporting sentence. |
| theme | string | – | The default theme. Leave out to let the world decide; both themes are always made. |
| world | string | – | Force a world instead of letting the brief choose. |
No output schema declared.
No examples provided.
fit_component Install a component, fitted to the site ~203
Installs a component licensed to the account, fully fitted to the direction: its colours and type become the product's, and its motion speed and intensity, corners, stroke and border weight, density, light or dark build and sample copy change to suit the site. Costs exactly what install_component costs (its price in coins on Pro 30, free on Max, free again for 30 days). By default a one-line shell command; pass as "source" to get the file itself when you cannot run commands. Call fit_preview first to see what will change.
| Name | Type | Req | Description |
|---|---|---|---|
| as | string | – | "command" (default): a curl command, valid for 15 minutes. "source": the licensed, fitted file. |
| dir | string | – | Project-relative folder (default "components/ui"). |
| direction_id | string | yes | The direction_id from set_direction (or create_direction). |
| slug | string | yes | The component slug, for example "glow-button". |
No output schema declared.
No examples provided.
fit_preview What fitting a component changes ~132
Lists, in plain words, what fit_component will change in one component for a direction (colours, motion, corners, stroke, density, light or dark build, copy) and what stays as made and why, plus the JSX to use it with. Never returns source and costs nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| copy | object | – | Optional copy: brand, headline, subline, cta. |
| direction_id | string | yes | The direction_id from set_direction (or create_direction). |
| role | string | – | The part it plays. |
| slug | string | yes | The component slug, for example "glow-button". |
No output schema declared.
No examples provided.
get_component Read a component ~64
Everything about one component: what it does, every prop with its type, default and meaning, which props the designer can tailor, and the file name.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Component slug, for example "blob-type". Slugs come from recommend_components or search_components. |
No output schema declared.
No examples provided.
get_dots Get dots drawn for the site ~346
Dot Room dots in the product's palette. As "accent": each dot as its own React file (live and animated) with the brand colours, theme, numeral font and ring weight baked in. As "texture": a quiet repeating background made of the chosen dots in one brand tone, as CSS (a class to put on any section) and the SVG tile. Costs like the Dot Room: 1 coin a dot, 10 for the whole archive, free on Max; open 30 days. preview: true shows the plan and price without spending.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | Project-relative folder for files (default "components"). |
| direction_id | string | – | The direction_id (from set_direction or create_direction). Items are drawn in its stroke weight, sizes and colours. |
| dots | array | yes | Dot kinds from browse_rooms (room "dot-room"), for example ["heart-rate", "aqi"]. |
| format | string | – | accent: "react" (default) or "svg" (a still of each). texture: always CSS plus the SVG tile. |
| preview | boolean | – | Only show the plan and the price. Spends nothing. |
| size | number | – | Dot diameter in px (default: the type scale step nearest 64). |
| strength | number | – | texture: how strong it is, 0.03 to 0.6 (default from the direction, about 0.12). |
| tone | string | – | texture: which token tone it is drawn in (default accent). |
| use | string | – | "accent" (default): the dots themselves. "texture": a background made from them. |
No output schema declared.
No examples provided.
get_icons Get icons drawn for the site ~320
Icon Room icons drawn for the product: the stroke weight from the direction's world and borders, the size from its type scale, the accent and quiet parts from its colour tokens (the main stroke is currentColor). Returns ONE React file with a typed, tree-shakeable named export per icon, or SVG strings. Costs like the Icon Room: 1 coin an icon, 10 for the whole archive (taken instead when that is no dearer), free on Max; anything taken stays open 30 days. preview: true shows the look and the price without spending.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Every icon in the archive (10 coins once, free on Max). |
| dir | string | – | Project-relative folder for the file (default "components"). |
| direction_id | string | – | The direction_id (from set_direction or create_direction). Items are drawn in its stroke weight, sizes and colours. |
| format | string | – | "react" (default): one TSX file. "svg": one standalone SVG per icon, colours resolved to the tokens. |
| icons | array | – | Icon names from browse_rooms (room "icon-room"), for example ["bell", "search", "cart"]. |
| preview | boolean | – | Only show the look, the usage and the price. Spends nothing. |
| size | – | – | Pixel size, or "ui" (default, the type scale step nearest 24) or "feature" (nearest 48). |
| stroke | number | – | Override the stroke width on the 24 grid. |
No output schema declared.
No examples provided.
install_component Install a component ~183
Delivers a component licensed to the account. With a direction_id the file arrives restyled for the product: every colour moved into its palette and its type set in the product's faces, so it looks made for this app rather than taken from a catalog. By default a one-line shell command that downloads the file; pass as "source" to get the file itself when you cannot run commands.
| Name | Type | Req | Description |
|---|---|---|---|
| as | string | – | "command" (default): a curl command, valid for 15 minutes. "source": the licensed file. |
| dir | string | – | Project-relative folder (default "components/ui"). |
| direction_id | string | – | The direction to restyle the file for. Always pass it when the app has a direction. |
| slug | string | yes | Component slug, for example "blob-type". Slugs come from recommend_components or search_components. |
No output schema declared.
No examples provided.
make_mark Make a mark for the brand ~289
Draws a mark for the brand from the Logo Room: its initials (or letters you choose) alone or in a circle, rounded or square container, drawn in the direction's colours and weight, flat or with a Logo Room finish that draws as SVG (haze, tube, sign, halftone, topo). Returns the SVG and a React component. Costs like a Logo Room export: 1 coin, free on Max. preview: true returns a tiny text outline and the plan without spending.
| Name | Type | Req | Description |
|---|---|---|---|
| container | string | – | Default: what the direction's world suggests. |
| dir | string | – | Project-relative folder for the file (default "components"). |
| direction_id | string | – | The direction_id (from set_direction or create_direction). Items are drawn in its stroke weight, sizes and colours. |
| finish | string | – | Default: flat for most directions, a light finish for neon worlds. |
| letters | string | – | 1 to 3 letters or digits. Default: the brand's initials. |
| name | string | – | Component name (default "<Brand>Mark"). |
| preview | boolean | – | A tiny outline and the plan only. Spends nothing. |
| size | number | – | Default width in px for the component (default from the type scale). |
| solid | boolean | – | A solid container with the letters cut out, instead of a line around them. |
No output schema declared.
No examples provided.
plan_site Plan a site ~194
Maps a brief to a whole site: the pages for the site type and, for each, the ordered blocks with the variant the direction's world favours, the Louis Studios component picked for it and why. One statement piece per screen, quiet surroundings. Blocks that need facts the content does not give are left out and listed. Then compose_page each page.
| Name | Type | Req | Description |
|---|---|---|---|
| brief | object | – | Used when there is no direction_id yet: brand, app (required), audience, mood, colors, theme, headline, subline, cta, avoid, and optionally world. |
| content | object | – | The site's real content, in the user's words. Blocks that need facts (numbers, quotes, prices, names) are only planned when they are given here; nothing is invented. |
| direction_id | string | – | The direction_id from set_direction (or create_direction). |
| type | string | yes | What kind of site. |
No output schema declared.
No examples provided.
preview_component Look at a component ~54
A still image of the component as it looks on the site, with links to its page and video.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Component slug, for example "blob-type". Slugs come from recommend_components or search_components. |
No output schema declared.
No examples provided.
recommend_components Recommend components ~148
Picks Louis Studios components for each part of an app (hero, buttons and controls, navigation, data and cards, loading, AI and voice). With a direction_id the picks suit that direction and come back already tailored to it.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | What the app is, when there is no direction yet. |
| colors | array | – | Optional, without a direction: colours to favour. |
| direction_id | string | – | The direction_id from create_direction. |
| per_section | integer | – | Picks per part (default 2). |
| sections | array | – | Optional: the parts you need, for example ["hero", "pricing cards", "loading", "settings toggles"]. |
No output schema declared.
No examples provided.
review_page Review a page ~334
Checks a page you composed before the user sees it. Pass the direction_id and the files you wrote, each with its content (page file, block files, CSS). Returns findings, each with severity, file and line, the problem and the exact fix: contrast below WCAG AA, also across the whole page where sections with different backgrounds meet (text inheriting the page colours onto a band, components fitted for the page placed on an opposite band, elements pulled across a section edge), colours outside the direction, more than one statement piece on a screen, images without alt, missing landmarks or skipped headings, motion without a reduced-motion fallback, widths that overflow a 375px phone, placeholder copy, missing licence headers. When this server can render, also screenshots at 1440 and 375px and what it measured there (sideways scroll, clipped or overlapping text, small tap targets, real contrast). Free; fix every high finding, then review again.
| Name | Type | Req | Description |
|---|---|---|---|
| direction_id | string | – | The direction the page was composed for. |
| entry | string | – | Optional: the path of the file that renders the page, when it is not page.tsx, App.tsx or index.tsx. |
| files | array | – | The page file, its block files and any CSS it imports. Installed component files are optional (without them each shows as a labelled box in the screenshot). |
| page | object | – | Instead of files: an object that holds them, { files: [{ path, content }] }. |
| widths | array | – | Optional screenshot widths in px (default [1440, 375]). |
No output schema declared.
No examples provided.
search_components Search the library ~81
Search Louis Studios components by words, category and colour. Leave everything empty to list the newest.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| color | string | – | – |
| limit | integer | – | How many results (default 10). |
| query | string | – | Words to look for, for example "countdown", "glass toggle", "liquid chrome". |
No output schema declared.
No examples provided.
set_direction Save the direction ~403
Call this once the user has picked one of the design_options (pass the same brief plus option 1, 2 or 3), or straight away when the user already knows the look (pass world, blend and knobs, or a tweak in plain words). Saves the direction and returns its direction_id, a description to tell the user, and the theme CSS for both light and dark: save it as styles/louis-studios-theme.css and import it once in the root layout. Every other designer tool takes this direction_id.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | yes | What the site or app is and does, in a sentence or two. |
| audience | string | – | Who it is for. |
| avoid | string | – | What the user does not want, for example "playful" or "glow". |
| blend | string | – | A second world mixed in, or "none". |
| brand | string | – | Brand or product name. |
| colors | array | – | Brand colours as hex or names, most important first. Kept exact. Leave out to let the designer choose. |
| cta | string | – | The call to action label. |
| headline | string | – | The main headline. |
| knobs | object | – | Explicit settings that override the world. Every one can also be said in plain words through "tweak". |
| mood | string | – | How it should feel, in the user's words. Naming worlds works too: "luxury + sakura", "brutalist", "Y2K". |
| option | number | – | Which of the three design_options for this same brief. |
| subline | string | – | One supporting sentence. |
| theme | string | – | The default theme. Leave out to let the world decide; both themes are always made. |
| tweak | string | – | Changes in plain words to apply before saving, as in adjust_direction. |
| world | string | – | Force a world instead of letting the brief choose. |
No output schema declared.
No examples provided.
tailor_component Tailor a component ~121
Configures one component for the direction: its colours from the palette, its text from the user's copy, its pace from the motion. Returns the tailored JSX and what was changed, and says when a component's own colours cannot change.
| Name | Type | Req | Description |
|---|---|---|---|
| copy | object | – | Text for this part, in the user's words. |
| direction_id | string | yes | The direction_id from create_direction. |
| role | string | – | The part it plays. |
| slug | string | yes | Component slug, for example "blob-type". Slugs come from recommend_components or search_components. |
No output schema declared.
No examples provided.
update_direction Adjust the direction ~273
Changes a direction when the user wants it different. Pass only what changes, and/or a tweak in plain words ("warmer", "more playful", "lighter", "more luxurious"). Returns the new palette, type and tokens; compose sections again afterwards.
| Name | Type | Req | Description |
|---|---|---|---|
| app | string | – | What the app is and does, in a sentence or two. |
| audience | string | – | Who it is for. |
| avoid | string | – | Things the user does not want, for example "playful". |
| brand | string | – | Brand or product name. |
| colors | array | – | Brand colours as hex ("#ff5a1f") or names ("teal"), most important first. Leave out to let the designer choose. |
| cta | string | – | The call to action label. |
| direction_id | string | yes | The direction_id from create_direction. |
| headline | string | – | The main headline. |
| mood | string | – | How it should feel, in the user's words: "calm and premium", "loud and sporty", "playful", "editorial"... |
| subline | string | – | One supporting sentence. |
| theme | string | – | Force a dark or light theme. Leave out to let the mood decide. |
| tweak | string | – | The change in plain words. |
No output schema declared.
No examples provided.
How do I install the Louis Studios MCP server?
Louis Studios is a hosted endpoint at https://studios.lou15.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · studios.lou15.com
claude mcp add --transport http com-lou15-studios-designer 'https://studios.lou15.com/mcp'
What is the Louis Studios MCP server?
Louis Studios is an MCP server listed in the public MCP registry as com.lou15.studios/designer. Designs React sites with animated components fitted to your brand, then checks each page. This page covers its hosted endpoint (https://studios.lou15.com/mcp).
Is the Louis Studios MCP server safe to use?
Louis Studios scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Louis Studios MCP server expose?
Louis Studios exposes 23 tools: create_direction, update_direction, compose_section, recommend_components, tailor_component, and 18 more. Their descriptions and schemas cost roughly 5,297 tokens of context every time the server is loaded.
Does the Louis Studios MCP server require authentication?
No. We connected to Louis Studios without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Louis Studios MCP server still maintained?
Louis Studios is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Louis Studios MCP server?
VerifyMCP ran 12 checks on Louis Studios, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Louis Studios: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.