Releases
v0.1.2
The bundled documentation is regenerated from the current repo, with no change to the tools. This is the first release made by the publishing workflow, through npm trusted publishing.
Changed
get_doc,get_component,list_componentsandsearch_docsdescribe the components added to the design system since 0.1.1:NavTree,NavGroupandNavLink;Sidebaras a navigation rail (layout="stacked",stackedWidthandpanel); atonalTabsvariant; and nine new icons.- The six tools, their inputs and their output are unchanged.
v0.1.1
Serves the design system 2.0 documentation, and a code-quality fix with no change to the tools. (#7)
Changed
-
Renamed to
@soroush.design/mcp(it was@soroush.tech/mcp), and the hosted server is athttps://mcp.soroush.design/mcp. Run it withnpx -y @soroush.design/mcp. The tools, their inputs and their output are unchanged; the old package is deprecated in favour of this one. -
The bundled content is regenerated from the current repo, so
get_doc,get_componentandsearch_docsdescribe design-system 2.0 and styled-system 6.0: the frame-onlylayoutprop, columns onGridwithgapas the gutter,span="full",LayoutProvider, the "Layout: one way per intent" table, andinstallPopover()on@soroush.tech/design-system/testing. -
The tool handlers are plain functions rather than
asyncones that awaited nothing. The six tools, their inputs and their output are unchanged.
v0.1.0
First release. An MCP server that gives AI coding tools first-class access to the design system: the component inventory, every component README, and the theme token contract, all generated from this repo's own sources at build time.
Added
-
Six tools:
list_components,get_component,get_tokens,list_docs,get_doc, andsearch_docs.get_componentserves a component's README, optionally sliced intointro,api(its props with token values and defaults), orexamples. -
Two transports from one implementation. Run it locally over stdio with
npx -y @soroush.tech/mcp, or connect to the hosted server:claude mcp add --transport http soroush https://mcp.soroush.tech/mcp -
Content generated from the repo rather than hand-maintained: component READMEs come from
packages/*/src/*/README.mdthrough the same registry and splitter the docs site uses, and the token contract is serialized from the livebaseTheme, so a new scale appears with no extra step.