Raven MCP
rhinocap/raven-mcp
Base de conhecimento em design para Claude gerar interfaces melhores
Ver no GitHubServidor MCP que fornece inteligência em design para Claude ao gerar interfaces. Integra 8 camadas de conhecimento: princípios de UX, padrões comprovados, sistemas de conteúdo, pesquisa, design de serviço, brand/visual, estratégia de negócio e design tokens. Permite que Claude acesse uma base de conhecimento completa sobre design ao criar UIs.
Instalação
npx convez-ai rhinocap/raven-mcp1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Gerar interfaces com princípios de UX validados (Nielsen, Laws of UX, WCAG)
- Criar fluxos de signup, pricing pages e dashboards com padrões comprovados
- Validar design decisions contra frameworks de pesquisa (HEART, AARRR, North Star)
- Implementar design tokens de sistemas reais (Stripe, Linear)
- Manter consistência de brand e guidelines em assets visuais
Veredito

Ferramenta madura e bem-estruturada que democratiza conhecimento de design para geração de UI com Claude. Cobertura abrangente (8 camadas) e documentação clara fazem dela referência sólida, mas requer familiaridade com conceitos de UX para máximo proveito.
README
A tradução para o português deste README ainda está na fila.
Raven MCP
Odin's ravens brought back knowledge of the world — Raven brings back design intelligence.
A design knowledge MCP server that Claude can query when generating UI. Eight layers: principles, patterns, content design systems, research methods, service design, brand/visual, business strategy, and design tokens.
Raven MCP is a personal open-source project by Andrew Cunliffe. It is not endorsed by, affiliated with, or supported by Intuit Inc. or any other company referenced in its source data. See NOTICE for full attribution of upstream sources and their licenses.
What it does
Raven gives Claude access to a comprehensive design knowledge base:
- Principles — Nielsen's 10 Heuristics, all 21 Laws of UX, Gestalt principles, WCAG accessibility, typography rules, color theory, mobile UX, D4D framework, UX writing, service design, and brand
- Patterns — Proven UI patterns for signup flows, pricing pages, navigation, forms, landing pages, dashboards, modals, empty/error/loading states, CTAs, social proof, mobile conversion — plus content patterns (error messages, empty-state copy, notifications, form validation) and service patterns (service blueprinting, human handoff, signup-as-service, omnichannel continuity, moments of truth)
- Content systems — Voice & tone guides from publicly documented brand systems: Mailchimp, GOV.UK, Shopify Polaris, and Atlassian
- Research — Qualitative, quantitative, and usability methods with do/don't protocols and checklists. Metrics frameworks: HEART, AARRR/Pirate, North Star Metric, conversion funnel, RICE, OKRs.
- Service design — Service blueprinting (with HTML blueprint generation — current vs. ideal state), human-handoff patterns, signup-as-service, omnichannel continuity, moments of truth / recovery, and the GOV.UK Service Standard
- Brand & visual — Logo usage (clear space, min sizes, variants, placement, restraint), gradient usage (hierarchy, palette, contrast, trend vs signature), imagery (consistency, representation, purpose), visual hierarchy, brand-as-system, and current (2026) visual-design trends
- Business — Monetization models, retention strategies, onboarding optimization, growth mechanics, and product metrics frameworks
- Tokens — Design system tokens for Stripe, Linear, and more
- Creative studio — Local-first brand profiles, asset references, character reference profiles, provider-agnostic image/video/3D/audio generation jobs, campaign plans, and transparent creative scoring. Raven does not ship media-provider credentials; set
RAVEN_CREATIVE_RUNNERto route jobs to your own renderer.
Install
Claude Code — one command
claude mcp add raven -- npx -y raven-mcp
Manual config (Claude Desktop or team .mcp.json)
{
"mcpServers": {
"raven": {
"command": "npx",
"args": ["-y", "raven-mcp"]
}
}
}
Claude Desktop — one-click extension
Prefer not to edit JSON? Download raven.mcpb and double-click it. Claude Desktop installs Raven automatically — no Node, no terminal.
From source
git clone https://github.com/rhinocap/raven-mcp.git
cd raven-mcp && npm install && npm run build
Tools
| Tool | Description |
|---|---|
get_principles | Get design principles relevant to a UI context |
get_pattern | Get proven patterns for a specific UI type |
get_business_strategy | Get business/monetization strategies |
evaluate_design | Evaluate a design description against principles |
search_knowledge | Search across all principles, patterns, and strategies |
get_checklist | Get a pre-publish checklist for a UI type |
get_d4d_framework | Get Design for Delight framework templates |
list_design_systems | Browse available design systems |
get_design_system | Get tokens for a specific design system |
compose_system | Mix tokens from different systems |
get_brand_system | Get a full system styled like a well-known brand |
audit_page | Audit HTML/CSS against Raven's quality standards (optional containerMaxWidth makes the container check token-aware) |
audit_layout | Evaluate visual rhythm, alignment, and optical balance |
audit_swiftui | Audit SwiftUI source against Apple HIG — Dynamic Type, semantic colors, 44pt targets, 4/8pt spacing, AccentColor |
audit_ios_screen | Score a rendered iOS screen from an accessibility/view-hierarchy snapshot — 44pt targets + contrast + rhythm, in points |
audit_ios_privacy | Audit Info.plist (or Expo app.json) /PRIVACY.md/entitlements/source — usage-string honesty, ATS, Android permissions, bundled secrets, undisclosed default data-egress |
audit_rn | Audit React Native / Expo source — touchable a11y labels, 44/48pt+hitSlop targets, font scaling, SafeAreaView, dark mode, against iOS HIG + Android Material |
generate_design_system | Generate a custom design system from a brand color |
list_content_systems | Browse brand voice & tone systems (Mailchimp, GOV.UK, Shopify Polaris, Atlassian) |
get_content_system | Get a brand's voice attributes, tone shifts, vocabulary, grammar, and content patterns |
get_content_principles | Get UX-writing principles — clarity, active voice, error anatomy, inclusive language |
get_content_pattern | Get copy recipes for error messages, empty-state copy, notifications, form validation |
get_research_method | Get qualitative, quantitative, or usability research methods with protocols and checklists |
get_metrics_framework | Get a product-metrics framework — HEART, AARRR, North Star, conversion funnel, RICE, OKRs |
get_service_pattern | Get a service design pattern — blueprinting, human handoff, signup-as-service, omnichannel, moments of truth |
get_service_standard | Get the GOV.UK Service Standard — 14 points for evaluating service quality |
generate_service_blueprint | Render a service blueprint as HTML — current state, or current vs. ideal side-by-side |
get_brand_principles | Get brand/visual principles — logo, gradient, imagery, hierarchy, brand-as-system |
get_brand_trends | Get current (2026) brand and visual-design trends with usage guidance |
list_creative_models | Browse provider-agnostic creative model slots for image, video, 3D, audio, character consistency, and analysis |
list_creative_presets | Browse creative presets: product photoshoot, marketplace cards, UGC ads, TV spots, social packs, storyboards, infographics |
create_brand_profile | Create or update a local brand profile for brand-aware creative jobs |
get_brand_profile | Read a local creative brand profile |
list_brand_profiles | List local creative brand profiles |
register_creative_asset | Register a local path or URL as a creative asset reference — no file bytes are uploaded by Raven |
create_character_profile | Create a local character/identity reference profile from registered assets |
create_generation_job | Create a provider-agnostic image, video, audio, 3D, campaign, or analysis job payload; optionally execute via RAVEN_CREATIVE_RUNNER |
get_generation_job | Read a creative generation job and its provider payload/output state |
list_generation_jobs | List local creative generation jobs |
plan_creative_campaign | Plan a multi-asset campaign and optionally create draft generation jobs |
score_creative | Score a prompt/script/concept for hook, benefit clarity, product signal, CTA, channel fit, audience fit, and brand fit |
raven_reflect | Summarize your local Raven usage log to find patterns + gaps |
Creative studio
Raven now covers the creative-production workflow around media generation without copying or depending on any closed vendor. The tools are orchestration primitives:
- Store brand kits locally with
create_brand_profile. - Register product photos, logos, references, or URLs with
register_creative_asset. - Create character/identity reference sets with
create_character_profile. - Generate provider-ready payloads with
create_generation_job. - Build full campaign shot lists with
plan_creative_campaign. - Score creative concepts with
score_creative.
By default, jobs are saved as local draft payloads under ~/.raven/creative (override with RAVEN_CREATIVE_HOME). To run real media generation, set RAVEN_CREATIVE_RUNNER to an executable that reads one job JSON object from stdin and returns JSON on stdout. That runner can call any provider you choose; Raven never stores API keys in source.
iOS / SwiftUI audits
Raven audits native iOS apps against the Apple Human Interface Guidelines, not web/CSS conventions. None of the web-only rules (lang, title, flex-wrap, clamp, max-width, CSS custom properties, bare hex) run on iOS input — and get_checklist/get_principles take platform: "ios" to return HIG items (Dynamic Type, 44pt targets, SF Symbols, safe areas, dark-mode parity, App Review privacy) instead of the web set.
audit_swiftui— paste SwiftUI source (source: a string or array of files). Statically flags hardcoded.font(.system(size:))below ~13pt, tiny semantic fonts (.caption/.caption2), hardcodedColor(red:green:blue:)/hex literals (vs. asset-catalog or semantic system colors), interactive frames under 44×44pt, and ad-hoc spacing off the 4/8-pt grid. Rewards semantic Dynamic Type fonts, semantic system colors, SF Symbols, and flexible frames. Pass the optionalaccent_color_contents(the rawAccentColor.colorset/Contents.json) and it verifies the accent color actually defines components — catching an empty/undefined AccentColor that would silently fall back to system blue.audit_ios_screen— the iOS analog ofaudit_layout. Call with no args for the expected snapshot shape and how to capture it (Accessibility Inspector / XCUITest). Call with{ elements: [{ label, rect, role, fontPt, fgColor, bgColor }], viewport }(plus an optional base64screenshot) to score 44×44pt touch targets, contrast (with iOSsecondaryLabel/tertiaryLabeltreated as platform-standard — a warning, not a hard fail), and visual rhythm (alignment, gap consistency, optical balance).audit_ios_privacy— the "no sketchy issues" gate. Readsinfo_plistor an Expoapp_json(managed RN apps have no Info.plist) plus optionalprivacy_md,entitlements, andsource. FlagsNS*UsageDescriptionstrings that are vague or contradict the code (e.g. anNSHealthUpdateUsageDescriptionwrite claim thatrequestAuthorization(toShare: [])never fulfills), unused entitlements, Android permissions (Expo), ATS cleartext exceptions, secrets/keys shipped in the bundle orapp.jsonextra, and default data-egress paths not disclosed at the point of choice (a pre-selected "Recommended" option that silently sends personal data to a hosted server).
All three return the same shape as audit_page — score, grade, summary, passes, errors, warnings, fix_priority (with audit_ios_screen adding a metrics block).
One command: node scripts/ios-audit.mjs <app-dir> [--snapshot snap.json] [--md report.md] discovers all the inputs and runs all three tools with an aggregated report.
React Native / Expo audits
Anyone building a React Native or Expo app gets the same treatment. RN renders to native iOS + Android widgets, so audit_ios_screen already scores its rendered output (an accessibility snapshot is platform-level); audit_rn covers the JSX/StyleSheet source — the RN analog of audit_swiftui — graded against the iOS HIG + Android Material conventions RN has to satisfy on both platforms. get_checklist/get_principles take platform: "react-native".
audit_rn— paste RN source (source: a string or array). Flags touchables (Pressable/Touchable*) missingaccessibilityLabel/accessibilityRole, touchables under 44pt with nohitSlop,allowFontScaling={false}(silently breaks Dynamic Type),fontSizebelow ~13, screens with noSafeAreaView/useSafeAreaInsets, and — for multi-mode apps — hardcoded colors with nouseColorScheme/Appearance. Passcolor_scheme: "dark"/"light"(your ExpouserInterfaceStyle) and the dark-mode check is suppressed for intentionally single-mode apps. RewardsSafeAreaView,hitSlop,Platform-aware code, and a theme.audit_ios_privacyalso accepts an Expoapp_json— it auditsexpo.ios.infoPlist, Android permissions, plugins, and scansexpo.extra/config for secrets and Google API keys.
One command: node scripts/rn-audit.mjs <app-dir> [--snapshot snap.json] [--md report.md] discovers screens + app.json (reading userInterfaceStyle so dark-only apps aren't false-flagged) and runs everything.
Release updates
Raven ships new principles, patterns, and brand systems regularly. For one email per minor/major release (patches stay quiet):
- Web: ravenmcp.ai/#updates — 10 seconds, one email field.
- In-product: ask Claude "register me for Raven updates at you@work.com" — Claude calls
raven_registerand you're in.
No marketing, unsubscribe anytime. Powered by Resend.
Learning loop
Raven keeps a small local-only log of how you use it so you (and Claude) can spot which patterns you build most often and which gaps show up again and again.
- Location:
~/.raven/usage.jsonl(override withRAVEN_USAGE_LOG=/path). - What's written: tool name, timestamp, elapsed ms, and a tiny insight object — audit score/warning rule names, pattern
type, brand company name, search layer. Never the HTML you audit, never prompt text, never brand copy. - What's never written: raw page bodies, client content, your work product.
- Disable entirely:
RAVEN_NO_USAGE_LOG=1. - Reflect: ask Claude "what have I been using Raven for?" and it will call
raven_reflect, which reads the log locally and summarizes the last N days — most-used tools, recurring audit warnings (likely knowledge gaps), patterns you request most, design systems you reach for.
Nothing is sent to a remote server. If a recurring gap is worth turning into a new Raven principle or pattern, you file an issue by hand — the automated pipeline at github.com/rhinocap/raven-mcp handles it from there.
Development
npm run dev # Run with tsx (hot reload)
npm run build # Compile TypeScript
npm start # Run compiled output
License & attribution
Raven MCP is released under the MIT License — Copyright (c) 2026 Andrew Cunliffe.
If you fork, embed, or redistribute Raven (in whole or in part), retain the MIT license notice and the LICENSE file. If you ship Raven inside another product, include attribution to "Raven MCP — https://ravenmcp.ai" in your acknowledgements.
Raven's knowledge base paraphrases and references work from many third-party sources — Nielsen Norman Group, Laws of UX (CC BY-NC-ND 4.0), Gestalt principles, WCAG (W3C), Mailchimp (CC BY-NC 4.0), GOV.UK (Open Government Licence v3.0), Shopify Polaris, Atlassian Design, and others. Each entry carries a sources URL field. See NOTICE for the full list of upstream sources and license terms; some carry their own conditions beyond MIT.
This is a personal project. It is not endorsed by Intuit Inc. or any other company referenced in its source data.
Data structure
All knowledge lives in src/data/ as static JSON files:
src/data/
principles/ # Nielsen, Laws of UX, Gestalt, accessibility, typography, color, mobile, D4D
patterns/ # signup, pricing, nav, forms, landing, dashboard, modals, empty/error/loading, CTA, social proof, mobile
business/ # monetization, retention, onboarding, growth, metrics
tokens/ # registry.json + systems/ (stripe, linear, vercel, …)
content/ # voice & tone: Mailchimp, GOV.UK, Shopify Polaris, Atlassian
systems/ # registry.json + brand-voice JSONs (Mailchimp, GOV.UK, Polaris, Atlassian)
principles/ # UX-writing principles (clarity, active voice, error anatomy, …)
patterns/ # copy recipes for errors, empty states, notifications, form validation
research/ # study protocols + metrics frameworks
principles/ # research fundamentals (method match, bias, sample size, ethics, triangulation, …)
methods/ # qualitative, quantitative, usability
frameworks/ # HEART, AARRR, North Star, conversion funnel, RICE, OKRs
service-design/ # service-level principles + patterns + frameworks
principles/ # Stickdorn, Shostack, peak-end, moments of truth, handoff
patterns/ # service blueprinting, human handoff, signup-as-service, omnichannel, moments of truth
frameworks/ # GOV.UK Service Standard (14 points)
brand/ # brand & visual design
principles/ # logo, gradient, imagery, hierarchy, brand-as-system
trends/ # 2026-current.json