Skip to main content
Glama
heilgar

Shadcn UI MCP Server

by heilgar

install-blocks

Install Shadcn UI components and blocks directly using your preferred runtime (npm, pnpm, yarn, bun) with this tool from the Shadcn UI MCP Server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
blockYesName of the block to install
runtimeNoUser runtime (npm, pnpm, yarn, bun)

Implementation Reference

  • The main execution logic for the 'install-blocks' tool: validates input, retrieves block data, selects installation command based on runtime or defaults to npm, and returns the command.
    export const installBlock = async ({block, runtime}: {block: string, runtime?: string}) => {
        try {
            if (runtime && !validateRuntime(runtime)) {
                return createResponse(`Invalid runtime: ${runtime}. Must be one of: npm, pnpm, yarn, bun`, true);
            }
            const { blockData, error } = await getBlockData(block);
            if (error) return createResponse(error, true);
            if (!blockData) return createResponse("Unexpected error: block data missing", true);
    
            if (!blockData.commands?.[0]) {
                return createResponse(`No installation command found for block '${block}'`, true);
            }
            const commands = blockData.commands[0];
            const selectedRuntime = runtime as PackageManager | undefined;
            const command = selectedRuntime ? commands[selectedRuntime] : commands.npm;
            if (!command) {
                return createResponse(`No installation command found for runtime '${runtime}'`, true);
            }
            return createResponse(command);
        } catch (error) {
            return handleError(error, "Error generating installation command");
        }
    }
  • Zod schema defining the input parameters for the 'install-blocks' tool: required 'block' string and optional 'runtime' string.
    toolSchema: {
        block: z.string().describe("Name of the block to install"),
        runtime: z.string().describe("User runtime (npm, pnpm, yarn, bun)").optional()
    },
  • src/index.ts:54-65 (registration)
    Tool definition and registration entry in toolDefinitions object, used for MCP capabilities and server.tool registration. Includes description, JSON parameters schema, Zod toolSchema, and handler reference.
    "install-blocks": {
        description: "Install a shadcn/ui block",
        parameters: {
            block: { type: "string", description: "Name of the block to install" },
            runtime: { type: "string", description: "User runtime (npm, pnpm, yarn, bun)", optional: true }
        },
        toolSchema: {
            block: z.string().describe("Name of the block to install"),
            runtime: z.string().describe("User runtime (npm, pnpm, yarn, bun)").optional()
        },
        handler: installBlock
    },
  • Supporting helper function used by installBlock to retrieve or fetch block data from cache.
    async function getBlockData(block: string) {
        if (!block) {
            return { error: "Block name is required" };
        }
        let blockData = resourceCache.get(block);
        if (!blockData) {
            await fetchAndCacheBlocks();
            blockData = resourceCache.get(block);
        }
        if (!blockData) {
            return { error: `Block '${block}' not found. Use list-blocks to see available blocks.` };
        }
        return { blockData };
    }
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/heilgar/shadcn-ui-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server