ZMP-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| zmp_get_login_statusC | Check authentication status with Zalo Mini App Platform for a given project directory or token. |
| zmp_request_login_qrB | Request a new developer login session and generate a QR code for Zalo authorization. Can optionally wait/poll until scanned. |
| zmp_wait_for_loginA | Poll and wait for user to confirm mobile Zalo QR scan authorization, then automatically save ZMP_TOKEN into .env. |
| zmp_start_oauth_callbackB | Start a local HTTP OAuth callback server (e.g. http://localhost:8085/oauth/callback) to capture redirect code/token. |
| zmp_set_tokenB | Save or update APP_ID and ZMP_TOKEN in the project local .env file. |
| zmp_get_app_infoB | Retrieve Mini App metadata, quotas, and versions from Zalo Developer API. |
| zmp_create_appA | Scaffold a new production-ready Zalo Mini App project with React 18, ZAUI, Vite, and Dark Mode zero-flicker. |
| zmp_buildB | Build the Zalo Mini App project and automatically synchronize bundle assets with app-config.json. |
| zmp_sync_configB | Synchronize CSS and JS build assets into app-config.json and app.json to prevent "No asset defined" errors. |
| zmp_validate_projectB | Validate project configuration, app-config.json format, bundle size limits (10MB/3MB), and allowed file extensions. |
| zmp_deployB | Deploy Zalo Mini App to Zalo Cloud with automatic asset synchronization, chunked upload, and testing quota tracking. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
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.
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.
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.
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.