All servers / Design / Baseline UI MCP server
Baseline UI MCP server
MCP server for Baseline UI design system documentation
Tested by ConnectATDScore 78 out of 100. Tested 2026-11-19 on package version 3.12.0. Package: @baseline-ui/mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 12 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (2.9 seconds including download)
- Tools offered: 4
- Last published: 2026-11-13
- Weekly downloads (npm): 891
- License: MIT · Direct dependencies: 2
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.
get_component_info0 of 1 parameter describedDetailed documentation, props, and story IDs for any Baseline UI component. This resource provides comprehensive component specifications and usage examples. ## Response Structure The response is a JSON object containing: - **id**: Storybook component ID (e.g., "core-buttons-actionbutton") - **breadcrumb**: Storybook docs path (e.g., "Core/Buttons/ActionButton"); omitted when the component has no docs page - **importStatement**: Import lines copied from the component's stories; they can include story helpers or omit the component - **documentation**: Markdown documentation, or null when the component has no docs page - **props**: A single TypeScript interface string, not a JSON array, with descriptions and defaults in its doc comments; empty when no prop types could be extracted - **stories**: An object with: - **usage**: Array of stories, each with: - **id**: Story ID (can be used with get_story_url) - **name**: Human-readable name of the story - **snippet**: Source of the story; absent when `error` is set - **description**: What this story demonstrates, when it has a description - **warning**: Why the snippet may be incomplete, when it is - **error**: An object with `name` and `message` saying why no snippet could be extracted, when none could - **implementation**: A single string with the source of the component's shared example components; empty when it has none ## Usage Use this resource to: - Understand all available props and their types for a component - Check required vs optional props - Read default values and usage examples - Find interactive stories to see components in action - Verify accessibility features and behavior ## Import Format Components are imported from `@baseline-ui/core`, and chart components from `@baseline-ui/charts`: ```tsx import { ComponentName } from "@baseline-ui/core"; import { ChartName } from "@baseline-ui/charts"; ```
get_story_url0 of 1 parameter describedGenerate a live demo URL for a Baseline UI story. Use a story ID from the Storybook index; the component info tool lists them for each component. The response is the URL, or an error result with suggestions when the story id is unknown. You can use this URL to understand the structure of the component and how to customize it.
get_figma_url0 of 1 parameter describedGet the Figma URL for a given component. The response is the URL, or an error result when the component has no linked Figma design. You can use this URL to understand the structure of the component and how it looks. The actual component's HTML structure might be slightly different from the Figma design but the overall structure and design should be the same including the design tokens.
list_available_resourcesno parametersList all 8 available resources in the Baseline UI MCP server with their descriptions and URIs. Use this tool to discover what information and documentation is available. ## Available Resources The Baseline UI MCP server includes: 1. **list_components** - Complete list of all components with descriptions and similar suggestions 2. **list_icons** - The full icon catalog organized by size (8, 12, 16, 20, 24, 36) 3. **getting_started** - Installation, setup, and basic usage guide 4. **theming** - Custom themes, color schemes, and theme implementation 5. **styling** - Styling patterns, sprinkles usage, and design tokens 6. **guidelines** - Best practices, accessibility, and component usage conventions 7. **internationalization** - Multi-language support and localization 8. **nutrient_web_viewer_theming** - Specialized theming for Nutrient Web Viewer SDK ## Response Structure Returns a JSON array of resources, each containing: - **name**: Resource identifier (e.g., "list_components", "guidelines") - **uri**: The resource URI for accessing the resource - **description**: What the resource provides - **mimeType**: Content type (typically "text/markdown") ## Usage Use this tool to: - Discover all 8 available documentation and resources - Understand what each resource provides before accessing it - Get the correct URI for reading a specific resource - Build dynamic interfaces that need to know available resources ## Workflow Recommendations - Start with **guidelines** for best practices and overall approach - Use **getting_started** to understand installation and setup - Consult **list_components** to find the right component for your needs - Reference **theming** for custom design systems - Check **styling** for CSS and design token guidance
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.