stackzero-labs/mcp
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@stackzero-labs/mcp show me available UI components for a dashboard"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Overview
This package allows you to run a model context server for stackzero-labs/ui components, enabling you to use the MCP protocol with your applications.
Related MCP server: MCP Tool
1-click install in Cursor
Installation
npm install @stackzero-labs/mcpUsage
As a standalone server
npx @stackzero-labs/mcpIn Claude Desktop
Add to your Claude Desktop configuration:
{
"mcpServers": {
"@stackzero-labs/mcp": {
"command": "npx",
"args": ["-y", "@stackzero-labs/mcp@latest"]
}
}
}In Cursor (manual setup)
Go to Cursor settings, select MCP. Add to your Cursor configuration:
{
"mcpServers": {
"@stackzero-labs/mcp": {
"command": "npx",
"args": ["-y", "@stackzero-labs/mcp@latest"]
}
}
}Development
# Install dependencies
pnpm install
# Build the project
pnpm build
# Run in development mode
pnpm dev
# Inspect the MCP server
pnpm inspectLicense
See LICENSE for details.
Available Tools
12 toolsgetAddressesC
Provides implementation details for address-01-block, address-02-block blocks.
Inputs: no named parameters.
getBannersC
Provides implementation details for banner-01-block, banner-02-block, banner-03-block, banner-04-block, banner-05-block, banner-06-block, banner-07-block, banner-08-block, banner-09-block, banner-10-block, banner-11-block, banner-12-block blocks.
Inputs: no named parameters.
getCartsC
Provides implementation details for cart-01-block blocks.
Inputs: no named parameters.
getImagesB
Provides implementation details for image-viewer-basic, image-viewer-motion, image-carousel-basic components.
Inputs: no named parameters.
getInputsB
Provides implementation details for input-icon, phone-number-input-basic components.
Inputs: no named parameters.
getProductCardsC
Provides implementation details for product-card-01-block, product-card-02-block, product-card-03-block, product-card-04-block, product-card-05-block, product-card-06-block, product-card-07-block, product-card-08-block, product-card-09-block, product-card-10-block, product-card-11-block, product-card-12-block, product-card-13-block blocks.
Inputs: no named parameters.
getProductsD
Provides implementation details for price-format-basic, price-format-sale, quantity-input-basic, variant-color-selector-basic, variant-selector-basic, variant-selector-images, variant-selector-multiple components.
Inputs: no named parameters.
getProductVariantsD
Provides implementation details for product-variant-01-block, product-variant-02-block, product-variant-03-block, product-variant-04-block, product-variant-05-block blocks.
Inputs: no named parameters.
getRatingsC
Provides implementation details for star-rating-basic, star-rating-fractions, upvote-rating-basic, upvote-rating-animated, face-rating-basic, face-rating-gradient components.
Inputs: no named parameters.
getReviewsC
Provides implementation details for review-01-block, review-02-block, review-03-block, review-04-block, review-05-block, review-06-block, review-07-block, review-08-block, review-09-block, review-10-block blocks.
Inputs: no named parameters.
getUIBlocksA
Provides a comprehensive list of all stackzero-labs/ui blocks.
Inputs: no named parameters.
getUIComponentsA
Provides a comprehensive list of all stackzero-labs/ui components.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 12 tools
Each tool targets a distinct UI element (addresses, banners, carts, etc.) with no overlap. Descriptions clearly differentiate them.
All tools follow a consistent 'get' + plural noun pattern (e.g., getAddresses, getBanners), with no mixing of conventions.
12 tools is appropriate for a UI component library, covering major element types without being excessive or sparse.
The set covers a wide range of UI elements and includes aggregate tools for all blocks/components. Minor potential gaps exist (e.g., missing modals or forms) but overall coverage is strong.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
A Model Context Protocol server for Wix AI tools
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
Shared memory MCP server for Claude Code, Codex, Gemini CLI and Cursor. Cited, editable.
Related MCP Servers
- AlicenseCqualityCmaintenanceA Model Context Protocol server that enables AI agents to generate, fetch, and manage UI components through natural language interactions.349 npm7ISC
- AlicenseDqualityDmaintenanceA server built on mcp-framework that enables integration with Claude Desktop through the Model Context Protocol.11MIT
- AlicenseBqualityDmaintenanceA Model Context Protocol server that enables seamless integration between Claude AI and development tools like VSCode, Augment, Vercel, Airtable, and Square.7MIT
- AlicenseNot gradedqualityDmaintenanceA cross-platform desktop application that runs a Model Context Protocol server, allowing AI applications like Claude Desktop to easily connect without requiring npx or Node.js installation.1,399 npm1MIT