@stampui/mcp
OfficialClick 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., "@@stampui/mcp add an FAQ section block"
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.
@stampui/mcp
MCP (Model Context Protocol) server for StampUI. Lets an AI coding agent browse the StampUI block registry and stamp blocks into a project as real .tsx source files, without leaving the editor: "add an FAQ section" becomes search, inspect, install.
Tools
Tool | What it does |
| List blocks, filter by |
| Free-text search across slug, title, description, tags |
| Full manifest, install command, docs link, and source (free blocks) or an unlock note (pro blocks) |
| Write a block's files into the project at an absolute |
The registry data and free block sources come from the MIT @stampui/blocks package; the manifest format is documented in the open block manifest spec.
Related MCP server: @kongyo2/npm-info-mcp-server
Setup
Claude Code
claude mcp add stampui -- npx -y @stampui/mcpClaude Desktop
Add to claude_desktop_config.json (Settings > Developer > Edit Config):
{
"mcpServers": {
"stampui": {
"command": "npx",
"args": ["-y", "@stampui/mcp"]
}
}
}Cursor and other MCP clients
Add the same entry to the client's MCP config (e.g. ~/.cursor/mcp.json):
{
"mcpServers": {
"stampui": {
"command": "npx",
"args": ["-y", "@stampui/mcp"]
}
}
}Free vs pro
Everything needed for free blocks works offline and without an account: sources ship inside @stampui/blocks.
Pro blocks are part of the commercial StampUI catalog. Their source is not in this package or any public repo. With a license key, set it in the server's environment and pro sources are fetched from the licensed registry per request:
claude mcp add stampui --env STAMPUI_TOKEN=SU_LIVE_-XXXX -- npx -y @stampui/mcpWithout a token, pro blocks still appear in listings and get_block explains how to unlock them; the server never attempts to bypass licensing, and PRs adding such behavior will be closed.
Environment variables
Variable | Meaning | Default |
| Commercial license key; only needed for pro blocks | unset |
| Registry origin, useful for testing |
|
Security notes
The server runs locally over stdio; it makes network requests only for pro block fetches, over HTTPS to the registry.
stamp_blockwrites files. It requires an absolutetargetDirand refuses paths that resolve outside it. Review what your agent installs like any other code it writes; MCP clients ask for permission before tool calls by default, keep that on forstamp_block.Your license key is read from the environment and sent only in the
Authorizationheader to the registry. Never paste it into chat.Report vulnerabilities per SECURITY.md.
Development
git clone https://github.com/StampUI/mcp
cd mcp
npm install
npm run build
npm test # stdio smoke test (initialize, tools/list, search_blocks)
# exercise it with the MCP inspector:
npx @modelcontextprotocol/inspector node dist/index.jsLinks
StampUI: https://stampui.com
Free component source: https://github.com/StampUI/ui
Changelog: CHANGELOG.md
License
MIT for this server. Free blocks it delivers are MIT via @stampui/blocks; pro blocks are covered by the StampUI commercial license.
Available Tools
4 toolsget_blockA
Get full details for one block: manifest, install command, dependencies, and the source code (free blocks) or how to unlock it (pro blocks).
Inputs: slug (required).
list_blocksA
List StampUI blocks. Optionally filter by category, tier (free|pro) or framework. Returns slug, title, description, tier and tags for each.
Inputs: tier, category, framework.
search_blocksA
Search StampUI blocks by free text across slug, title, description and tags. Use this to find a block for a need, e.g. 'billing', 'data table', 'login'.
Inputs: query (required).
stamp_blockA
Write a block's source files into the user's project. Provide the slug and a target directory (absolute, e.g. the repo root). Free blocks work offline; pro blocks need STAMPUI_TOKEN.
Inputs: slug (required), targetDir (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a distinct purpose: get_block retrieves details of one block, list_blocks lists multiple blocks, search_blocks searches by text, and stamp_block writes files. No overlap.
All tool names follow a consistent verb_noun pattern in snake_case: get_block, list_blocks, search_blocks, stamp_block. Perfectly predictable.
Four tools is an appropriate size for a block management server, covering core operations without being too few or too many.
The server covers the main use cases: retrieving, listing, searching, and installing blocks. Minor missing operations like removing or updating installed blocks are not critical for this domain.
Maintenance
Related MCP Connectors
Search and install 4,000+ security-scanned MCP servers from inside any MCP-aware AI client.
An MCP server that gives your AI access to the source code and docs of all public github repos
Search a directory of 70K+ AI building blocks: MCP servers, agents, models, datasets, prompts.
MCP server that lets your AI assistant build and deploy apps, hosting each one at a live URL.
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server that lets AI agents search the substreams.dev package registry.1MIT
- AlicenseAqualityFmaintenanceMCP server that provides npm package information for AI agents during TypeScript development.79 npm1MIT
- AlicenseNot gradedqualityDmaintenanceThis MCP server provides tools to install and manage shadcn/ui components directly from AI coding agents.2MIT
- AlicenseAqualityCmaintenanceMCP server for Shadcn Dashboard that enables AI to discover, search, and install UI blocks directly into projects without copy-paste.628 npmMIT