mcpField
D
designmind

designmind

Local
github.com/CloudCorpRecordsMemory & Knowledge0Updated 1w ago

About designmind

designmind is a local MCP server and CLI for design knowledge, aimed at designers and teams seeking reference material. Its curated, read-only catalogue covers principles, patterns, design systems, brand, content, research, metrics, and service standards.

Key features

  1. 01Design principles and UX guidance
  2. 02UI patterns and checklists
  3. 03Design-system token lookup and merging
  4. 04Brand and content guidance
  5. 05Research methods and metrics frameworks

Use cases

  1. 01Reviewing a design description against principles
  2. 02Finding guidance for a UI pattern before shipping
  3. 03Merging tokens from multiple design systems
  4. 04Looking up a research method or metrics framework

MCP support

The MCP server exposes 20 read-only tools for searching and retrieving its local design-knowledge catalogue.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"cloudcorprecords-designmind": {
"command": "npx",
"args": [
"-y",
"@reneturcios/designmind"
]
}
}
}
Run commandnpx -y @reneturcios/designmind

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@reneturcios/designmind0.1.0
ocighcr.io/cloudcorprecords/designmind:0.1.0

Tools

20

Saved tool list · updated 1w ago

ParameterTypeRequiredDescription
contextstringYesDesign context to match principles against, such as forms, navigation, or accessibility.

Details

From the project README

designmind

Local design knowledge as an MCP server and CLI: principles, UI patterns, checklists, design-system tokens, brand and content systems, research methods, metrics frameworks, and the GOV.UK Service Standard — all served from a curated catalogue that ships with the package. No network, no API key, no state.

designmind is a labelled core subset (20 tools) rebuilt from the public tool spec of a 111-tool design-knowledge server. The tools that audit live sites, grab assets, run a taste engine or a creative studio, maintain a decision graph, or run generation jobs are intentionally not reproduced; what is here is the read-only knowledge core.

What the catalogue contains

Original prose written for this rebuild, covering:

  • Principles — Nielsen's ten heuristics, Laws of UX (Fitts, Hick, Jakob, Miller, Doherty, Von Restorff, Peak-End), Gestalt principles, WCAG AA basics (contrast, focus, labels, not colour alone), and typography, colour-role and spacing-scale rules.
  • UI patterns and checklists — dashboards, forms, navigation, onboarding, search, checkout, empty states, modals, tables and settings, each with guidance and pitfalls.
  • Design systems — token sets for Material, Carbon, Polaris, Atlassian and GOV.UK, which can be merged with compose_system (later sources win; every conflict is listed, never hidden).
  • Brand and content systems — brand guidance plus voice and tone systems for GOV.UK, Polaris, Atlassian and conversational UI, content principles, and content patterns (error messages, empty states, confirmations, help text, notifications, labels).
  • Strategy and methods — business strategy topics, the D4D (Discover, Define, Develop, Deliver) framework with templates, research methods, HEART / AARRR / North Star / RICE / OKR, and service patterns with the 14-point GOV.UK Service Standard.

Coverage differs from the original server's catalogue — this is a fresh local curation, not a copy of its content.

Install and run

npx -y @reneturcios/designmind mcp        # stdio MCP server
npx -y @reneturcios/designmind get_pattern form
docker run -i ghcr.io/cloudcorprecords/designmind          # MCP via container
docker run --rm ghcr.io/cloudcorprecords/designmind get_checklist form

MCP client config:

{
  "mcpServers": {
    "designmind": {
      "command": "npx",
      "args": ["-y", "@reneturcios/designmind", "mcp"]
    }
  }
}

Tools

ToolArgumentsPurpose
get_principlescontextPrinciples relevant to a context
get_patternui_typeUI pattern guidance
get_business_strategytopic?Business strategy guidance
evaluate_designdescription, compact?Score a design description against the principles catalogue — scores, matching principles and violations; no screenshots
search_knowledgequerySearch the whole catalogue
get_checklistui_typeA pre-ship checklist
get_d4d_frameworktemplate?Discover / Define / Develop / Deliver
list_design_systems—Catalogue design systems
get_design_systemnameOne system's token set
compose_systemsources[]Merge token sets; later wins, conflicts listed
get_brand_systembrandBrand guidance for a named brand
get_content_systembrandVoice and tone system for a named brand
get_content_principlestopic?Content design principles
get_content_patternpattern_typeA content pattern (errors, empty states, …)
get_research_methodmethod_typeA UX research method, with steps
get_metrics_frameworkframeworkHEART, AARRR, North Star, RICE or OKR
get_service_patternpatternA service design pattern
get_service_standard—The GOV.UK Service Standard, 14 points
get_brand_principlestopic?Brand principles
get_brand_trends—Curated brand design trends

Unknown names (a system, brand, framework, pattern…) return an error listing the names that do exist, rather than a guess. The CLI exposes the same twenty operations as subcommands; run designmind with no arguments for the full usage list.

Development

npm install
npm run build   # tsc -> dist/
npm test        # node test runner, local only
npm run dev     # run the CLI from source

License

MIT — Copyright (c) 2026 Rene Turcios.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.