StampUI MCP server
Commit Nov 6, 2026Allows AI coding agents to browse the StampUI block registry and install UI components directly into a project as .tsx source files.
Also known as StampUI/mcp
- Stars
- 1
- Tools
- 4
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Nov 6, 2026
- License
- MIT
What is StampUI MCP?
StampUI allows AI coding agents to browse the StampUI block registry and install UI components directly into a project as .tsx source files. It exposes 4 tools, such as list_blocks, search_blocks, get_block.
Summary generated from the project's README
About StampUI MCP server
Installing UI components directly into your codebase from an AI coding agent is what this server enables. Developers using Claude Code, Claude Desktop, or Cursor can browse the StampUI block registry and instantly convert a request like adding an FAQ section into a search, inspection, and installation workflow. The server provides tools to list blocks by category, tier, or framework, perform free-text searches, and retrieve detailed manifests for specific components.
Users can install components as actual .tsx source files into a specific target directory. While free blocks work offline using the @stampui/blocks package, accessing pro blocks requires a commercial license key provided via the STAMPUI_TOKEN environment variable. The server operates locally over stdio and maintains security by refusing to write files outside of the designated absolute target directory.
What you can do with it
- 1Browse available UI componentsAsk your AI agent to find specific UI elements filtered by their tier or framework.
- 2Search for specific design patternsUse natural language to find blocks based on their descriptions or tags.
- 3Access premium UI blocksRetrieve source code for commercial components using a valid license key.
Written from the project's README. Every use case is checked against a quote from it.
StampUI MCP tools 4
Detected from the READMElist_blockssearch_blocksget_blockstamp_block
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablestampui/mcp is public and reachablegithub.com/stampui/mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-06github.com/stampui/mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model4 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHub@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 |
List blocks, filter by category, tier (free/pro), or framework |
search_blocks |
Free-text search across slug, title, description, tags |
get_block |
Full manifest, install command, docs link, and source (free blocks) or an unlock note (pro blocks) |
stamp_block |
Write a block's files into the project at an absolute targetDir |
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.
Setup
Claude Code
claude mcp add stampui -- npx -y @stampui/mcp
Claude 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/mcp
Without 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 |
|---|---|---|
STAMPUI_TOKEN |
Commercial license key; only needed for pro blocks | unset |
STAMPUI_REGISTRY_URL |
Registry origin, useful for testing | https://stampui.com |
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.js
Links
- StampUI: https://stampui.com
- Free component source: https://github.com/StampUI/ui
- CLI: https://github.com/StampUI/cli
- 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.
StampUI MCP questions
What tools does StampUI MCP provide?
It exposes 4 tools, including list_blocks, search_blocks, get_block, stamp_block.
How do I install pro blocks?
Pro blocks require a commercial license key provided via the STAMPUI_TOKEN environment variable to fetch sources from the licensed registry.
Is it safe to let the server write files to my project?
The stamp_block tool requires an absolute target directory and refuses any paths outside of it; you should also keep MCP client permission prompts enabled.