Skip to main content
Glama
@stampui/mcp

@stampui/mcp

Official
by StampUI

@stampui/mcp

npm CI license

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.

Related MCP server: @kongyo2/npm-info-mcp-server

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_block writes files. It requires an absolute targetDir and 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 for stamp_block.

  • Your license key is read from the environment and sent only in the Authorization header 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

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 tools
get_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

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case: get_block, list_blocks, search_blocks, stamp_block. Perfectly predictable.

    Tool Count5/5

    Four tools is an appropriate size for a block management server, covering core operations without being too few or too many.

    Completeness4/5

    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

    ActivityMaintained
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers