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

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

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

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

@@ -0,0 +1 @@
+## Usage

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

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

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

@@ -0,0 +1,41 @@
+### General title guidelines
+
+The Brand Title is a standard headline with a brew shape placed behind a key term to draw visual emphasis. It combines editorial clarity with intentional visual anchoring.
+
+### Writing the title
+
+**Lead with a verb.** Titles should be action-oriented and scannable. A user should understand the proposition at a glance. For example:
+
+Say: "Build faster with us"
+
+Don't say: "Our approach to innovation"
+
+**Keep it short and direct.** Aim for one strong idea per title. Avoid complex subordinate clauses or long noun chains.
+
+**Questions are acceptable** when they invite the reader into a dialogue or frame a challenge. Use sparingly; they shouldn't become the default register. For example:
+
+Say: "How do you want to find freelancers?", "Create a quote", or "Rate this freelancer."
+
+Don't say: "Should we create a quote?" or "How would you rate this freelancer?"
+
+### Choosing the highlighted keyword
+
+The brew shape highlights the **most semantically significant word or phrase** in the title, the term that carries the core message without surrounding context.
+
+**Keep it to 1–2 words maximum.** The shape is a visual accent, not a subtitle.
+
+**Avoid articles, prepositions, and pronouns.** These are structural words, not meaning-carrying ones. The shape should never land on *the*, *a*, *with*, *our*, *you*, or similar.
+
+**Prefer the first or last word of the sentence.** The brew shape works best at either end of the line, it creates a clean visual entry or exit point. A keyword buried in the middle of a sentence fragments the reading flow and weakens the composition.
+
+### Localisation guidelines
+
+The brew shape must highlight the **same semantic meaning across all languages**, not necessarily the same word position.
+
+When translating, prioritise meaning equivalence over structural mirroring. If the equivalent keyword naturally falls in the middle of the sentence in a given language, adapt the phrasing so it moves to the beginning or end**.**
+
+Work with the localisation team to validate that:
+
+- The highlighted word carries the same weight and intent as in the source
+- The position feels natural in the target language, not artificially rearranged
+- The shape doesn't accidentally land on a grammatical particle or auxiliary verb

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

@@ -0,0 +1 @@
+Standard headline with a brew shape placed behind a key term to draw visual emphasis.

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

@@ -0,0 +1,11 @@
+![Title brand on dialog](/uploads/DzCbw8lx7EYvUz82_WGNsg.png)
+
+## Anatomy
+
+## Specifications
+
+## Type
+
+## Variants
+
+## Related

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

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

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

@@ -0,0 +1 @@
+## Usage

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

@@ -0,0 +1,4 @@
+## Rules
+
+- Do: null
+- Don't: null

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

@@ -0,0 +1 @@
+A list of options to help users navigate and perform actions.

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

@@ -0,0 +1,11 @@
+![Menu in company settings](/uploads/fxt643JYc9Du3fPbUjaNKQ.png)
+
+## Anatomy
+
+## Type of menu
+
+## Specifications
+
+## Variants
+
+## Related

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

@@ -0,0 +1,17 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Menu",
+  "slug": "menu",
+  "category": "components",
+  "component": "VJoyMenu",
+  "pageId": 7340384,
+  "pageUid": "7340384",
+  "fetchedAt": "2026-07-15T08:24:45.830Z",
+  "tabs": [
+    "Introduction",
+    "Usage",
+    "Content"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/menu/",
+  "extraction": "zeroheight-api"
+}

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

@@ -0,0 +1,8 @@
+## States
+
+## Do/don't
+
+- Do: Use only one active item in the menu
+- Don't: Use several active items on the menu 
+- Do: Keep the same color as in the DS
+- Don't: Change the icons colors

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

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

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

@@ -0,0 +1 @@
+

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

@@ -0,0 +1 @@
+A compact visual indicator used to signal status, presence, or new activity without the use of explicit text or numerical values

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

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

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

@@ -0,0 +1,35 @@
+![Badge label inside table for expense tracker](/uploads/cMSieUtHmdNJ77giuxfZew.png)
+
+## Number
+
+### Anatomy
+
+| Type | Colors background | Text Color |
+| Red | Joy-Color-Primary-50 | Joy-Color-Neutral-White |
+### Specifications
+
+### Type
+
+| **Variant** | **Purpose** |
+| Pink | Notification color, for a status linked to something new (about the pink color, which reminds us of the new badge) |
+| Orange, yellow and green | Usually used as fonctionnel color (warning, validated...) |
+| Other colors | Use to define different statuses, no specific color rule |
+### Variant
+
+## Default
+
+### Anatomy
+
+### Specification
+
+### Type
+
+| **Variant** | **Purpose** |
+| Pink | Notification color, for a status linked to something new (about the pink color, which reminds us of the new badge) |
+| Orange, yellow and green | Usually used as fonctionnel color (warning, validated...) |
+| Other colors | Use to define different statuses, no specific color rule |
+### Variant
+
+#### Styles
+
+## Related

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

@@ -0,0 +1,18 @@
+## Dot number
+
+### Usage
+
+The badge number component is made up of numbers with the following behavior:
+
+- The number cannot be 0
+
+- The numbers must reflect the number of actions contained in the function.
+
+This type of badge is used to highlight an action to be taken by the user.
+
+### Do/don't
+
+- Do: 
+- Don't: 
+- Do: 
+- Do:

package/dist/doc/zeroheight/components/8386038/change-logs.md

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

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

@@ -0,0 +1,34 @@
+## Anatomy
+
+### Label
+
+- Use a single noun. "Password" is the standard; "New password" or "Current password" are acceptable disambiguators when two fields appear on the same screen.
+- Don't use sentence case with a verb ("Enter your password"), the label is not an instruction. Keep it concise: 1–3 words maximum.
+
+### Placeholder
+
+The placeholder is visible only on an empty field. Use it as a soft prompt, not as a substitute for the label or as a restatement of the requirements.
+
+Once the field contains any value, the placeholder is replaced by masked characters (••••••••). Do not rely on the placeholder to convey critical information; it disappears at the first keystroke.
+
+### Requirement helper texts
+
+- Write each requirement as a noun phrase, not a full sentence. Start with the most common failure (length), then character-type constraints.
+- Use "At least N" for minimums, never "minimum" or "min." Avoid abbreviations: they introduce ambiguity and fail translation.
+- Group symbols and numbers if both are accepted: "One number or symbol". Only split them into separate requirements if they are independently mandatory.
+- When a requirement is met, mark it visually (colour change, checkmark). Don't change the text: the user needs the original wording as a reference while typing.
+- Cap requirements at 3. If your policy has more rules, surface the most restrictive ones here and link to a full policy page.
+
+## States
+
+### Empty
+
+The field has no value. The placeholder is visible and acts as a soft prompt to invite input. All requirements are unmarked.
+
+### Partial
+
+The user is actively typing. The placeholder is replaced by masked characters. Requirements update in real time as each condition is met, giving the user progressive feedback without waiting for submission.
+
+### Full
+
+All requirements are satisfied. Every requirement indicator is marked. The field remains masked for privacy.

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

@@ -0,0 +1 @@
+The **input password** is a secure, single-line field designed to protect sensitive data by masking characters while providing a visibility toggle for user verification

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

@@ -0,0 +1,7 @@
+![Input password example](/uploads/dc2MAKWJevjKPXPr8amggg.png)
+
+## Anatomy
+
+## States
+
+## Related

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

@@ -0,0 +1,18 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Input Password",
+  "slug": "input-password",
+  "category": "components",
+  "component": "VJoyInputPassword",
+  "pageId": 8386038,
+  "pageUid": "8386038",
+  "fetchedAt": "2026-07-15T08:24:45.806Z",
+  "tabs": [
+    "Introduction",
+    "Usage",
+    "Content",
+    "Change logs 🔄"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/input-password/",
+  "extraction": "zeroheight-api"
+}

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

