Skip to main content
Glama

Related Servers

Alternatives to open-mcp-apps

  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables interacting with YouTube Data API v3 through MCP tools (get-video, get-channel, get-latest-video) and bundled UI apps for video and channel profiles.
    4
    ISC

Related Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to respond to users with live, persistent, interactive web apps served at a single URL that evolve in place as the conversation continues. It exposes UI generation and evolution tools over MCP so agent responses can include clickable buttons and streaming interfaces alongside chat replies.
    4
    Apache 2.0
  • F
    license
    Not graded
    quality
    D
    maintenance
    Federates UI component registries, enabling AI agents to fetch exact component code, dependencies, and setup prerequisites directly into the workspace. Includes sandboxed previews, anti-slop layout auditing, and offline-to-cloud telemetry sync.
    1
    -
  • A
    license
    Not graded
    quality
    B
    maintenance
    Gives AI apps a shared, plain-folder memory on your own machine, so whatever you tell one model the others can read, and you can inspect, review and undo every change they make. Memory stays portable across vendors, models and account changes instead of living on a provider's servers.
    42 PyPI
    31
    Apache 2.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to build and deploy an app from a GitHub repository to a managed live server and then operate it — logs, captured errors, health checks, managed Postgres, secrets, custom domains, email authentication, and Stripe checkout links. It also exposes safe, read/write-labelled tools so agents can rebuild, start/stop, and inspect projects without ever editing source code.
    MIT

TDQS

B3.4/5.0

Scored across 34 tools

Disambiguation4/5

Most tools target distinct resources and actions, with detailed descriptions clarifying overlaps (e.g., save_app vs edit_app, data_update_item vs data_move_item). A few pairs like get_app vs get_app_html and data_list vs file_list vs list_apps could be momentarily confused, but the descriptions differentiate them well.

Naming Consistency3/5

All names use snake_case, but verb placement is mixed: app management tools use verb_noun (list_apps, get_app, save_app), while data/file/screen tools use noun_verb (data_list, file_write, screen_read). This domain-based split is readable but not a single consistent pattern.

Tool Count2/5

At 34 tools, the surface is large even for a broad platform. Several tools are explicitly internal-only (get_app_html, get_data_version, preview_app_store_entry, screen_poll), which unnecessarily inflates the agent-facing toolset and suggests consolidation is possible.

Completeness4/5

The set covers app lifecycle (create, read, update, delete, restore, purge, checkpoints), data CRUD with changes and batch writes, file storage, screen interaction, app functions, and settings. Minor gaps exist, such as no explicit collection creation/deletion or file batch operations, but core workflows are well-supported.

Maintenance

ActivitySlowing
ResponsivenessNo recent community issues