FREE MCP SERVER · NO ACCOUNT

Tailkits for your coding agent.

Real Tailwind section code, DESIGN.md tools, the Tailkits directory and a landing-page audit, in Claude Code, Codex, Cursor, Gemini CLI, VS Code and Windsurf. One URL, nothing to sign up for.

https://tailkits.com/mcpStreamable HTTP · 13 tools · 4 prompts

Install

Run in your project (add --scope user for every project).

claude mcp add --transport http tailkits https://tailkits.com/mcp

With a Tailkits UI token (Pro code, higher limits)

claude mcp add --transport http tailkits https://tailkits.com/mcp \
  --header "Authorization: Bearer $TAILKITS_TOKEN"

The prompts appear as slash commands, e.g. /mcp__tailkits__build-landing-page. Create a token at /ui/mcp-setup/.

Reference: Claude Code MCP docs

Run once; it writes ~/.codex/config.toml.

codex mcp add tailkits --url https://tailkits.com/mcp

With a Tailkits UI token (Pro code, higher limits)

# ~/.codex/config.toml
[mcp_servers.tailkits]
url = "https://tailkits.com/mcp"
bearer_token_env_var = "TAILKITS_TOKEN"

Codex reads the token from the environment variable; export TAILKITS_TOKEN in your shell. Create a token at /ui/mcp-setup/.

Reference: Codex MCP docs

~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project).

{
  "mcpServers": {
    "tailkits": {
      "url": "https://tailkits.com/mcp"
    }
  }
}

With a Tailkits UI token (Pro code, higher limits)

{
  "mcpServers": {
    "tailkits": {
      "url": "https://tailkits.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:TAILKITS_TOKEN}"
      }
    }
  }
}

Cursor fills ${env:TAILKITS_TOKEN} from your environment. Create a token at /ui/mcp-setup/.

Reference: Cursor MCP docs

Run in your project, or add the JSON to ~/.gemini/settings.json. httpUrl is Streamable HTTP; url would mean SSE.

gemini mcp add --transport http tailkits https://tailkits.com/mcp

With a Tailkits UI token (Pro code, higher limits)

{
  "mcpServers": {
    "tailkits": {
      "httpUrl": "https://tailkits.com/mcp",
      "headers": {
        "Authorization": "Bearer <your token>"
      }
    }
  }
}

Or: gemini mcp add --transport http -H "Authorization: Bearer $TAILKITS_TOKEN" tailkits https://tailkits.com/mcp Create a token at /ui/mcp-setup/.

Reference: Gemini CLI MCP docs

.vscode/mcp.json in the workspace (GitHub Copilot agent mode), or run MCP: Open User Configuration.

{
  "servers": {
    "tailkits": {
      "type": "http",
      "url": "https://tailkits.com/mcp"
    }
  }
}

With a Tailkits UI token (Pro code, higher limits)

{
  "inputs": [
    {
      "type": "promptString",
      "id": "tailkits-token",
      "description": "Tailkits token",
      "password": true
    }
  ],
  "servers": {
    "tailkits": {
      "type": "http",
      "url": "https://tailkits.com/mcp",
      "headers": {
        "Authorization": "Bearer ${input:tailkits-token}"
      }
    }
  }
}

VS Code asks for the token once and stores it securely. Create a token at /ui/mcp-setup/.

Reference: VS Code MCP docs

mcp_config.json: ~/.codeium/windsurf/mcp_config.json (newer builds: ~/.config/devin/mcp_config.json).

{
  "mcpServers": {
    "tailkits": {
      "serverUrl": "https://tailkits.com/mcp"
    }
  }
}

With a Tailkits UI token (Pro code, higher limits)

{
  "mcpServers": {
    "tailkits": {
      "serverUrl": "https://tailkits.com/mcp",
      "headers": {
        "Authorization": "Bearer ${env:TAILKITS_TOKEN}"
      }
    }
  }
}

Windsurf fills ${env:TAILKITS_TOKEN} from your environment. Create a token at /ui/mcp-setup/.

Reference: Windsurf MCP docs

Tools

UI sections

ui_list_categories: The section categories with counts, free counts and picker links.
ui_search_sections: Search by words, category or free only. Ids, previews, page links.
ui_get_section: One section's code as HTML, React or Astro, with its tokens, motion and setup.
ui_pick_sections: A picker link where you click the sections you like and paste the ids back.

DESIGN.md

designmd_create: A complete DESIGN.md from a style, brand colour, font, radius and motion.
designmd_lint: Errors and warnings for any DESIGN.md.
designmd_to_theme: Tailwind v4, shadcn or plain CSS variables from a DESIGN.md.
designmd_apply: Up to 10 sections restyled with your DESIGN.md, plus the theme CSS.

Directory

directory_search: Templates, components, tools, launches and blog posts by words, tag or category.
directory_get: Features, price, demo, alternatives; blog posts as Markdown.

Launch

launch_audit_page: A deterministic landing-page audit with a score per area and ranked fixes.
launch_checklist: What to do before, on and after launch day, and where to launch.
launch_submit_link: A prefilled Tailkits submission link. It never submits: you do.

Prompts

build-landing-page: Brief to DESIGN.md to picked sections to restyled code.
restyle-with-design-md: Your DESIGN.md applied to Tailkits sections.
launch-my-product: Audit, fix, checklist, submission link.
find-a-template: Directory search for your stack and use case.

Limits and access

No account: every tool works. 300 tool calls a day per IP address, of which 30 page audits. Connecting and listing tools is never limited.
Free sections return their code to everyone. Pro sections return their description, preview and page link; the code needs a Tailkits UI token.
With a token (Authorization: Bearer, from /ui/mcp-setup/): 5,000 calls a day, and Pro code when the account has an active plan.
No AI on our side: every answer is built from Tailkits data or computed by fixed rules. The audit only fetches public https pages.

The Pro-only server for existing Tailkits UI customers stays at /mcp/tailkits.