All servers / Design / ONEM RVA Design System MCP server
ONEM RVA Design System MCP server
Centralized MCP server for ONEM/RVA Design System with stdio and HTTP transport support
Tested by ConnectATDScore 86 out of 100. Tested 2026-11-18 on package version 2.9.5. Package: @onemrvapublic/design-system-mcp-server · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Package safety | 16 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (4.2 seconds including download)
- Tools offered: 38
- Last published: 2026-11-17
- Weekly downloads (npm): 1,690
- License: none listed · Direct dependencies: 5
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
help_friendno parametersStart here when intent is unclear. Returns a grouped MCP tool catalog plus a recommended call sequence so AI can choose the next best tool with less trial-and-error.
list_components1 of 1 parameter describedList all available design system components with their categories and descriptions. Optionally filter by category (mat-*, page-*, layout-*).
get_component1 of 1 parameter describedGet detailed information about a specific component including its API (inputs, outputs), usage examples, and accessibility notes.
search_components1 of 1 parameter describedUse first for keyword-driven discovery across all synced datasets (components, Figma, tokens, styles, icons, JSON Forms, theme). Best tool when the user does not know exact component names.
generate_component_usage2 of 2 parameters describedGenerate a complete code example showing how to use a specific component with proper imports and common configuration.
get_component_props1 of 1 parameter describedGet a detailed list of all inputs, outputs, and methods for a component with their types and descriptions.
get_accessibility_info1 of 1 parameter describedGet accessibility information and WCAG compliance notes for a component, including common accessibility patterns and testing results.
list_jsonforms_renderersno parametersList all available JSON Forms custom renderers for form controls like checkbox, datepicker, phone, IBAN, etc.
get_jsonforms_renderer1 of 1 parameter describedGet detailed information about a specific JSON Forms renderer including its inputs and tester function.
list_theme_utilities1 of 1 parameter describedList all available theme utilities including SCSS variables, CSS custom properties (design tokens), color palettes, spacing scales, mixins, and breakpoints.
get_theme_utility1 of 1 parameter describedGet detailed information about a specific theme utility (variable, palette, or mixin).
list_icons3 of 3 parameters describedList DS icons synced from Figma in a human-readable table with icon name, key, description, and link. Use before writing icon usage code to avoid wrong icon names.
get_sync_statusno parametersGet MCP sync health and freshness for Figma + codebase data, including last sync times and error summaries.
list_figma_components5 of 5 parameters describedList components synced from Nemo Figma with page, mapping, and variant counts. Supports filters for page, status, and mapped-only.
get_spacing_spec1 of 1 parameter describedThe padding, gap, direction and alignment of one or many components, in a compact form, in a single call. Use this when checking or correcting the spacing of a page against its design: it is far cheaper than calling get_figma_component per component. Accepts names, node ids or pasted Figma URLs.
get_figma_component1 of 1 parameter describedGet detailed info for one synced Figma component: mapping, properties, variants, tokens used, the Figma link, and the anatomy tree with padding, gap and layout per layer. Accepts a component name, a node id, or a pasted Figma frame URL. For spacing across several components prefer get_spacing_spec, which is far cheaper.
list_design_tokens4 of 4 parameters describedList design tokens from synced Figma variables when available, with safe fallback guidance to codebase theme utilities.
get_design_token1 of 1 parameter describedGet full details for a single design token by name: hex value, CSS custom property or Sass map usage, section context, and which Figma components reference this token.
explain_token_diff2 of 2 parameters describedExplain differences between two design tokens including value comparison, role context, and Figma-derived descriptions.
list_figma_styles1 of 1 parameter describedList synced Figma styles (TEXT, FILL, EFFECT, GRID) with resolved values when available.
suggest_component1 of 1 parameter describedDescribe what UI behaviour or pattern you need in plain English and get the top DS component suggestions with use-case guidance, code snippets, and Figma links. Ideal when you do not know which component to use.
audit_component1 of 1 parameter describedRun a quality/completeness audit on a DS component and get a scored report (0–100) covering documentation coverage, input/output typing, accessibility notes, Figma mapping, standalone status, and more.
compare_components2 of 2 parameters describedCompare two DS components side by side: inputs, outputs, accessibility features, Figma mappings, and use-case guidance. Useful when choosing between similar components.
get_color_palette1 of 1 parameter describedBrowse the DS color palette from synced Figma tokens. For each tone shows the hex value, CSS custom property, and WCAG contrast ratios against white and black (AA/AAA grades). Filter by role (e.g. "primary", "neutral").
migrate_to_ds6 of 6 parameters describedSingle-file migration analyzer. Returns a complete plan: setup prerequisites (npm install + provider + theme class), DS replacement mapping, ready-to-paste snippets, imports to ADD/REMOVE from @Component imports[], TypeScript handler/subscription rewrites, and SCSS hints. Two equivalent input shapes — pick whichever feels natural: { code, ts_code, scss_code } OR { html, typescript, scss }. The HTML/code field is required; the others are optional.
migrate_file2 of 2 parameters describedOne-call migration. Takes ANY file from an Angular component triple (foo.component.ts / .html / .scss / .css) and auto-resolves the sibling files before running migrate_to_ds. Saves 3-4 read roundtrips per file. Use this when migrating a known component file; use `migrate_to_ds` directly when you only have inline snippets.
analyze_repo_migration5 of 5 parameters describedUse first for repo-scale migration and quality checks. Reports Material/custom patterns to migrate, DS misuse (missing required inputs, deprecated components), and a file-by-file Copilot fix-pack.
rescan_componentsno parameters[Admin] Re-scan all design system source files and reload component metadata. Use after code changes have been deployed.
get_release_notes2 of 2 parameters describedShow the design system release notes, most recent first (5 per page). Each entry explains exactly what shipped: affected entry points plus the style values, config values, ARIA attributes and public members its diff changed. Pass `version` for a single release, or `page` to go back in time.
angular_migration_guide1 of 1 parameter describedGuide upgrading a project to the Angular version the design system targets. Read `@angular/core` from the project's package.json and pass it as `currentAngularVersion`; returns the ng update path, the official update guide, and the DS compatibility.
lint_ds_usage2 of 2 parameters describedLint an Angular template that uses the design system and report usage bugs before the compiler does: missing required inputs, unknown inputs/outputs (with did-you-mean), invalid enum values, leftover Angular Material, and unknown DS selectors.
review_implementation3 of 3 parameters describedQuality gate for code you just wrote or changed. Reports custom CSS that a spacing utility class already covers, hard-coded px and hex values, stylesheets that restyle design system internals or pierce encapsulation, inline style attributes, and templates that have grown into a monolith. Run it after implement_figma_design, alongside lint_ds_usage.
generate_form3 of 3 parameters describedScaffold a complete design system form from a field spec. Default JSON Forms mode emits schema + uischema + the renderers to register; reactive mode emits a FormGroup + template. Routing to iban/phone/ssin/date/select renderers is handled automatically.
get_started2 of 2 parameters describedZero-to-first-component quickstart: required Angular version, install command, the correct import for a first component, and a working snippet. Ideal when integrating the design system into a new or existing project.
explain_component1 of 1 parameter describedPlain-language explanation of one component: what it is, when to use it, its required inputs, whether a demo exists, and which sibling components to consider instead. Great for choosing the right component.
ds_upgrade_guide2 of 2 parameters describedOne-call guide to upgrade a project stuck on an older design system: the Angular upgrade path to the DS target, the DS package bump, breaking changes pulled from the release notes since the project version, and a pointer to lint_ds_usage to catch broken component usage.
ds_install3 of 3 parameters describedRepo-aware install & configuration plan the AI agent should APPLY DIRECTLY (run the commands, make the file edits), not just print. Pass the project's package.json (and optionally angular.json). Returns an ordered action plan: the Angular-matched install command pinned to a published dist-tag (never a bare @latest), the required peer-dependency install command, the SCSS theme setup, the app.config providers, the index.html theme class, and a confirmation page that renders real DS components. Fonts and Material Icons load automatically from the internal CDN via the theme (corporate network required).
implement_figma_design3 of 3 parameters describedCall this FIRST, before any other tool and before writing code, whenever the user pastes a figma.com link, a frame, a mockup or a screenshot. It does not matter whether they say what to do with it: a bare Figma link on its own is enough. Triggers on messages like "Implement this design from Figma <link>", "build this screen", "recreate this page", or a message that is only a Figma URL. Returns the workflow to follow: how to read the frame, how to map every layer to a nemo Design System component, which tools to call in which order, and the rules (no raw Angular Material, no hard-coded colours or spacing, lint the result). Follow the returned steps instead of improvising.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.