A
licenseA
qualityC
maintenanceProvides comprehensive tools for React Native development, automating project initialization, version management, upgrades, Expo integration, and development workflows through AI assistance.
2
26 npm
21
MIT
mcp-ui-expo-tamagui
by Tai-DT
Related Servers
Alternatives to mcp-ui-expo-tamagui
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to view and analyze screenshots from React Native/Expo applications for AI-powered mobile UI development. Integrates with Claude, Cursor, VS Code and other MCP-compatible editors.6 npm15MIT
- AlicenseNot gradedqualityFmaintenanceEnables integration of Gluestack components with Claude Desktop and Cursor IDE for UI development.681 npm46MIT
- AlicenseAqualityCmaintenanceEnables the generation and iterative refinement of React UI components from natural language descriptions or design images using Vercel's v0 API. It provides tools for design-to-code workflows and chat-based component development within Claude, Cursor, and other MCP environments.48 npm20MIT
- AlicenseCqualityDmaintenanceAn extensible Model Context Protocol server that enables AI assistants like Claude to generate React Native components and perform development tasks through a standardized interface.1MIT
- AlicenseBqualityDmaintenancereact-mcp integrates with Claude Desktop, enabling the creation and modification of React apps based on user prompts99 npm76MIT
TDQS
B3.4/5.0
Scored across 6 tools
Disambiguation3/5
Most tools are distinct actions (search vs optimize vs theme creation), but generate_ui_component and get_component_suggestions both target new component creation, creating potential confusion about which to use for a given task. The descriptions hint at a difference (final code vs recommendations) but are brief enough to cause misselection.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern in snake_case (generate, search, get, optimize, create). The two search tools are parallel (search_expo_docs, search_tamagui_docs), and every name clearly starts with an action verb. No mixed conventions or irregularities.
Tool Count5/5
With six tools, the set is well-scoped for the server's purpose of UI development with Expo and Tamagui. Each tool addresses a specific need (generation, documentation, suggestions, optimization, theming) without redundant or excess additions. The count feels complete and not bloated.
Completeness4/5
The tool surface covers the primary lifecycle of UI component development: design/generate, get suggestions, optimize, search docs, and configure themes. Minor gaps exist, such as no explicit tool for previewing components or managing component dependencies, but these are not critical for the core workflow and can be worked around with existing tools.
Maintenance
ActivityInactive
ResponsivenessNo issues