@coveord/plasma-mcp-server

MCP (Model Context Protocol) server for the Plasma design system. It gives AI agents dynamic access to component, pattern, and content documentation without loading everything upfront.

For installation, client configuration, and guidance on using the Plasma skill with the Plasma and Mantine MCP servers, see the canonical AI Coding Agents guide.

Import invariant: always import from @coveord/plasma-mantine, even when Mantine docs were the reference. @coveord/plasma-mantine re-exports all Mantine components with Coveo's theme applied.

Tools

| Tool | Description | | ------------------------- | --------------------------------------------------------------------------------------------------------- | | list_components | Returns all documented Plasma component names | | get_component_doc | Returns the full Markdown doc for a component (props, sub-components, design guidelines) | | get_component_props | Returns just the props table for a component | | search_docs | Searches component docs, patterns, content guidelines, and foundations; returns the top matching excerpts | | list_patterns | Returns all documented patterns | | get_pattern | Returns the full Markdown doc for a pattern (decision guide, rules, content, accessibility) | | list_content_guidelines | Returns all documented content guidelines | | get_content_guideline | Returns the full Markdown doc for a content guideline (voice, mechanics, vocabulary, audience) | | get_foundations | Returns the design foundations doc (color, typography, spacing, radii, shadows, iconography) |

Example prompts

Once the MCP server is connected, you can ask your AI agent:

"Show me all the available Plasma components."

"Get the documentation for the Button component."

"What props does the Modal component accept?"

"Search the Plasma docs for 'form validation'."

"What are the Plasma spacing and radius tokens?"

"How should I link to the documentation from a Plasma panel?"

How it works

The component, pattern, and content documentation is bundled at build time from @coveord/plasma-llms/dist/ into a dist/data.json file. The MCP server loads this file at startup and serves it via the MCP protocol, with no runtime network calls or file I/O required.

For the underlying static files (useful for tools that fetch URLs directly), see @coveord/plasma-llms.