Skip to main content
Glama
CarbonoDev

TailwindCSS MCP Server

by CarbonoDev

install_tailwind

Generate installation commands and configuration files for TailwindCSS in various frameworks like React, Next.js, Vue, and Angular. Specify your framework and package manager to get customized setup instructions.

Instructions

Generate installation commands and configuration files for TailwindCSS in different frameworks

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
frameworkYesTarget framework (e.g., 'react', 'nextjs', 'vue', 'vite', 'laravel', 'angular', 'svelte')
packageManagerNoPackage manager to use (default: npm)
includeTypescriptNoInclude TypeScript configuration (default: false)

Implementation Reference

  • The main handler function that orchestrates the TailwindCSS installation guide generation.
    private async handleInstallTailwind(args: any): Promise<any> {
      try {
        const params = this.validateInstallTailwindParams(args);
        const guide = await this.installationService.generateInstallationGuide(params);
        return this.createSuccessResponse(guide);
      } catch (error) {
        this.handleServiceError(error, "Failed to generate TailwindCSS installation guide");
      }
    }
  • src/index.ts:176-185 (registration)
    Tool registration definition for "install_tailwind" in the MCP server.
    name: "install_tailwind",
    description: "Generate installation commands and configuration files for TailwindCSS in different frameworks",
    inputSchema: {
      type: "object",
      properties: {
        framework: {
          type: "string",
          description: "Target framework (e.g., 'react', 'nextjs', 'vue', 'vite', 'laravel', 'angular', 'svelte')",
        },
        packageManager: {
  • Type definition for the input parameters of the "install_tailwind" tool.
    export interface InstallTailwindParams {
      framework: string;
      packageManager?: "npm" | "yarn" | "pnpm" | "bun";
      includeTypescript?: boolean;
    }
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool generates commands and files but doesn't clarify if this is a read-only operation, whether it modifies existing files, what permissions are needed, or what the output format looks like (e.g., text commands vs. file creation). For a tool that implies file system interaction, this lack of detail is a significant gap.

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 front-loads the core purpose without unnecessary words. It directly states what the tool does ('Generate installation commands and configuration files') and the scope ('for TailwindCSS in different frameworks'), earning its place with zero waste. This is appropriately sized for the tool's complexity.

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

Completeness2/5

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

Given the tool's moderate complexity (3 parameters, no output schema, no annotations), the description is incomplete. It lacks behavioral context (e.g., file system impact, output format), usage guidelines, and any mention of return values or errors. While the schema covers parameters well, the description fails to address broader operational aspects, leaving gaps for an agent to invoke it correctly.

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 input schema has 100% description coverage, clearly documenting all parameters (framework, packageManager, includeTypescript) with enums and defaults. The description adds no additional parameter semantics beyond what the schema provides, such as explaining framework-specific nuances or TypeScript integration details. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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: 'Generate installation commands and configuration files for TailwindCSS in different frameworks.' It specifies the verb ('Generate') and resource ('installation commands and configuration files'), and distinguishes from siblings like 'convert_css_to_tailwind' or 'search_tailwind_docs' by focusing on setup rather than conversion or documentation. However, it doesn't explicitly differentiate from 'get_tailwind_config_guide', which might overlap in providing configuration guidance.

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. It doesn't mention prerequisites (e.g., needing a project initialized), exclusions (e.g., not for existing Tailwind setups), or comparisons to siblings like 'get_tailwind_config_guide' for configuration help. The agent must infer usage from the purpose alone, which is insufficient for clear decision-making.

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

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/CarbonoDev/tailwindcss-mcp-server'

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