Tailkits Ui

Created By
Yucel Sahan5 months ago
200+ production-ready components your AI already knows. Just describe your UI get clean code, ship faster. Describe, don't code Ask AI what you need in plain English No more template hunting AI creates best UI for your needs Ship by tonight Build entire landing pages with multiple sections
Overview

what is Tailkits UI?

Tailkits UI is a component library that provides over 200 production-ready Tailwind components, allowing users to describe their UI needs in plain English and receive clean, shippable code quickly.

how to use Tailkits UI?

To use Tailkits UI, integrate the MCP server URL into your client configuration and describe the UI you want. The AI will generate the necessary code for you.

key features of Tailkits UI?

  • Access to 200+ production-ready Tailwind components.
  • AI-driven workflows to build landing pages with compatible components.
  • Consistent design language across sections, reducing the need for template hunting.

use cases of Tailkits UI?

  1. Quickly building landing pages with various sections like hero, features, and pricing.
  2. Generating consistent UI components for web applications.
  3. Streamlining the design process for developers and designers.

FAQ from Tailkits UI?

  • Can I use Tailkits UI with any IDE?

Yes! Tailkits UI works with various IDEs including VS Code, JetBrains IDEs, and more.

  • Is there a cost associated with using Tailkits UI?

The pricing details can be found on the Tailkits website.

  • How do I set up Tailkits UI?

Add the Tailkits UI MCP server URL to your client config with your token.

Server Config

{
  "mcpServers": {
    "tailkits-ui": {
      "url": "https://dashboard.tailkits.com/mcp/tailkits?token=YOUR_TOKEN_HERE",
      "transport": "sse"
    }
  }
}
Project Info
Created At
5 months ago
Updated At
5 months ago
Author Name
Yucel Sahan
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago