mcp-popup-ui
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| ask_userA | Ask the user to choose exactly ONE option from a list. Use this tool instead of listing options in your text response whenever you need the user to make a decision. WHEN TO USE THIS TOOL:
EXAMPLES OF WHEN TO USE:
⚠️ CRITICAL: Each parameter MUST be passed SEPARATELY. Do NOT combine them! ❌ WRONG (options contains title/description - WILL FAIL): options: [{"label": "A"}, {"label": "B"}], "title": "...", "description": "..." ✅ CORRECT (each parameter separate): options: [{"label": "A"}, {"label": "B"}] title: "Pick one" description: "Choose your preference" PARAMETERS:
The tool opens a popup in the user's browser and waits for their selection. If allow_other is true, users can enter custom text if predefined options don't fit. Returns the selected option as a string, or indicates if the user skipped. |
| ask_user_multipleA | Ask the user to choose ONE OR MORE options from a list. Use this tool instead of listing options in your text response whenever the user can select multiple items. WHEN TO USE THIS TOOL:
EXAMPLES OF WHEN TO USE:
⚠️ CRITICAL: Each parameter MUST be passed SEPARATELY. Do NOT combine them! ❌ WRONG (options contains title/description - WILL FAIL): options: [{"label": "A"}, {"label": "B"}], "title": "...", "description": "..." ✅ CORRECT (each parameter separate): options: [{"label": "A"}, {"label": "B"}] title: "Select features" description: "Choose all that apply" PARAMETERS:
The tool opens a popup in the user's browser and waits for their selections. If allow_other is true, users can add custom text if predefined options don't fit. Returns an array of selected options, or indicates if the user skipped. |
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 2 tools
The two tools are clearly differentiated by singular vs. plural selection. Ask_user restricts to exactly one option, while ask_user_multiple allows multiple selections, with descriptions emphasizing this distinction.
Both tools follow a consistent snake_case verb_noun pattern: ask_user and ask_user_multiple. The naming clearly communicates the shared purpose and the single/multiple distinction.
With only 2 tools, the server feels thin, especially given the broader 'popup-ui' name. The two selection modes cover a narrow niche, and while they are well-defined, the overall surface is minimal.
The tools handle single and multiple choice popups, but other common popup interactions such as free-form text input, simple confirmations, or informational dialogs are missing. Agents must rely on allow_other for custom input, which is not ideal, leaving notable gaps.