# Tailwind To Stylex — REST API endpoint `tailwind-to-stylex`

Convert Tailwind CSS v4 theme variables, JSON design tokens, or a static Tailwind config theme into StyleX defineConsts source and TypeScript declarations. Uploaded JavaScript is parsed as data and never executed.

- Category: developer
- MCP server: https://mcp.findutils.com/ (Streamable HTTP, no API keys, 120 req/min per IP)
- REST endpoint: POST https://api.findutils.com/api/tools/tailwind-to-stylex/execute (no API keys, 60 req/min per IP)
- Reference page: https://findutils.com/api/tailwind-to-stylex/
- Same tool on the other surface: https://findutils.com/mcp/tailwind-to-stylex/

## Call the endpoint (verified example)

```bash
curl -X POST https://api.findutils.com/api/tools/tailwind-to-stylex/execute \
  -H "Content-Type: application/json" \
  -d '{
    "source": "@theme { --color-brand-500: #3366ff; --spacing: 0.25rem; }"
  }'

# Parameter schema
curl https://api.findutils.com/api/tools/tailwind-to-stylex
```

## Input schema

| Argument | Type | Required | Description |
|---|---|---|---|
| `source` | string | yes | Tailwind @theme CSS, CSS custom properties, JSON tokens, or a static Tailwind theme object. |
| `format` | string (auto \| css \| json \| config) | no | Input format: auto, css, json, or config. Default: auto. Default: `"auto"`. |

Example arguments (verified):

```json
{
  "source": "@theme { --color-brand-500: #3366ff; --spacing: 0.25rem; }"
}
```

OpenAPI 3.1 spec: https://findutils.com/api/openapi.json · Interactive docs: https://findutils.com/api/docs/

## Also an MCP tool

```bash
claude mcp add findutils --transport http https://mcp.findutils.com/
```

Then ask the client to call `findutils:tailwind_to_stylex`. Full MCP reference: https://findutils.com/mcp/tailwind-to-stylex/

---
Full catalog: GET https://api.findutils.com/api/tools · https://findutils.com/api/ · https://findutils.com/llms.txt