Dev.cards
Server Details
Free UI components with full source in HTML/CSS/JS and React: heroes, pricing, dashboards, forms.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 3 tools
search_components is clearly a discovery tool, while get_component and get_component_code both target a single component by id and could be momentarily confused. The descriptions do draw a clean line (metadata/design spec vs. full pre-generated source files), so the overlap is minor.
All three names follow a consistent snake_case verb_noun pattern: search_components, get_component, get_component_code. The get_component / get_component_code pair reads as a natural, predictable refinement rather than a convention break.
Three tools is on the thin side, but each maps to a distinct stage of the workflow (discover, inspect, retrieve code) and none feels redundant. A listing/category helper would round it out, but the set is well scoped for the purpose.
The discover → inspect → fetch-code lifecycle is fully covered, including empty-query listing for search_components and per-target code retrieval. Minor gaps exist around bulk retrieval or enumerating categories/targets separately, but agents can work around these via search.
Available Tools
3 toolsget_componentGet a UI componentARead-onlyIdempotentInspect
Get metadata, the design specification, source references and the available implementations of one component by id.
Inputs: id (required), version.
get_component_codeGet UI component source codeBRead-onlyIdempotentInspect
Get the complete, pre-generated source files of one component for one tested target, with their SHA-256 hashes, setup instructions and pinned dependencies. Vanilla is javascript; React is typescript. Styling is always css.
Inputs: id (required), styling (required), language (required), framework (required), +1 more.
search_componentsSearch UI componentsARead-onlyIdempotentInspect
Search the published Dev.cards UI components (hero sections, pricing tables, dashboards, forms, navigation and more) by text and implementation target. Returns compact metadata: id, version, name, category, description and targets. Leave q empty to list every component.
Inputs: q, framework.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Free premium UI components in plain HTML, CSS and vanilla JS, for AI coding assistants.
Search free React, Tailwind, and shadcn components, blocks, and dashboards; get installable source.
React, Tailwind CSS and shadcn/ui components, sections and landing pages for coding agents.
React + Tailwind UI components and recipes your AI coding tool can search and install.
Related MCP Servers
- AlicenseAqualityBmaintenanceSearch, inspect and install Ballmac UI React + Tailwind components, blocks and templates, with props, keyboard notes and the exact shadcn install command, and plan whole pages from blocks.812MIT
- FlicenseAqualityBmaintenanceEnables AI assistants to search a catalogue of plain HTML, CSS and JavaScript UI components and fetch each one's exact files, settings and framework integration instructions. Lets users add production-ready interface components by asking in natural language.221-

Duchampofficial
AlicenseNot gradedqualityBmaintenanceGives coding agents a curated, reviewable library of landing pages, hero sections, image prompts, motion-video recipes, logo and pitch-deck recipes, fonts and motion backgrounds that they can search, inspect and fetch, then rebuild locally from code. Searches and reference inspection are uncounted, while template, UI and asset fetches share a daily free limit under OAuth sign-in with no API key.MIT- AlicenseAqualityDmaintenance🎨 AI-powered UI/UX design intelligence - 1519+ curated design resources through MCP | React, Vue, Next.js, Flutter & more7210 npm41MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.