Agent
Discoverability

Textures

Curated hover textures for websites. Claude finds one by mood or placement and adds it to your hero or card as one self-contained React file.

View in the Claude registry
Integration details

Description

Textures is a curated library of hover-reactive brand textures for websites: fields of bars, dots, dashes, tiles or rings that answer the pointer behind a hero, header, pricing card, feature card or background. On phones they play by themselves while on screen. Ask Claude for a hover effect, a micro-interaction or an animated background. search_textures finds Textures by your words, placement or size; get_texture returns the exact file to write: one self-contained React component at components/textures/<slug>.tsx, no Tailwind, no dependency beyond React, under 16 KB. Every file is proven before it is served: it compiles in a fresh Next and Vite app, matches the original pixel for pixel, and does no work at rest. check_textures runs the Textures rules on what Claude wrote, and get_guidelines carries the integration rules in one page. Colours come from tokens that default to your project's foreground and background, so a Texture lands in your brand. Every Texture declares where it fits and what it costs, and holds still for visitors who prefer reduced motion. Free Textures need no plan. Pro Textures need a Textures Pro subscription; for anyone else Claude gets the price and the upgrade link, never the code. New Pro Textures arrive every week.

Integration type
Connector
Verification status
Community connector
Platform
Claude
Category
Content & Design

The broad Category that contains the Primary Subcategory.

Primary Subcategory
UI Component Libraries & Design Systems

The Primary Subcategory used for this profile’s headline score.

Secondary Subcategories
None listed

Other Subcategories where the Integration is listed.

Access
Account required
First tracked
2026-10-21
Tool count
6
Market
US
Agent DiscoverabilityClaude Discoverability Score

Claude Connector discovery is coming soon

Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.

No spam. Unsubscribe any time.

What discovery looks like

Claude showing a list of relevant Connectors in a conversation

Claude can surface verified Connectors when they match a user’s Prompt.

Primary Subcategory
0 scoredVerified connectors by score · Community connectors A–Z
Primary Subcategory
—Carbon MCPPending VerificationGet notified
—DS ManagerPending VerificationGet notified
—EddyterPending VerificationGet notified
—FluenticonsPending VerificationGet notified
—HorizonXPending VerificationGet notified
—HueCheck Palette LabPending VerificationGet notified
—Jiro BuildPending VerificationGet notified
—nnuerPending VerificationGet notified
—OODS FoundryPending VerificationGet notified
—Tactile UIPending VerificationGet notified
—TexturesPending VerificationGet notified
—Uniquel UI ComponentsPending VerificationGet notified
—zeroheightPending VerificationGet notified
Tools

6 tools agents can invoke

Recommended guideHow to get your Claude Connector organically discoveredFollow the practical steps agents use to find, shortlist, and choose your Connector.Read guide
FAQs

Textures Claude Connector FAQ

How the directory, categories and Discoverability Score work.

Read the methodology
How do I improve Textures's Claude Connector discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

What are Textures alternatives on Claude?

As of 2026-10-28, Textures competes with Carbon MCP, DS Manager, Eddyter, Fluenticons, HorizonX, HueCheck Palette Lab, Jiro Build, nnuer and 5 more in Claude UI Component Libraries & Design Systems, ranked by public Discoverability Score.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.