MCP Apps Starter Kit
Related Servers
Alternatives to MCP Apps Starter Kit
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA companion desktop app enabling bi-directional interaction between Claude Desktop and visual UI elements, allowing Claude to display, read from, and write to interactive interfaces while processing user events and feedback.5 npm8Apache 2.0
- FlicenseAqualityDmaintenanceAn MCP App that renders an interactive dashboard in Claude conversations to unify calendar events, emails, and documents into a single interface. It enables users to manage their daily schedule and perform actions like meeting preparation through bidirectional communication between the UI and the model.2-
- FlicenseNot gradedqualityDmaintenanceA React single-page application served as an MCP server that renders different UI pages based on the invoked tool name from the host context. It enables embedding interactive React components directly within MCP clients like Claude Desktop through tool calls.-
- AlicenseNot gradedqualityDmaintenanceA Todo app leveraging MCP Apps to provide interactive UI within conversations, allowing users to manage todos via Claude Desktop or Claude Code.MIT
- AlicenseBqualityDmaintenanceA framework for building interactive UI applications and React-based widgets for ChatGPT and Claude using the Model Context Protocol. It enables developers to create custom tools and visual components that facilitate rich, bidirectional interaction between AI models and users.3MIT
- AlicenseBqualityDmaintenancereact-mcp integrates with Claude Desktop, enabling the creation and modification of React apps based on user prompts99 npm76MIT
TDQS
Scored across 8 tools
Most tools target distinct domains (budget, comparison, trip, workout), but render_comparison and render_decision_matrix both compare options, and render_trip_explorer is also comparison-like. The detailed descriptions help clarify, but slight overlap exists.
All render tools follow the consistent verb_noun pattern (render_budget, render_trip, etc.), and the log tools use save_workout_log/get_workout_log. Naming is uniform, snake_case, and predictable.
With 8 tools, the count is well within the ideal range. Each tool appears purposeful, and there is no redundancy or bloat. The broad scope fits a 'starter kit' concept.
The set is a mix of render-only tools with no persistence except for workout logs (save/get). There are no update/delete operations for workout logs, and no data management for budget, comparisons, or trips. The domain is unclear, and lifecycle coverage is inconsistent.