@@ -0,0 +1,6 @@
+## Usage
+
+The **Input Password** follows the same structural rules as the standard [Text Input](https://joy.malt.com/6bf479565/p/89d9e2) but includes specific security features and real-time guidance to ensure users create strong, compliant passwords.
+
+- **Security by Default:** Automatically masks characters to protect sensitive data, and must always include a **Show/Hide toggle** to allow users to verify their entry.
+- **Active Guidance:** Use this component when specific security criteria are required. It is paired with a **Password Requirement Checklist** that updates in real-time as the user types, providing immediate feedback on their progress.

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

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

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

@@ -0,0 +1,38 @@
+## Logic rules
+
+### Quick reference
+
+| **Field** | **Freelancer** | **Client** | **Empty State** |
+| Name | ✅ Always | ✅ Always | N/A |
+| Job title | ✅ Always | ❌ Never | Hide |
+| Company name | ❌ Never | ✅ Always | Hide |
+| Rating | ✅ If ≥ 1 rating | ✅ If ≥ 1 rating | Hide |
+| Profile link | ✅ If accessible by viewer | ❌ Never | Fallback: plain text name |
+### Atoms
+
+#### **Name**
+
+Always displayed. Never omitted, even if the rest of the profile is incomplete.
+
+#### **Job title**
+
+*(freelancers only)* Always displayed.
+
+#### **Company name**
+
+*(clients only)* Always displayed.
+
+#### **Rating**
+
+Show only when at least one rating exists. If the value is zero or null, hide the entire rating row (no empty stars, no "No ratings yet").
+
+#### **Profile link on name**
+
+Apply the usual link treatment only when a profile page is accessible to the current viewer. If not, show the name as plain text.
+
+## Display rules
+
+### Name
+
+- Display as fetched, no transformation
+- Link label = name

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

@@ -0,0 +1 @@
+A condensed version of the profile card used to provide user context within dense layouts or other components.

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

@@ -0,0 +1,9 @@
+![User card example](/uploads/aMmW_2zCD9qM1-DIklTghg.png)
+
+## Anatomy
+
+## Type of user card
+
+## Components
+
+## Related

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

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

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

@@ -0,0 +1,11 @@
+### **Usage**
+
+**User Cards are particularly useful when:**
+
+- **The are** ideal for dense layouts like activity feeds, or sidepanel where a full Profile Card would be too intrusive.
+- When the user's identity is important but not the primary focus of the page (e.g., showing who "client view" a document).
+
+### Do/don't
+
+- Do: Keep it minimal: Only include the bare essentials (Avatar + Name). Avoid adding bios or long descriptions here.
+- Don't: Don't overstuff: Avoid adding action buttons (like "Follow" or "Message") directly onto the User Card; save those for the larger Profile Card.

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

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

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

@@ -0,0 +1,82 @@
+### General guidelines
+
+Dropdowns rely on the complentarity between specific text elements to function correctly:
+
+| **Elements** | **Purpose** | **Required** |
+| Label | Identifies what the dropdown controls | Yes |
+| Placeholder | Hint at the expected selection when empty | Yes |
+| Option text | Individual choices in the list | Yes |
+| Helper text | Additional context or instructions. | Optional |
+| Error message | Explain what went wrong. | Conditional and contextual |
+#### **Labels**
+
+Labels tell users what they are selecting and must be clear, concise, and consistent.
+
+- **Capitalisation**: Use sentence case (ex: "Payment method").
+- **Length:** Keep labels short, ideally **1–3 words**.
+- **Specificity:** Be specific (e.g., use "Ticket type" instead of "Type").
+- **Consistency:** Match labels to the options inside. Mostly noun-based.
+
+Avoid:
+
+- Ending labels with colons.
+- Using title case (ex: “Payment Method”).
+- Including instructions in the label (ex: “Select your payment method”).
+- Using vague terms like “Option” or “Selection”.
+
+#### **Placeholders**
+
+Placeholders appear when no option is selected and disappear once a selection is made. They should guide selection, not replace labels.
+
+- **Capitalisation**: Use sentence case.
+- **Length**: Keep it under 30 characters
+- **Format:** Use sentence case
+- Pattern
+
+- Default: {verb + noun}. Ex: “Select country”
+- Filters: {All + noun}. Ex: “All teams”
+
+#### **Options**
+
+Options are the core content of the dropdowns. They must be scannable and predictable in their form and nature.
+
+- **Capitalisation**: Use sentence case (ex: “Legal entity 1”), unless the option is a proper noun or acronym.
+- **Length**: Use 1 to 4 words per option. Do not use article whenever possible.
+- **Consistency:** Start all options with the same part of speech (all verbs or all nouns)
+- **Specificity**: Ensure every option is distinct and unambiguous.
+
+**Ordering options:**
+
+The order of options significantly impacts usability. Choose the strategy wisely.
+
+| **Strategy** | **When to use** | **Example** |
+| Logical | For sequences involving time, size, quantity, etc. | Project status |
+| Alphabetical | For long lists with no inherent order, with no prioritisation. | Freelancer names, Countries |
+| Frequency | When specific options are selected more often than others | Most popular first |
+| Chronological | For date or time-based options | “Today”, “Last month” etc. |
+| Severity | For status and priority levels | Critical, high, medium, low |
+**Specific options:**
+
+Certains options require consistent treatment across the platform.
+
+- **“None” options**: Use when “no selection” is valid. Label as “None”, “No preference”, or even “Not applicable”. Place consistently at the top or bottom.
+- **“All” options:** Use in filters. Label as “All {items}”. Always place first in the options. Example: “All countries”.
+- **“Other” options:** Use when the user’s desired value might not be listed. Label as “Other” or “Other” + Text field. Always place last.
+- “Add new” actions (see also “Other” + Text field): Allow creation of new options, specific to this user. Start with a verb (”Add new {item}”. Place last, separate visually (divider, different font, etc.)
+
+#### **Error messages**
+
+Error messages explain why a selection is invalid or missing.
+
+- **Required field empty:** "Select a [label]" (e.g., "Select a country").
+- **Invalid selection:** "[Selection] isn't available for [context]" (e.g., "Express shipping isn't available for PO boxes").
+- **Conflict:** "Can't use [selection] with [other]" (e.g., "Can't use 'Draft' with a published date").
+
+#### **Accessibility**
+
+To ensure accessibility for all users:
+
+- Every dropdown must have a visible label programmatically associated with it.
+- Do not use placeholder text as a substitute for a label.
+- Ensure options are text-based; do not rely on colors, emojis, or icons alone to convey meaning.
+- Include units in numeric options (e.g., write "30 days" rather than just "30").

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

@@ -0,0 +1 @@
+The core list component used within dropdown to display and manage a menu of selectable options.

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

@@ -0,0 +1,19 @@
+![Dropdown open in table filters](/uploads/NU-edoiPXJYbN2OTtKs4fg.png)
+
+## Anatomy
+
+## Type
+
+| **Variant** | **Purpose** |
+| Default | Default version |
+| CTA | One or several call to actions |
+| Search | Input search (no autocomplete) |
+## Specifications
+
+## Components
+
+### DowndownList
+
+### Items
+
+## Related

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

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

package/dist/doc/zeroheight/components/8636827/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/foundations/1398439/description.md

@@ -0,0 +1 @@
+**Color tokens** are used to apply colors logically and consistently on the screen and within components.

package/dist/doc/zeroheight/foundations/1398439/ia-colors.md

@@ -0,0 +1,4 @@
+### IA colors
+
+- Do: Using IA colours for UI elements in the product
+- Don't: Using AI colours for non-product branding elements such as shapes

package/dist/doc/zeroheight/foundations/1398439/meta.json

@@ -0,0 +1,17 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Colors",
+  "slug": "colors",
+  "category": "foundations",
+  "component": null,
+  "pageId": 1398439,
+  "pageUid": "1398439",
+  "fetchedAt": "2026-07-15T08:24:45.722Z",
+  "tabs": [
+    "Overview",
+    "Usage",
+    "IA colors"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/colors/",
+  "extraction": "zeroheight-api"
+}

package/dist/doc/zeroheight/foundations/1398439/overview.md

@@ -0,0 +1,29 @@
+![Malt brand color pallet](/uploads/wo0gxR91r6jnu0j7St10lQ.png)
+
+## Product color pallet
+
+### Primary
+
+### Secondary
+
+### Tertiary
+
+### Quaternary
+
+## Neutral
+
+## Functional Colors
+
+### Success
+
+### Error
+
+### Warning
+
+### Information
+
+## Brand color pallet
+
+## IA color pallet
+
+## Dialog Overlay

package/dist/doc/zeroheight/foundations/1398439/usage.md

@@ -0,0 +1,11 @@
+## Color usage tokens
+
+The name of the colors is only to put a context, for the real design token name please check the the [Colors | Pallets](https://zeroheight.com/6bf479565/p/027b08/b/266e61)
+
+### Color
+
+| Name | Variable |
+| `button-bg-primary` | `Joy-primary-50` |
+| `button-bg-secondary` | `Joy-secondary-30` |
+| `surface-bg-primary` | `Joy-neutral-white` |
+| `accessibility-focus-default` | `Joy-information-50` |

package/dist/doc/zeroheight/foundations/1612530/description.md

@@ -0,0 +1 @@
+**Spacing tokens** are used to define the consistent amount of space between elements on a screen. They ensure a predictable and balanced layout by creating a clear rhythm and hierarchy.

package/dist/doc/zeroheight/foundations/1612530/meta.json

@@ -0,0 +1,15 @@
+{
+  "source": "https://zeroheight.com/6bf479565/",
+  "title": "Spacings",
+  "slug": "spacings",
+  "category": "foundations",
+  "component": null,
+  "pageId": 1612530,
+  "pageUid": "1612530",
+  "fetchedAt": "2026-07-15T08:24:45.890Z",
+  "tabs": [
+    "Overview"
+  ],
+  "imagesPath": "packages/core-vue/static/zeroheight/spacings/",
+  "extraction": "zeroheight-api"
+}