Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Able.Style is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Manage your wardrobe or closet, discover ways to wear your clothes, and get outfit suggestions.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http able-style-mcp https://able.style/mcp
# 2 — ask your agent for something these tools do
# suggest-outfit-tool, like-dislike-outfit-tool, add-to-or-remove-from-wardrobe-by-id and 12 more
Able.Style costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http able-style-mcp https://able.style/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Generates personalized fashion, style, and outfit suggestions based on wardrobe items, preferences, local weather conditions, and occasion formality. Use this tool when users ask for fashion or style advice such as: "What should I wear?", "What outfit do you recommend?", "Help me choose clothes for [occasion]", "Outfit ideas for [weather/event]", or "What should I wear in [hot/cold/rainy] weather?
| Parameter | Type | Required | Notes |
|---|---|---|---|
| menswearOrWomenswear | yes | Gender category for clothing suggestions: "menswear" for men's clothing, "womenswear" for women's clothing. Set to null if unspecified or user prefers gender-neutral suggestions. Use available user pr | |
| temperature | yes | Weather temperature category for outfit appropriateness: "cold" for < 6°C/43°F (winter coats, layers, boots), "cool" for 6-15°C/43-59°F (light jackets, long sleeves, closed shoes), "warm" for 15-22°C/ | |
| smartness | yes | Formality/dressiness level on a 1-5 scale: 1 = Casual (jeans, t-shirts, sneakers, everyday wear), 2 = Quite Casual (smart jeans, polo shirts, clean trainers), 3 = Smart Casual (chinos, button-down shi | |
| inspirationId | no | Optional identifier of an existing outfit inspiration to reload. Use this only when refreshing the exact outfit already displayed in the widget. |
Records or removes a like or dislike for a specific outfit suggestion. Use this tool when users want to save outfits they love or indicate ones they don't prefer. Use cases: "I like this outfit", "Save this to my favorites", "I don't like this one", "Remove my like from this outfit". Requires authentication - if user is not logged in, this will trigger an OAuth authentication flow. Helps personali
| Parameter | Type | Required | Notes |
|---|---|---|---|
| outfitId | string | yes | The unique identifier of the outfit to like or dislike. IMPORTANT: This exact value is available in the conversation context at result.outfitId in the most recent suggest-outfit-tool response — look t |
| likeOrDislike | string | yes | The preference type to record: "like" to mark the outfit as preferred, or "dislike" to mark it as not preferred. Likes help surface similar outfits in future suggestions, while dislikes help filter ou |
| value | boolean | yes | Set to true to add the preference (like/dislike), or false to remove an existing preference. Use true when user says "I like this" or "I don't like this". Use false when user says "Remove my like" or |
Adds or removes a known clothing item from the user's personal wardrobe by its style ID. Use this tool when users want to track clothing items they own or indicate they have something similar. Use cases: "Add this to my wardrobe", "I have a similar jacket", "Mark that I own this", "Remove this from my wardrobe". Requires authentication - if user is not logged in, this will trigger an OAuth authent
| Parameter | Type | Required | Notes |
|---|---|---|---|
| styleId | string | yes | The unique identifier of the clothing style/item. IMPORTANT: This value MUST be copied exactly from the styleIdentifier.styleId field returned in the most recent previous suggest-outfit-tool respo |
| isUserStyle | boolean | yes | Whether this is a user-created custom style (true) or a catalog style from the platform (false). Most items from outfit suggestions will be catalog styles (false). IMPORTANT: This value MUST be copied |
| styleDescription | string | yes | The user-friendly description of the style to add to or remove from the wardrobe. IMPORTANT: This value MUST be copied from the description field of the outfit item returned in the most recent previ |
| categoryName | no | Provide the category name of the style to add to or remove from the wardrobe. For example: "Jackets", "Shirts", "Trousers", "Shoes". This value is provided in outfit suggestion responses in the "categ | |
| addOrRemove | string | yes | The action to perform: "add" to include the item in the user's wardrobe, or "remove" to delete it from their collection. Use "add" when user says "I have this shirt" or "Add the shoes to my wardrobe". |
Backward-compatible alias of add-to-or-remove-from-wardrobe-by-id. Prefer add-to-or-remove-from-wardrobe-by-id for new calls. Adds or removes a known clothing item from the user's personal wardrobe by its style ID. Use this tool when users want to track clothing items they own or indicate they have something similar. Use cases: "Add this to my wardrobe", "I have a similar jacket", "Mark that I own
| Parameter | Type | Required | Notes |
|---|---|---|---|
| styleId | string | yes | The unique identifier of the clothing style/item. IMPORTANT: This value MUST be copied exactly from the styleIdentifier.styleId field returned in the most recent previous suggest-outfit-tool respo |
| isUserStyle | boolean | yes | Whether this is a user-created custom style (true) or a catalog style from the platform (false). Most items from outfit suggestions will be catalog styles (false). IMPORTANT: This value MUST be copied |
| styleDescription | string | yes | The user-friendly description of the style to add to or remove from the wardrobe. IMPORTANT: This value MUST be copied from the description field of the outfit item returned in the most recent previ |
| categoryName | no | Provide the category name of the style to add to or remove from the wardrobe. For example: "Jackets", "Shirts", "Trousers", "Shoes". This value is provided in outfit suggestion responses in the "categ | |
| addOrRemove | string | yes | The action to perform: "add" to include the item in the user's wardrobe, or "remove" to delete it from their collection. Use "add" when user says "I have this shirt" or "Add the shoes to my wardrobe". |
Adds one item that the signed-in user owns to their Able.Style wardrobe from a text description supplied by the user. Use this when the user describes an item in words and asks to add it. When a photo, attachment or image URL is the source, use add_wardrobe_item_from_image; if transfer is unavailable, use create_image_upload with purpose wardrobe_image_add. Do not infer a description from an image
| Parameter | Type | Required | Notes |
|---|---|---|---|
| description | string | yes | A 10–150 character description of exactly one item the user owns. Use the user's text; do not substitute your interpretation of an attached image unless the user explicitly requests a description-base |
| menswearOrWomenswear | no | Optional clothing preference for resolving categories. Supply only when the user has specified menswear or womenswear; otherwise omit it to use their profile. |
Add one clothing item from the user's original image to their wardrobe. Use this when the user attaches a photo or supplies an image URL and asks to add/save the pictured item, for example 'Add this to my wardrobe'. The server processes the actual image. Do not replace this flow with add_wardrobe_item_from_description or your own visual interpretation. Generate requestId and provide exactly one of
| Parameter | Type | Required | Notes |
|---|---|---|---|
| requestId | string | yes | Unique identifier for this requested action. Reuse it for retries and the upload-page fallback; use a new value for another item. |
| file | object | no | The original image attachment supplied by ChatGPT through its file-input mechanism. Use the host-provided file reference; never fabricate download_url or file_id. |
| imageUrl | string | no | A real, publicly accessible HTTP(S) URL to the original image. Do not use a local path, sandbox URL or an invented URL for a chat attachment. |
| image | object | no | — |
| menswearOrWomenswear | no | The user's clothing preference. Omit to use their saved preference. |
Create a secure web or installed-app image picker when the user asks for an upload link, or an image-based action cannot receive the original image directly. Use this even when you can see a chat photo but cannot pass its real file reference, public URL or original bytes to add_wardrobe_item_from_image. For wardrobe photos, use purpose wardrobe_image_add; do not silently switch to add_wardrobe_ite
| Parameter | Type | Required | Notes |
|---|---|---|---|
| requestId | string | yes | Unique identifier for this requested action. Reuse it for retries and the upload-page fallback; use a new value for another item. |
| purpose | string | yes | — |
| options | object | no | — |
Check the status of an owned wardrobe image action. Returns safe failure details or the added item and its link. Use activityId from add_wardrobe_item_from_image or create_image_upload.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| activityId | string | yes | — |
Use this when the user wants to browse or search their signed-in wardrobe, including questions about categories, colours, attributes, newest items, and natural-language terms such as 'flowery shirts'. Returns up to five items per call and the total number of matches across all pages. The results widget automatically loads further pages as the user scrolls. If the widget is unavailable and nextPage
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | no | Optional natural-language wardrobe search. Whitespace is trimmed. | |
| sortBy | string | no | Sort order. Defaults to relevance for a query and newest-first without a query. |
| filters | object | no | — |
| pageToken | no | Opaque continuation token from the preceding result. When supplied, omit all other inputs. |
Get other styles and owned userStyles that can be worn with a particular clothing item. Uses the same selection logic as the Able.Style style page and requires sign-in. Copy exact IDs from earlier results: a ref with kind style uses styleId, and kind user_style uses userStyleId. Provide exactly one of styleId or userStyleId. Returns five items per page; the widget loads more on scroll. Without a w
| Parameter | Type | Required | Notes |
|---|---|---|---|
| styleId | string | no | Exact catalog style ID. Omit userStyleId and pageToken. |
| userStyleId | string | no | Exact ID of a userStyle owned by the signed-in user. Omit styleId and pageToken. |
| pageToken | string | no | Continuation token from this tool. When supplied, omit all other inputs. |
Get outfit inspirations showing ways to wear a particular clothing item, including their tagged styles and owned userStyles. Uses the same selection logic as the Able.Style style page and requires sign-in. Copy exact IDs from earlier results: a ref with kind style uses styleId, and kind user_style uses userStyleId. Provide exactly one of styleId or userStyleId. Returns five items per page; the wid
| Parameter | Type | Required | Notes |
|---|---|---|---|
| styleId | string | no | Exact catalog style ID. Omit userStyleId and pageToken. |
| userStyleId | string | no | Exact ID of a userStyle owned by the signed-in user. Omit styleId and pageToken. |
| pageToken | string | no | Continuation token from this tool. When supplied, omit all other inputs. |
Find matching products and retailers where the user can buy a catalog style. Requires sign-in. Copy the exact catalog styleId from an earlier result; userStyle IDs are not supported. An explicit country overrides the saved account delivery country; otherwise the saved account country is preferred to the optional host country hint. Ask the user to select a country when neither is available. Save de
| Parameter | Type | Required | Notes |
|---|---|---|---|
| styleId | string | yes | — |
| country | string | no | — |
Recheck an exact purchase offer and return its current retailer link. Requires sign-in. Call only when the user wants to open a retailer, using the exact styleId, styleProductId, offerId and delivery country from style-purchase-options-by-id. Do not call for offers with canBuy false. This opens a product listing; it does not place an order.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| styleId | string | yes | — |
| styleProductId | string | yes | — |
| offerId | string | yes | — |
| country | string | yes | — |
Updates one or more settings on the signed-in user's Able Style profile.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| settings | object | yes | — |
Checks whether the current Able Style app session is signed in. This app-only tool never starts authentication and must not be called by the model.
No parameter schema on file.
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Able.Style or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| suggest-outfit-tool | state-write | state-write: declares readOnlyHint: false |
| like-dislike-outfit-tool | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| add-to-or-remove-from-wardrobe-by-id | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| add-to-or-remove-from-closet-tool | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| add_wardrobe_item_from_description | state-write | state-write: declares readOnlyHint: false |
| add_wardrobe_item_from_image | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| create_image_upload | state-write | state-write: declares readOnlyHint: false |
| get_wardrobe_image_activity | no tags | |
| search_wardrobe | untrusted-input | untrusted-input: keyword "browse" |
| style-wear-with-get-by-id | no tags | |
| style-ways-to-wear-by-id | no tags | |
| style-purchase-options-by-id | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| style-purchase-buy-url | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| update-user-settings-tool | state-write | state-write: declares readOnlyHint: false |
| authentication-status-tool | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 2.1.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Able.Style can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.