Blender integration through the Model Context Protocol
Nothing to run from here
Designers 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.
93/100
tool-list score
21
tools declared
remote
at its publisher
—
calls last 7d
What it does
Checks, prompts and skills for designers working with AI: contrast, a11y, heuristics, critique.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http designers-mcp https://designers.allthepossibles.com/mcp
# 2 — ask your agent for something these tools do
# check_contrast, audit_page_accessibility, heuristic_worksheet and 18 more
Designers costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ALAll 6 servers
allthepossibles6 servers
4 categories
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 designers-mcp https://designers.allthepossibles.com/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 asks of you
Nothing is required, but it can take Authorization header (Optional. Bearer dz_... for Pro; every free tool works with no key. Install steps per client: https://designers.allthepossibles.com/docs/install) if you want to set it.
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
21 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.
Check colour contrast. Give fg and bg, or pairs (a list of {fg, bg, label, sizePx, bold}), or a palette. Returns the WCAG 2.2 ratio with AA and AAA results for the text size, APCA Lc with what it is enough for, the nearest passing colour, and for palettes the colour pairs that become indistinguishable under protanopia, deuteranopia or tritanopia. Accepts hex, rgb(), hsl() and CSS names.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fg | string | no | Foreground colour |
| bg | string | no | Background colour |
| sizePx | number | no | Text size in CSS px, default 16 |
| bold | boolean | no | True if the text is bold, which changes the large-text threshold |
| pairs | array | no | Several pairs at once |
| palette | array | no | Colours to test against white, black and each other under colour blindness |
Audit one page's static HTML for accessibility problems and name the WCAG 2.2 criterion for each: missing lang or title, images without alt, unlabelled form fields, vague or empty links and buttons, heading jumps, no main landmark, zoom-blocking viewport, autoplay with sound, tabindex above zero, duplicate ids, click handlers on non-interactive elements, tiny inline targets. It reads markup only a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | no | Public page to fetch |
| html | string | no | Or paste HTML instead |
| compareUrl | string | no | A second URL (for example the redesign): returns what was fixed, what is new and what remains |
Build a Nielsen ten-heuristics review worksheet for a screen or flow. Give text (the copy of the flow), html or a url. Returns, for each heuristic, keyword and markup signals found or missing, review prompts, and blanks for findings and 0 to 4 severity. The signals point at where to look; a human evaluation is still required.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | no | Screen or flow copy |
| html | string | no | Page HTML, if you have it instead of a URL |
| url | string | no | Public page to read instead of pasted text |
| task | string | no | The task the reviewer is evaluating, e.g. 'change a billing address' |
Look for the default AI-generated design look in a live page's markup and CSS: purple-to-blue gradients, gradient text, a default font stack, pill buttons with arrows, uppercase eyebrow labels, emoji headings, glassmorphism, glow blobs, equal card grids, stock marketing phrases and placeholder copy. Returns weighted signals and a 0 to 100 score. Signals, not proof.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Public page to read |
| compareUrl | string | no | A second URL: returns what became less or more generic |
Review interface copy, one string per line, optionally prefixed with a type (button:, error:, empty:, tooltip:, placeholder:, heading:, toast:, label:). Checks each string for what its type needs (errors say what to do, empty states give a next step, buttons name the outcome), checks the set for inconsistency, and runs AI-writing tells over everything.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | no | One string per line, e.g. 'button: Submit' or 'error: Invalid input' |
| items | array | no | Or a list of strings or {text, type} |
Lint design critique. Sorts each note into observation, opinion, solution-without-problem, vague, or question, explains what is missing, and gives an observation, impact, suggestion skeleton for weak notes. Reports the share of notes ready to act on.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | One note per line, or paragraphs |
Plan a design critique for a stage (concept, wireframe, visual, prototype, build, shipped): a framing statement, timed agenda, the questions that fit the stage, roles, and the kinds of feedback to turn away until a later stage.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| description | string | yes | A sentence or two about the design |
| stage | string | yes | Where the work is now |
| goal | string | no | What the design has to achieve |
| audience | string | no | Who it is for |
| minutes | integer | no | Session length, 15 to 120, default 30 |
Lint user research questions, one per line, for leading wording, double-barrelled questions, hypotheticals, predictions, loaded words, jargon, closed questions in an open interview, why-questions and unlabelled rating scales, with a suggested rewrite for each problem.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | One question per line |
| mode | string | no | Default interview |
Usability arithmetic with formulas shown. mode sus: score System Usability Scale responses (rows of ten 1-5 answers) with grade, percentile and 95% interval. mode discovery: participants needed to find a share of problems (Nielsen and Landauer). mode ab: sample size per variant for a conversion test (baseline, lift in percent, optional dailyVisitors). mode survey: responses needed for a margin of
| Parameter | Type | Required | Notes |
|---|---|---|---|
| mode | string | no | Which calculator |
| responses | array | no | sus: array of 10-number arrays |
| p | number | no | discovery: chance a participant hits a problem, default 0.31 |
| target | number | no | discovery: share of problems to find, default 0.85 |
| baseline | number | no | ab: current conversion rate, e.g. 0.05 |
| lift | number | no | ab: smallest relative lift to detect, percent |
| alpha | number | no | ab: significance level, 0.1, 0.05 or 0.01 |
| power | number | no | ab: 0.8, 0.9 or 0.95 |
| dailyVisitors | integer | no | ab: traffic per day, to estimate how long to run |
| margin | number | no | survey: margin of error, e.g. 0.05 |
| confidence | number | no | survey: 0.9, 0.95 or 0.99 |
| population | integer | no | survey: total population, for the finite-population correction |
Lint a product analytics tracking plan (event names with optional properties, one per line like 'project_created (template, source)') for mixed naming styles, vague events, UI-element names, near-duplicate events, tense and order drift, and personal data in property names. With no events and a productType (saas, ecommerce, marketplace, content, mobile) it drafts a starter plan.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | no | Events, one per line, or a JSON array |
| events | array | no | Or a list of strings or {name, properties} |
| productType | string | no | Draft a starter plan for this kind of product |
Pro. Crawl up to 15 same-origin pages from a start URL, audit each one's static HTML for WCAG 2.2 problems, and report issues by how many pages they affect so that shared-template problems come first. Returns a markdown report.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Start page |
| maxPages | integer | no | 2 to 15, default 10 |
Take a design token file (CSS custom properties like --color-text: #111;, a JSON object of colours, or W3C design tokens) and test every foreground-like token against every background-like token for 4.5:1 text and 3:1 component contrast, with the nearest passing colour, and find colours that merge under colour blindness. Free up to about 30 colours; Pro takes 200. Returns a markdown report.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tokens | string | yes | The token file contents |
Pro. Build a scored, exportable markdown report from heuristic evaluation findings you have written. Each finding has heuristic (1 to 10), severity (0 to 4), location, issue, effect, fix and optional effort (S, M, L) and evaluator. Merges duplicates across evaluators, computes a health score, and sorts a fix-first table.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | no | Report title |
| task | string | no | The task that was evaluated |
| findings | array | yes | Findings from the evaluation |
Explain what this server can do and suggest the three best first tasks for what the person has (a Figma link, a live URL, copy, a research plan, an event list). Use this first when the person is new or unsure what to ask for.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| have | string | no | What they have, in their own words, e.g. 'a Figma link and some button copy' |
Show the caller's plan (Free or Pro) and how many calls remain today on each tool. Does not use up a daily call.
No parameter schema on file.
Check target sizes and spacing against WCAG 2.2 SC 2.5.8 (24 by 24 CSS px, or a smaller target with enough spacing), the 44px guidance for iOS and the web, and 48dp for Android. Pass targets as a list of {name, width, height, gap, inline} or text lines like 'Save button 40x32 gap=8'. Returns pass or fail per guideline with advice.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| targets | array | no | Targets to check |
| text | string | no | Or lines like 'Close icon 32x32 gap=4' |
Lint design token names from a list, CSS variables or a JSON token file: mixed separators, colours named by hue where roles belong, values or locations in names, version words, duplicate values, abbreviation drift (bg and background) and irregular scales.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | Token names or file contents |
Score a DESIGN.md (the brand and design context file models read before building): missing sections, no hex values, text and background pairs that fail contrast, too many typefaces, adjectives a model reads as the generic look, no never-list, no sizes, too long or too thin.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | string | yes | The DESIGN.md contents |
Diagnose setup problems. Reports what the server sees about this connection (client, whether a Pro key was received and is active, plan), checks a Figma link for the right shape (frame link with node-id, not a prototype or Community page), and matches a described symptom to fixes for: connected but nothing happens, local versus remote servers, 401 and 403, rate limits, tools or skills not triggeri
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symptom | string | no | What is going wrong, in the person's words |
| client | string | no | Claude Desktop, claude.ai, Claude Code, Cursor, VS Code, Codex or ChatGPT |
| figmaLink | string | no | A Figma link to check |
Pro. Save named project context (brand notes, a DESIGN.md, past decisions, personas) against the Pro key, up to 20 items of 50,000 characters, so later sessions and prompts can reuse it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | e.g. design-md, brand-voice |
| content | string | yes | The text to save |
Pro. List the saved project context, or read one item by name.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | no | Omit to list everything saved |
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 Designers 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: —
ATool-list grade · score 93 / 100
Release 1.1.0 · scanned 30 Oct 2026
Graded from the tools this server lists, not from its source code.
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.
Threat score100
Client score93
Findings0 threat · 4 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest6d1960f8ec42804a08cfe0e0c53dcd471805a611c19aa981086b823be2c8ffb9
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| check_contrast | no tags | |
| audit_page_accessibility | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| heuristic_worksheet | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| detect_design_slop | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| review_ui_copy | no tags | |
| lint_design_feedback | no tags | |
| plan_critique | no tags | |
| lint_research_questions | no tags | |
| usability_stats | no tags | |
| lint_tracking_plan | no tags | |
| audit_site_accessibility | untrusted-input | untrusted-input: keyword "crawl", declares openWorldHint: true (interacts with entities outside the server) |
| check_contrast_tokens | no tags | |
| build_heuristic_report | no tags | |
| getting_started | no tags | |
| whoami | no tags | |
| check_touch_targets | no tags | |
| lint_token_names | no tags | |
| lint_design_md | no tags | |
| doctor | no tags | |
| save_project_context | no tags | |
| get_project_context | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest6d1960f8ec42804a
Scanned2026-10-30
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
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.1.0.
1.1.0
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 Designers 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.