Skip to main content
Glama
totodev999

shadcn-ui MCP Server

by totodev999

get_component_examples

Retrieve practical code examples for shadcn/ui components to implement UI elements correctly in your projects.

Instructions

Get usage examples for a specific shadcn/ui component

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
componentNameYesName of the shadcn/ui component (e.g., "accordion", "button")

Implementation Reference

  • Main handler function for the get_component_examples tool. It validates the component name, fetches examples using fetchComponentExamples, and returns them in a standardized response format. Handles errors appropriately.
     * Handle the get_component_examples tool request
     */
    private async handleGetComponentExamples(args: any) {
      const componentName = this.validateComponentName(args);
    
      try {
        // Fetch component examples
        const examples = await this.fetchComponentExamples(componentName);
        return this.createSuccessResponse(examples);
      } catch (error) {
        this.handleAxiosError(error, `Component examples for "${componentName}"`);
      }
    }
  • Core helper function that orchestrates fetching examples by scraping the shadcn/ui docs page with cheerio, collecting code blocks, and fetching additional demo from GitHub.
    /**
     * Fetches component examples from documentation and GitHub
     * @param componentName Name of the component
     * @returns Array of component examples
     */
    private async fetchComponentExamples(
      componentName: string
    ): Promise<ComponentExample[]> {
      const response = await this.axiosInstance.get(
        `${this.SHADCN_DOCS_URL}/docs/components/${componentName}`
      );
      const $ = cheerio.load(response.data);
    
      const examples: ComponentExample[] = [];
    
      // Collect examples from different sources
      this.collectGeneralCodeExamples($, examples);
      this.collectSectionExamples($, 'Usage', 'Basic usage example', examples);
      this.collectSectionExamples($, 'Link', 'Link usage example', examples);
      await this.collectGitHubExamples(componentName, examples);
    
      return examples;
    }
  • Helper function to extract general code examples (pre blocks) from the documentation page, associating them with nearby headings for titles.
    /**
     * Collects general code examples from the page
     * @param $ Cheerio instance
     * @param examples Array to add examples to
     */
    private collectGeneralCodeExamples(
      $: cheerio.CheerioAPI,
      examples: ComponentExample[]
    ): void {
      const codeBlocks = $('pre');
      codeBlocks.each((i, el) => {
        const code = $(el).text().trim();
        if (code) {
          // Find heading before code block
          let title = 'Code Example ' + (i + 1);
          let description = 'Code example';
    
          // Look for headings
          let prevElement = $(el).prev();
          while (
            prevElement.length &&
            !prevElement.is('h1') &&
            !prevElement.is('h2') &&
            !prevElement.is('h3')
          ) {
            prevElement = prevElement.prev();
          }
    
          if (prevElement.is('h2') || prevElement.is('h3')) {
            title = prevElement.text().trim();
            description = `${title} example`;
          }
    
          examples.push({
            title,
            code,
            description,
          });
        }
      });
    }
  • Helper to fetch additional demo code example directly from the shadcn/ui GitHub repo raw file.
    private async collectGitHubExamples(
      componentName: string,
      examples: ComponentExample[]
    ): Promise<void> {
      try {
        const githubResponse = await this.axiosInstance.get(
          `${this.SHADCN_RAW_GITHUB_URL}/apps/www/registry/default/example/${componentName}-demo.tsx`
        );
    
        if (githubResponse.status === 200) {
          examples.push({
            title: 'GitHub Demo Example',
            code: githubResponse.data,
          });
        }
      } catch (error) {
        // Continue even if GitHub fetch fails
        console.error(
          `Failed to fetch GitHub example for ${componentName}:`,
          error
        );
      }
    }
  • src/index.ts:133-147 (registration)
    Tool registration in the list_tools response, including name, description, and input schema.
    {
      name: 'get_component_examples',
      description: 'Get usage examples for a specific shadcn/ui component',
      inputSchema: {
        type: 'object',
        properties: {
          componentName: {
            type: 'string',
            description:
              'Name of the shadcn/ui component (e.g., "accordion", "button")',
          },
        },
        required: ['componentName'],
      },
    },
  • Input schema definition for the tool, specifying the required 'componentName' parameter.
    inputSchema: {
      type: 'object',
      properties: {
        componentName: {
          type: 'string',
          description:
            'Name of the shadcn/ui component (e.g., "accordion", "button")',
        },
      },
      required: ['componentName'],

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool retrieves examples but does not describe any behavioral traits such as rate limits, authentication needs, error handling, or the format of returned examples. This leaves significant gaps in understanding how the tool operates beyond its basic purpose.

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

Conciseness5/5

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

The description is a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It is front-loaded and appropriately sized for a simple tool, making it easy for an agent to parse and understand quickly.

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

Completeness3/5

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

Given the tool's low complexity (one parameter, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose but lacks details on behavioral aspects and usage guidelines, which are important for effective tool invocation. Without annotations or output schema, more context in the description would be beneficial.

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

Parameters3/5

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

The schema description coverage is 100%, with the parameter 'componentName' clearly documented in the input schema. The description adds minimal value beyond this, as it only reiterates the need for a component name without providing additional context like valid examples or constraints. This meets the baseline for high schema coverage.

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

Purpose4/5

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

The description clearly states the tool's purpose with a specific verb ('Get') and resource ('usage examples for a specific shadcn/ui component'), making it immediately understandable. However, it does not explicitly differentiate from sibling tools like 'get_component_details' or 'search_components', which might also provide example-related information, so it falls short of a perfect score.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like 'get_component_details' or 'search_components'. It implies usage for retrieving examples but offers no context on prerequisites, exclusions, or specific scenarios, leaving the agent to infer usage based on the tool name alone.

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