A
licenseNot graded
qualityD
maintenanceEnables AI assistants to manage TCSAS miniprogram development tasks such as launching the IDE, previewing, and uploading miniprograms via natural language.
8 npm
MIT
ZMP-MCP
Related Servers
Alternatives to ZMP-MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to build, deploy, and inspect apps through a hosted backend service, including reading platform docs, deploying raw source, inspecting logs, verifying live pages in browsers, and managing project tasks.MIT
- AlicenseNot gradedqualityAmaintenanceEnables developers using agentic AI tools to scaffold applications and integration cards, retrieve API references and best-practice guidelines, inspect project metadata, validate manifests, and detect and fix framework-specific code issues.452 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to deploy and manage apps on blitz.cloud, including databases, environment variables, DNS records, and logs.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to deploy and manage compatible web apps, isolated Postgres databases, and project file storage, while inspecting build logs, runtime errors, and usage through an OAuth-authenticated remote MCP connection.MIT
- AlicenseAqualityBmaintenanceEnables AI assistants to deploy and manage SnapDeploy containers and resources—including builds, logs, environment variables, databases, and custom domains—directly through natural language.1591 npmMIT
TDQS
A3.5/5.0
Scored across 11 tools
Disambiguation3/5
The auth tools (request_login_qr, wait_for_login, get_login_status, start_oauth_callback, set_token) have overlapping responsibilities, especially request_login_qr which can also wait/poll, blurring its boundary with wait_for_login. Build, sync_config, and deploy also all mention asset synchronization, which could cause misselection.
Naming Consistency5/5
All tools consistently use the zmp_ prefix with snake_case action-noun patterns (e.g., zmp_create_app, zmp_build, zmp_get_app_info). The convention is predictable and readable throughout.
Tool Count5/5
11 tools is well within the ideal range and each maps to a distinct step in the Zalo Mini App lifecycle (auth, create, build, validate, deploy). The count feels appropriately scoped for the server's purpose.
Completeness4/5
The surface covers the core development lifecycle from authentication through deployment, including project scaffolding, validation, and config sync. Minor gaps exist such as listing all apps or managing app metadata updates, but these are not critical for the primary workflow.