@maltjoy/mcp-server 0.4.0 → 0.5.0-beta.0

package/dist/doc/zeroheight/components/2352087/description.md

@@ -0,0 +1 @@
+Dropdown allow users to choose from a list of options. Clear and consistent content is essential to make selections faster and reduce user errors.

package/dist/doc/zeroheight/components/2352087/introduction.md

@@ -0,0 +1,18 @@
+![Dropdown open in table filters](/uploads/NU-edoiPXJYbN2OTtKs4fg.png)
+
+## Anatomy
+
+## Type
+
+| **Variant** | **Purpose** |
+| Close | Trigger component closed (could be a button, input...) |
+| Open | Trigger opened with content |
+## Specifications
+
+## Components
+
+### No Button
+
+#### With button
+
+## Related

package/dist/doc/zeroheight/components/2352087/meta.json

@@ -0,0 +1,18 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Dropdown ",
+  "slug": "dropdown",
+  "category": "components",
+  "component": "VJoyDropdown",
+  "pageId": 2352087,
+  "pageUid": "2352087",
+  "fetchedAt": "2026-07-15T08:24:45.741Z",
+  "tabs": [
+    "Introduction",
+    "Usage",
+    "Content",
+    "Change log 🔄"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/dropdown/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/components/2352087/usage.md

@@ -0,0 +1,13 @@
+### When to use
+
+- Users need to select from 3 or more predefined options.
+- Options in the dropdown are not mutually exclusive.
+- Users do not already know the exact options available.
+- Users are familiar with the concepts (countries, legal entities, companies, etc.)
+- Space is limited, and showing all options isn’t practical.
+
+### When not to use
+
+- To push actions → use the [dropdown button](https://joy.malt.com/6bf479565/p/2448b8) instead.
+- Users typically know their answer (ex: rate, prices) → use an input field instead.
+- Options require a complex decision-making process → break the task into multiple steps instead.

package/dist/doc/zeroheight/components/2411991/content.md

@@ -0,0 +1 @@
+

package/dist/doc/zeroheight/components/2411991/description.md

@@ -0,0 +1 @@
+A progress indicator is a visual representation of a user’s progress through a set of steps, guiding toward the completion of a specified process.

package/dist/doc/zeroheight/components/2411991/introduction.md

@@ -0,0 +1,27 @@
+## Anatomy
+
+### Specs
+
+| Height Step | Width | Label | Steps | Substeps |
+| 8px | Full screen | padding-left: 40px | 3 maximums | 10 maximums |
+### States
+
+![image](/uploads/aiO9gm8RrCdDbO1j5tw3Lw.svg)
+
+### Intermediate steps
+
+The intermediate steps are used to show the user his progress in the funnel.
+
+They do not need titles and can be up to 10.
+
+**The size of the progress bar is adapted to the number of steps**
+
+![image](/uploads/KqvpaJXjcPwvJ2_xZIo9NQ.svg)
+
+## Components
+
+### Desktop
+
+### Mobile
+
+## Example

package/dist/doc/zeroheight/components/2411991/meta.json

@@ -0,0 +1,18 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Stepper",
+  "slug": "stepper",
+  "category": "components",
+  "component": "VJoyStepper",
+  "pageId": 2411991,
+  "pageUid": "2411991",
+  "fetchedAt": "2026-07-15T08:24:45.895Z",
+  "tabs": [
+    "Introduction",
+    "Usage",
+    "Content",
+    "Release log 🔄"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/stepper/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/components/2411991/release-log.md

@@ -0,0 +1 @@
+## Change log

package/dist/doc/zeroheight/components/2411991/usage.md

@@ -0,0 +1 @@
+

package/dist/doc/zeroheight/components/2427736/change-log.md

@@ -0,0 +1 @@
+## Change log

package/dist/doc/zeroheight/components/2427736/description.md

@@ -0,0 +1 @@
+Component description

package/dist/doc/zeroheight/components/2427736/introduction.md

@@ -0,0 +1,11 @@
+## Components
+
+### Desktop
+
+WIP
+
+## Example
+
+![image](/uploads/nNXrtMuLrzZLfI4u0oOHaw.png)
+
+## Related

package/dist/doc/zeroheight/components/2427736/meta.json

@@ -0,0 +1,17 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Separator",
+  "slug": "separator",
+  "category": "components",
+  "component": "VJoySeparator",
+  "pageId": 2427736,
+  "pageUid": "2427736",
+  "fetchedAt": "2026-07-15T08:24:45.881Z",
+  "tabs": [
+    "Introduction",
+    "Usage",
+    "Change log 🔄"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/separator/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/components/2427736/usage.md

@@ -0,0 +1 @@
+

package/dist/doc/zeroheight/components/2427817/change-log.md

@@ -0,0 +1 @@
+## Change log

package/dist/doc/zeroheight/components/2427817/content.md

@@ -0,0 +1,69 @@
+## General guidelines
+
+Tooltips should enhance the experience without obstruction. Ensure they don’t cover interface elements, especially the ones they relate to, and position them strategically around those elements.
+
+Writing guidelines may vary depending on the usage of the tooltip.
+
+| **Education** | A tooltip can help users understand uncommon functionality, interface elements, interaction or terminology. |
+| **Accessibility** | A tooltip can help label icon-only buttons, and allows user to understand the action they will take without requiring additional navigation. |
+| **Disclosure** | A tooltip can help disclose overflow text in a limited text field such as a table column. |
+## Education
+
+Use a tooltip to educate users about a specific functionality or terminology. Do this in a brief and informative manner.
+
+- Do: Try to remain the limit of 2 to 3 lines.
+- Don't: Avoid exceeding 150 characters, spaces included.
+
+Use a neutral, descriptive tone of voice.
+
+- Do: Use plain language and an informative tone.
+- Don't: Never add “Joy”. If you want to promote a feature, use the Product Tour or Dialog component.
+
+Since it only appears on hover, not all users may see the tooltip. They should only include secondary or complementary information.
+
+- Do: Provide helpful advice to further support the user experience.
+- Don't: Avoid putting critical, mandatory information in tooltips.
+
+Because tooltips are displayed on hover (web), they should only provide immediate, accessible information. They are not actionable and can’t involve a link.
+
+- Do: Provide the entirety of the information in the tooltip.
+- Don't: Never add link in tooltips.
+
+### Show bold content - optional
+
+Bold content should be used Able the bold content in a tooltip to:
+
+- introduce the context in a longer tooltip
+- add a title to a table (see "Show table" below)
+
+- Do: Remain simple and clear.
+- Don't: Avoid showing bold content to label icon-only buttons.
+- Do: Use the bold content as a label.
+- Don't: Never use punctuation at the end of the bold content.
+- Do: Introduce the topic of the tooltip.
+- Don't: Avoid repeating the same information in the bold content and the rest of the tooltip.
+
+### **Show table - optional**
+
+⚠️ The table display only occurs in a few edge cases such as the activity tracker or total cost breakdown.
+
+- Do: Use the default content to introduce the table.
+- Don't: Avoid adding unnecessary bold content, repeating the default content.
+- Do: If you need to add further details about the table, add bold content to label your table and add the secondary information in the default content.
+
+## Accessibility
+
+When used to explain an icon, tooltips shouldn’t be longer than 2 or 3 words.
+
+- Do: Write a minimalist text.
+- Don't: Never use punctuation or emojis.
+- Do: Be straight-to-the point.
+- Don't: Avoid unnecessary long sentences.
+- Do: Whenever possible, add a subject to the verb for additional context.
+- Don't: Whenever possible, avoid generic content.
+
+## Disclosure
+
+A tooltip can help disclose overflow text in a limited text field such as a table column.
+
+## Related guidelines

package/dist/doc/zeroheight/components/2427817/description.md

@@ -0,0 +1 @@
+A tooltip is an additional, non-actionable text that appears on hover to explain an interface element to the user.

package/dist/doc/zeroheight/components/2427817/meta.json

@@ -0,0 +1,18 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Tooltip",
+  "slug": "tooltip",
+  "category": "components",
+  "component": "VJoyTooltip",
+  "pageId": 2427817,
+  "pageUid": "2427817",
+  "fetchedAt": "2026-07-15T08:24:45.909Z",
+  "tabs": [
+    "Overview",
+    "Usage",
+    "Content",
+    "Change log 🔄"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/tooltip/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/components/2427817/overview.md

@@ -0,0 +1,22 @@
+![Tooltip in the quote](/uploads/i2nPJyxlLXdntz73xP-5Vg.png)
+
+## Anatomy
+
+## Specifications
+
+## Type
+
+## Behavior
+
+### Entry point
+
+The tooltip what trigger when interact with a ***“?”**** icon* or a ***component*** :
+
+- On hover for desktop
+- On click for the tablet and mobile
+
+The tooltip position is stick to the text
+
+## Example
+
+## Related

package/dist/doc/zeroheight/components/2427817/usage.md

@@ -0,0 +1,23 @@
+### Tooltip composition
+
+- Do: What can you have in a tooltip
+ 
+- Simple picture or visual
+- Text
+- Don't: What you can’t have in a tooltip
+
+- Video 
+- Complex picture 
+- Very long text 
+- Full table
+- Links
+
+### How can I use a tooltip
+
+- For contextual information
+- To show a definition of the topic
+
+### How I can't use a tooltip
+
+- Showing complex information (table...)
+- Showing high-level information

package/dist/doc/zeroheight/components/2432739/change-log.md

@@ -0,0 +1 @@
+## Change log

package/dist/doc/zeroheight/components/2432739/content.md

@@ -0,0 +1,112 @@
+## General guidelines
+
+There are 4 variants to highlight, each with a specific colour and icon, associated with and supporting the nature of the content.
+
+Be careful about the trigger and variant you use in a given context.
+
+- Do: Use the positive and didactic “Information” in a preventive manner to support users take the right steps.
+- Don't: Avoid using warning variants in a preventive manner, before users had the chance to interact with the section.
+
+### Tone
+
+The highlight informs users about important **contextual** messages—use it to alert and guide users in completing ongoing tasks. Highlights should always be placed in direct relation to a specific section or page.
+
+Highlights are **permanent** and can be somewhat intrusive or disruptive to the user experience. Use them only to notify users about high-priority or time-sensitive actions.
+
+Do not use more than one highlight at a time within a given section. If multiple messages need to be communicated, prioritize the most urgent or blocking issue first, or consolidate them into a single highlight.
+
+- Do: Use the right variant and provide immediate help to solve the situation.
+- Don't: Avoid stacking several highlights without a clear link between them.
+
+Do not exceed 2 lines (approximately 130 characters spaces included). ⚠️ **Reduce the length to a maximum of approximately 100 characters on mobile.**
+
+- Do: Write a concise highlight.
+- Don't: Avoid unnecessary details and length.
+
+### Label - optional
+
+Labels are optional. Use label to introduce the highlight’s topic and focus on a primary information.
+
+- Do: Divide the different levels of information between label and subtitle.
+- Don't: Never use the label only.
+- Don't: Never duplicate content in the label and subtitle as it will create noise.
+
+### Links - optional
+
+Links in highlights are optional and should be used sparingly. In some rare cases, users can be redirected to the FAQ, help centre or other sections of the product for additional context on their situation.
+
+- Do: Write a clear, accessible, and actionable link.
+- Don't: Avoid inserting the link on the middle of the highlight.
+- Don't: Avoid adding the link on a single word that may be unseen or unaccessible.
+
+## Information
+
+Information highlights are not system feedback, they are permanent and contextual.
+
+Display them **before** the action is performed to educate users about the current situation, the next steps and how to get there.
+
+- Do: Plan ahead, support before the error.
+- Don't: Never give information too late when you can prevent error from happening.
+
+Use a didactic, slightly joyful tone (when appropriate) but always get right to the topic.
+
+- Do: Engage the user with a light tone, when appropriate.
+- Don't: Depending on your goals and context, avoid being too neutral.
+- Don't: Avoid being overly joyful.
+
+## Warning
+
+Use warnings to alert users about possible errors **before** they occur and provide clear, actionable steps to avoid issues.
+
+- Do: Help the user prevent potential issues and blockers.
+- Don't: Avoid using error highlights when warning are possible.
+
+Keep the message neutral and educational rather than alarming. The tone should be simple and direct.
+
+- Do: Remain neutral.
+- Don't: Avoid being overly alarming.
+- Don't: Avoir merely notifying the user. Focus on prevention and resolution instead.
+
+## Validation
+
+Validation highlights acknowledge a positive event that benefits the user.
+
+This type of highlight reassures users and differentiates from **informational highlights** by confirming a successful outcome.
+
+- Do: Acknowledge successful outcomes—after an autosave, for example.
+- Don't: Don't use informational highlights for validation - they should be displayed before an action is performed.
+
+The tone varies from neutral to slightly joyful but not overly enthusiastic. Reinforce user confidence without unnecessary celebration.
+
+- Do: Add discrete, concise hints of Joy ("All set!", "ready to roll").
+- Don't: Avoid being overly enthusiastic and using interjections (”Woop woop!”), adjectives or adverbs such as “successfully”.
+
+## Error
+
+Error highlights are displayed **after** an issue has occurred, helping users understand what went wrong and how to proceed.
+
+Use error highlights to explain the issue, why it happened, and how to resolve it.
+
+- Do: undefined
+- Don't: Avoid being vague and not providing resolution.
+
+Maintain a clear, neutral, and instructional tone.
+
+- Do: undefined
+- Don't: Avoid dramatic or alarming language.
+
+## AI
+
+The AI-variant focuses on AI-centered and AI-infused features only.
+
+Use a positive, slightly joyful tone—engaging but not overly enthusiastic or overpromising.
+
+- Do: undefined
+- Don't: undefined
+
+Emphasize the specific benefits AI brings to the user in this context, avoiding generic AI advantages.
+
+- Do: Highlight the immediate benefits of AI.
+- Don't: Never use generic and subjective qualifiers.
+
+## Related guidelines

package/dist/doc/zeroheight/components/2432739/description.md

@@ -0,0 +1 @@
+A highlight is a permanent feedback used to draw users' attention to important information. It supports several variants to provide context to the message.

package/dist/doc/zeroheight/components/2432739/meta.json

@@ -0,0 +1,18 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Highlight",
+  "slug": "highlight",
+  "category": "components",
+  "component": "VJoyHighlight",
+  "pageId": 2432739,
+  "pageUid": "2432739",
+  "fetchedAt": "2026-07-15T08:24:45.780Z",
+  "tabs": [
+    "Overview",
+    "Usage",
+    "Content",
+    "🔄 Change log"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/highlight/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/components/2432739/overview.md

@@ -0,0 +1,17 @@
+![Highlight in client onboarding.](/uploads/51sSxESrIiK8a2IK9DssXA.png)
+
+## Anatomy
+
+## Specifications
+
+## Type
+
+## Size
+
+## Variants
+
+### Desktop
+
+### Mobile
+
+## Related

package/dist/doc/zeroheight/components/2432739/usage.md

@@ -0,0 +1,43 @@
+## Variants
+
+There are 4 variants to highlight, each with a specific colour and icon, associated with and supporting the nature of the content.
+
+### **Deprecation of the default highlight**
+
+The “default” (neutral) highlight was previously used to communicate neutral information without any specific tone. However, we are gradually phasing out its use in new designs.
+
+Our Design System already includes four highlight variants, each with a distinct purpose, colour, and tone (see above). These variants are designed to cover all potential use cases.
+
+Besides, from a UX Writing perspective, a message always carries a tone, as it inherently addresses a user need. Therefore, a fully neutral highlight is not necessary.
+
+#### **Fallback Options**
+
+If you were previously using the default highlight, choose the most appropriate alternative based on the message’s intent:
+
+- **Informational highlight** – for general updates or useful context;
+- **Warning highlight** – for alerts or potential issues;
+- **Validation highlight** - for confirmation and positive outcomes;
+- **Error highlight - **for issues blocking the experience.
+
+## Rules
+
+The highlight has to be used with the accent bar OR icon but **not both.**
+
+- **Accent bar:** Use it to increase the message's visibility.
+- **Icon alignment**: The icon is always aligned with the first line.
+
+## How can I use a highlight
+
+### Highlight or error field?
+
+Highlights apply to broader contexts, not just individual form fields, which require an inline error message.
+
+- Do: Use in-context, specific helper.
+- Don't: Avoid using generic error component for a specific field.
+
+### Highlight or snackbar?
+
+Error highlights should be used instead of a snackbar when the issue requires the user’s focus and prevents further action
+
+- Do: Make sure the error and solution are visible and accessible, especially if it blocks the experience.
+- Don't: Avoid using temporary, not dismissible snackbars that may be unnoticed.

package/dist/doc/zeroheight/components/2434826/change-log.md

@@ -0,0 +1 @@
+## Change log

package/dist/doc/zeroheight/components/2434826/content.md

@@ -0,0 +1,72 @@
+Placeholders should offer **useful and specific guidance** about the expected input. They serve as **hints** to indicate input format or suggest example content, but should not replace labels.
+
+## Placeholder general guidelines
+
+- Keep placeholder text short and concise,** ideally between 3–5 words **(more for free text).
+- Use **simple, familiar language** that is easy to understand.
+- Avoid jargon, full sentences, or overly detailed explanations.
+- Do not overload the placeholder with too much information—keep it focused and clear.
+- **Do not repeat the field label** in the placeholder. Redundancy can confuse users and reduce clarity.
+
+### Accessibility
+
+Avoid truncating placeholder content, as this can negatively impact usability.
+
+- Do: Keep the placeholder within the frame of the field.
+- Don't: Avoid unnecessary lengths.
+
+**Make sure key information to fill the field is accessible outside of the placeholder, as they disappear when users begin typing.**
+
+- Do: Leverage helper text to convey secondary information.
+- Don't: Do not include required instructions solely within the placeholder.
+
+### Types of input
+
+Adapt placeholder content based on the type of input:
+
+- For **action-based fields,** describe the expected written text using **clear and direct verbs ("Search", "Add", "Upload", etc.).**
+
+- Do: Be specific about the action to take.
+- Don't: Avoid generic placeholders.
+
+- Do: Provide additional information about the type of input.
+- Don't: Avoid vague instructions, which offer no contextual guidance.
+
+- For **guidance-based placeholders**, use **examples** (e.g., for dates, emails, phone numbers). However, examples should never replace the label.
+
+- If an example may be misinterpreted as actual input, consider placing it as **helper text below** the input field instead.
+- When using examples within a placeholder, **clearly indicate them by using “Ex:”.**
+
+- Do: Use obvious false or random inputs on top of adding "Ex:".
+- Don't: Avoid confusing the user with seemingly prefilled data.
+
+- Do: Remember to localise placeholder inputs whenever relevant.
+- Don't: Avoid using the same placeholders for all countries.
+
+#### Examples of placeholder usage
+
+| Input Type | Example Placeholder |
+| Name | "First name" |
+| Email | "e.g., [name@domain.com](mailto:name@domain.com)" |
+| Phone Number | "+1 123 456 7890" |
+| Date of Birth | "DD/MM/YYYY" |
+| Username | "Choose a username" |
+| Search Bar | "Search..." |
+## Label usage
+
+- **Always include a label** alongside your input field.
+
+- If a visual label is not present, the placeholder will temporarily act as one. In such cases, a floating or persistent label must appear when the user interacts with the field.
+
+- Do: undefined
+- Don't: undefined
+
+## Placeholder vs. helper text
+
+- **Placeholders** provide short, temporary hints **inside** the input field.
+
+✅ Example: `"e.g., +44 123 4567"`
+- **Helper Text** offers additional instructions and persists **below** the input field.
+
+✅ Example: `"Include country code for international numbers."`
+- If the guidance requires more detail, use **helper text instead of a long placeholder**.

package/dist/doc/zeroheight/components/2434826/description.md

@@ -0,0 +1 @@
+Component description

package/dist/doc/zeroheight/components/2434826/introduction.md

@@ -0,0 +1,15 @@
+## Anatomy
+
+## Size
+
+## Components
+
+### € / %
+
+### Day Month
+
+## Example
+
+![image](/uploads/urmC4wRGXhkHPXAH0HgBxw.png)
+
+## Related

package/dist/doc/zeroheight/components/2434826/meta.json

@@ -0,0 +1,17 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Input Number",
+  "slug": "input-number",
+  "category": "components",
+  "component": "VJoyInputNumber",
+  "pageId": 2434826,
+  "pageUid": "2434826",
+  "fetchedAt": "2026-07-15T08:24:45.803Z",
+  "tabs": [
+    "Introduction",
+    "Content",
+    "Change log 🔄"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/input-number/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/components/2564356/code.md

@@ -0,0 +1 @@
+

package/dist/doc/zeroheight/components/2564356/description.md

@@ -0,0 +1 @@
+Component description

package/dist/doc/zeroheight/components/2564356/introduction.md

@@ -0,0 +1,39 @@
+## Definition
+
+A **modal bottom sheet** must be used to help the user to focus on options, or to give him several choices of actions in a context.
+
+It is an alternative to inline menus or simple dialogs on mobile. They must be dismissed in order to interact with the underlying content.
+
+They may vary according to need and context, by using a number of elements, the composition (list or grid), etc.
+
+### **Size**
+
+Its size may vary depending on the content.
+
+### Natif iOS & Android
+
+On natif, the modal bottom sheet is native component.
+
+### Web
+
+For the web, the modal bottom sheet is working as classic modal
+
+## Anatomy
+
+![image](/uploads/GoVIu0bV9kt7c19Y_WIvEA.svg)
+
+## Overlay
+
+## Components
+
+### Bottom Sheet
+
+### Sticky
+
+### Header
+
+## Examples
+
+![image](/uploads/MGS0MKG7X-i9XHDqKVPW-g.png)
+
+## Related