@stampui/mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| STAMPUI_TOKEN | No | Commercial license key; only needed for pro blocks | |
| STAMPUI_REGISTRY_URL | No | Registry origin, useful for testing | https://stampui.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_blocksA | List StampUI blocks. Optionally filter by category, tier (free|pro) or framework. Returns slug, title, description, tier and tags for each. |
| 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'. |
| 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). |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.