Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Agentee 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
Shop all-over print cotton tees with your AI agent: search, cart, promos, checkout. Human pays.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http agentee-mcp https://allover.art/mcp
# 2 — ask your agent for something these tools do
# search_products, get_product, list_collections and 28 more
Agentee 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 agentee-mcp https://allover.art/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.
31 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.
Search the allover.art catalog (one card per design). Args: query? (free text, e.g. 'cat', 'neon koi'), theme? (canonical theme like Cats/Anime/Skulls, comma-separated for several), section? (mens|womens|kids), limit? (<=48), max_price? (USD). Returns product cards with good_id, price and url.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | no | Free-text search, e.g. 'cat' or 'neon koi'. |
| theme | string | no | Canonical theme filter (Cats, Anime, Skulls, ...); comma-separate several. |
| section | string | no | Catalog section: mens, womens or kids. |
| limit | integer | no | Max cards to return (default 24, max 48). |
| max_price | number | no | Only items priced at or below this amount, USD. |
Full details of one product by its code: available sizes, fabrics, per-variant price, and the design 'about' text. Args: code (from search_products).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | Product code from search_products results. |
List active curated collections (themed landing pages) with their slugs and urls. Args: limit?.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max collections to return (default 50, max 100). |
Show the current contents of the user's cart (the same cart they see in the browser when signed in).
No parameter schema on file.
Add a product to the user's cart. Args: good_id (from search/get_product), size (must be one of the product's sizes), fabric? (if the product offers a choice), qty? (default 1). Returns the updated cart.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| good_id | integer | yes | Numeric product id from search_products/get_product. |
| size | string | yes | Size label; must be one of the product's available sizes. |
| fabric | string | no | Fabric label from get_product, if the product offers a choice. |
| qty | integer | no | Quantity to add (default 1, max 99). |
Change the quantity of a cart line by its index (from view_cart); qty=0 removes it. Args: index, qty.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| index | integer | yes | Zero-based cart line index from view_cart. |
| qty | integer | yes | New quantity (0 removes the line, max 99). |
Get the URL where the human opens their cart to review and pay. The agent never pays — checkout is always done by the person in the browser.
No parameter schema on file.
Look up the user's recent orders (or one by number) and their fulfilment status. Args: number?, limit? (default 5).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| number | string | no | Exact order number to look up; omit for the most recent orders. |
| limit | integer | no | Max orders to return (default 5, max 20). |
Change a cart line by its index (from view_cart): set qty (0 removes), or switch size/fabric. Args: index, qty?, size?, fabric?.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| index | integer | yes | Zero-based cart line index from view_cart. |
| qty | integer | no | New quantity; 0 removes the line. |
| size | string | no | New size for this line (must be available for the product). |
| fabric | string | no | New fabric for this line (must be available for the product). |
Remove a cart line by its index (from view_cart). Args: index.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| index | integer | yes | Zero-based cart line index from view_cart. |
Validate and apply a promo code to the cart (server-checked). Returns the new discount/shipping/total, or applied=false with a reason. Args: code.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| code | string | yes | Promo code to validate and apply. |
Remove the applied promo code from the cart.
No parameter schema on file.
Return the shopper's saved default size and fit. Call this BEFORE asking the user for a size — if a default is set, apply it automatically (add_to_cart uses it when size is omitted), and prefer products matching their fit (basic vs oversized).
No parameter schema on file.
Save the shopper's default size and/or fit so they don't re-enter it each time. Args: size (XS…5XL), fit (basic | oversized). Pass only what the user stated.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| size | string | no | Default size: XS, S, M, L, XL, 2XL…5XL. |
| fit | string | no | Fit preference: basic or oversized. |
Return shipping addresses the user used in past orders — offer these to a returning buyer instead of asking again.
No parameter schema on file.
Set the shipping address for this order (validated). Args: name, country, city, address, zip?, phone.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Recipient full name. |
| country | string | yes | Destination country. |
| city | string | yes | Destination city. |
| address | string | yes | Street address line. |
| zip | string | no | Postal / ZIP code (optional where not used). |
| phone | string | yes | Contact phone number for delivery. |
Available shipping methods for the current cart/address, with price and ETA (free over the threshold).
No parameter schema on file.
Choose a shipping method by its option_id (from get_shipping_options). Args: option_id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| option_id | string | no | Shipping option id from get_shipping_options (currently 'worldwide'). |
Full order summary to show the human before ordering: line items, promo/discount, shipping, address, grand total. Prices are server-computed.
No parameter schema on file.
Create a draft order from the cart + address + promo and return {checkout_url, draft_id, expires_at}. The human opens checkout_url — everything is pre-filled — reviews and pays. The agent never pays. Call get_order_preview and confirm with the human first.
No parameter schema on file.
START HERE for any custom-print request: the menu of generation choices (print placements with plain-language descriptions, products, backgrounds, engines+costs). Present these to the human — at minimum ask which PLACEMENT and which PRODUCT they want — before calling studio_generate.
No parameter schema on file.
Generate a CUSTOM t-shirt print from a text prompt (AI, takes 2-10 min). SPENDS THE ACCOUNT OWNER'S STUDIO CREDITS: tell them the cost and their balance and get a yes BEFORE calling this — never spend silently, and never spend to 'try something' on your own initiative. Credits are earned (20 free on signup, 20 with every tee bought), so a wasted one is a real loss to them. Free exception: preserve
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prompt | string | yes | Text description of the design to generate. |
| product | string | no | Studio product base from studio_options (default mens_oversize_tshirt). |
| background | string | no | T-shirt background choice (see studio_options backgrounds). |
| placement | string | no | Print size/position: portrait_extended (default), square_center or chest_small. |
| model | string | no | Generation engine: nb2 (default) or gpt-image-2 — both 1 credit. |
| image_url | string | no | https link to the user's OWN image, used as style/subject reference. |
| preserve | boolean | no | true = print the image exactly as-is, no AI redraw (free); requires image_url. |
Check a custom print generation. Args: print_id (from studio_generate). When done returns preview_url — show it to the human.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| print_id | string | yes | Generation id returned by studio_generate. |
The user's Studio credit balance. Check before studio_generate (1 credit per generation, either engine; welcome bonus 20; every bought tee adds 20).
No parameter schema on file.
Put a FINISHED custom print into the cart as a product. Args: print_id (must be done), product? (same set as studio_generate), size, qty?. Then the normal checkout flow applies (get_order_preview -> prepare_order).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| print_id | string | yes | Finished print id — studio_status must report status=done. |
| product | string | no | Studio product base, same set as studio_generate (default mens_oversize_tshirt). |
| size | string | yes | Size label; must be available for the chosen product. |
| qty | integer | no | Quantity (default 1, max 99). |
The user's designer-program stats (if they are a designer-partner): units sold, revenue, accrued royalties, available for payout, royalty percent, their designer page URL.
No parameter schema on file.
The user's own published designs with live status (products on sale / hidden / pending). Args: limit? (default 50).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max designs to return (default 50, max 200). |
Get a short-lived URL to upload an image file to us (use when the designer has no public link — otherwise pass the URL straight to submit_design). Args: filename?. PUT the raw bytes to upload_url, then pass the returned upload_id to submit_design.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| filename | string | no | Original file name, for readability. |
Send one of the designer's own artworks for moderation. TWO inputs, same path: either artwork files — front/back accept a public image URL OR an upload_id from designer_upload_slot — or session_id of a FINISHED Studio session of theirs (generated with studio_generate; no need to download the print, we fetch it server-side). Args: name (required), front OR session_id (one of them), back?, layout? (
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Design name the moderator will see. |
| front | string | yes | Image URL or upload_id. Omit when passing session_id. |
| session_id | string | no | Finished Studio session of this designer (print_id from studio_generate). Alternative to front. |
| back | string | no | Optional second side: URL or upload_id. |
| layout | string | no | 'front_back' (default) or 'r10'. |
| note | string | no | Anything the moderator should know. |
| batch | string | no | Group id for a bulk upload. |
What the designer has already sent in and where it stands: in review / accepted / needs changes (with the reason). Args: limit?.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max rows (default 50, max 200). |
The user's Studio publications in moderation: in review / in catalog / needs changes. Args: limit?.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max submissions to return (default 20, max 100). |
- 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 Agentee 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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
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 1.0.0.
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 Agentee 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.