Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Vibe Manufacturing 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
Find manufacturers worldwide, match a part spec to suppliers, estimate cost, request quotes.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http vibe-manufacturing-mcp https://vibe-manufacturing.com/api/mcp
# 2 — ask your agent for something these tools do
# search, fetch, search_site and 21 more
Vibe Manufacturing 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 vibe-manufacturing-mcp https://vibe-manufacturing.com/api/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.
24 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 Vibe Manufacturing playbook, guides, tool reviews and the manufacturer directory. Mention a process (for example CNC machining) or a country to get matching manufacturers. Returns result ids for fetch.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What to look for, e.g. "laser cutting manufacturers in Germany" or "how to check manufacturability" |
Fetch the full text of a document or manufacturer profile by the id returned from search.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | A page URL or supplier:<CC>:<domain> from search results |
Search the playbook, guides, tool reviews and comparisons on vibe-manufacturing.com.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free-text search term |
| limit | integer | no | Max results, 1 to 20 |
Get one of the 13 playbook steps (summary, explanation, checklist, related tools).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| step | integer | yes | Step number 1 to 13 |
List tools and factories with pros and cons. Optional category: Fabrication, Electronics, Sourcing, Prototyping, Measuring, Design, Review.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Optional category filter |
Estimate landed cost per unit and the price needed for a target margin for a custom product. All money values in USD per unit.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| part | number | no | — |
| finishing | number | no | — |
| hardware | number | no | — |
| assembly_minutes | number | no | — |
| labor_rate_per_hour | number | no | — |
| packaging | number | no | — |
| shipping | number | no | — |
| returns_percent | number | no | — |
| payment_fee_percent | number | no | — |
| target_margin_percent | number | no | — |
Find contract manufacturers in the directory by country and process. Processes: laser-cutting, cnc-machining, sheet-metal, 3d-printing, injection-molding, pcb-assembly, die-casting, welding, waterjet-cutting, metal-stamping, forging, heat-treatment, grinding-polishing, casting, wire-forming, steel-construction, surface-finishing. Country as ISO code (DE) or slug (germany).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | no | ISO 3166-1 alpha-2 code or country slug |
| process | string | no | Process id, e.g. laser-cutting |
| city | string | no | — |
| limit | integer | no | Max results, 1 to 100 |
Rank manufacturers for a structured part spec. Returns scored matches with the reasons, so an agent can explain the choice to its user.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| process | string | yes | — |
| materials | array | no | — |
| certifications | array | no | — |
| country | string | no | Preferred country, ISO code or slug |
| quantity | integer | no | Units wanted; favors prototype-friendly shops for small numbers and series producers for large ones |
| file_formats | array | no | CAD formats you can supply |
| industries | array | no | — |
| tolerance_mm | number | no | Tightest tolerance you need, in mm |
| limit | integer | no | — |
Design-for-manufacturing rules for one process (sheet metal, CNC machining, injection molding, 3D printing, casting, welding, PCB assembly and more): typical tolerances, file formats, the rules with their reasons, a pre-RFQ checklist and common mistakes. Typical rules of thumb; the manufacturer's own guidelines override them. Omit process to list all.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| process | string | no | — |
Check a design against typical manufacturing rules before you request quotes. Returns pass, warn or fail per check with the limit and the reason. Supported processes: sheet-metal, laser-cutting, cnc-machining, 3d-printing, injection-molding, die-casting, casting, metal-stamping, pcb-assembly. Parameters are in millimetres/degrees, for example thickness_mm, bend_radius_mm, flange_length_mm, hole_di
| Parameter | Type | Required | Notes |
|---|---|---|---|
| process | string | yes | — |
| params | object | yes | Numeric design parameters, see the tool description |
Find manufacturing businesses you can contact directly, including official-registry establishments without a website (Mexico: INEGI DENUE). Returns how to reach each one: contact form, phone and email (published only for legal entities), website. Filter by ISO country code (MX, US, ...), process and city. Use next_after to page.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | no | ISO 3166-1 alpha-2, e.g. MX |
| process | string | no | — |
| city | string | no | — |
| limit | integer | no | — |
| after | integer | no | next_after value from the previous page |
Send a quote request for the human you act for. Only call after the user agreed that the request and email may be shared with suitable manufacturers. A person reviews it and replies by email.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| string | yes | Reply address of the human requester | |
| description | string | yes | Part, material, size, tolerances, file formats |
| process | string | no | — |
| country | string | no | — |
| quantity | string | no | — |
| user_consent | boolean | yes | true only if the user agreed to share the request with manufacturers |
Create a structured request for quotation for the human you act for. Call get_rfq_requirements for the process first and upload files with upload_rfq_file; use dry_run to check completeness before sending. The answer contains quote_readiness, missing and recommended items. We match manufacturers, email the ones that opted in, and return direct contact, quote-form and agent links for all matches pl
| Parameter | Type | Required | Notes |
|---|---|---|---|
| process | string | yes | — |
| quantity | integer | yes | — |
| description | string | yes | Part, size, material, use |
| requester_email | string | no | Reply address of the human requester; required unless dry_run |
| user_consent | boolean | no | true only if the user agreed to share the request with matched manufacturers; required unless dry_run |
| materials | array | no | — |
| certifications | array | no | — |
| industries | array | no | — |
| file_formats | array | no | — |
| cad_files | array | no | — |
| tolerance_mm | number | no | — |
| finish | string | no | — |
| needed_by | string | no | — |
| ship_to_country | string | no | ISO 3166-1 alpha-2 |
| budget_note | string | no | — |
| thickness_mm | number | no | Material thickness for sheet, plate and cut parts |
| file_ids | array | no | file_id values returned by upload_rfq_file |
| dry_run | boolean | no | true = check completeness only; nothing is stored or sent |
| strict | boolean | no | true = refuse to send when required items are missing |
| callback_url | string | no | Optional https URL that receives a signed event when a factory answers |
Read the matches and the quotes received so far for an RFQ you created. Needs the rfq_id and the token returned by create_rfq.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rfq_id | string | yes | — |
| token | string | yes | — |
What a factory needs to quote a given process (required and recommended items with accepted values). Read this before create_rfq so the request is complete.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| process | string | yes | — |
Upload a design file (STEP/STP, IGES/IGS, STL, 3MF, OBJ, DXF, DWG, PDF, ZIP (Gerber files go in a ZIP); up to 6 MB as base64 here, up to 100 MB with POST /api/v1/rfq/files?name=...). Returns a file_id to pass in create_rfq file_ids. Unused files expire after 24 hours. Only upload files the user agreed to share with manufacturers.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | File name with extension, e.g. bracket.step |
| content_base64 | string | yes | — |
| rfq_id | string | no | Optional: attach to an existing request (needs token) |
| token | string | no | The rfq token, or a supplier token, when rfq_id is given; may be sent as Authorization: Bearer instead |
Write to the matched factories about a request (buyer token) or to the buyer (supplier token): a question, an answer or an update, optionally with file_ids. We relay it by email or API and keep the thread.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rfq_id | string | yes | — |
| token | string | no | rfq token (buyer) or supplier token (factory); may be sent as Authorization: Bearer instead |
| body | string | yes | — |
| kind | string | no | — |
| company_id | integer | no | Buyer only: address one matched manufacturer instead of all |
| file_ids | array | no | — |
Read the conversation of a request: messages from factories (answers, quotes, files) and your own. Pass since=<last message_id> to get only new ones.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rfq_id | string | yes | — |
| token | string | no | rfq token (buyer) or supplier token (factory); may be sent as Authorization: Bearer instead |
| since | integer | no | — |
For a manufacturer's agent: answer an RFQ the company was matched to. Needs the supplier token issued when the company registered. Replaces any existing quote from this supplier for this RFQ, adds a thread entry and notifies the buyer by email and an optional callback; repeating the call sends notifications again. Only call with the supplier's authorization.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rfq_id | string | yes | — |
| supplier_token | string | no | Only if your client cannot send the Authorization: Bearer header |
| unit_price | number | yes | — |
| currency | string | no | 3-letter code, default EUR |
| quantity | integer | no | — |
| lead_time_days | integer | no | — |
| valid_until | string | no | YYYY-MM-DD |
| notes | string | no | — |
For a manufacturer's agent (needs the supplier token): the open quote requests your company was matched to, newest first, with readiness, whether you answered, your quote and unread buyer messages.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_answered | boolean | no | Default true |
| limit | integer | no | — |
| supplier_token | string | no | Only if your client cannot send the Authorization: Bearer header |
For a manufacturer's agent (needs the supplier token): one request in full — spec, what is missing, why you matched, file download links for your company, and the conversation so far.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rfq_id | string | yes | — |
| supplier_token | string | no | Only if your client cannot send the Authorization: Bearer header |
For a manufacturer's agent (needs the supplier token): write to the buyer of a request you were matched to — a question, an answer or an update, optionally with file_ids from upload_rfq_file. Draft it for the manufacturer and send only after they confirm.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| rfq_id | string | yes | — |
| body | string | yes | — |
| kind | string | no | — |
| file_ids | array | no | — |
| supplier_token | string | no | Only if your client cannot send the Authorization: Bearer header |
For a manufacturer's agent (needs the supplier token): what the directory stores about your company, and the allowed values for each field.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| supplier_token | string | no | Only if your client cannot send the Authorization: Bearer header |
For a manufacturer's agent (needs the supplier token): change processes, materials, certs, formats, industries, signals, machines, lead_time_days, min_order_qty, notes or notify_email. Fields you leave out keep their value; a field you send replaces it whole (a processes list replaces the stored list, so send the complete list, not only additions). Name, domain, country and address cannot be chang
| Parameter | Type | Required | Notes |
|---|---|---|---|
| processes | array | no | — |
| materials | array | no | — |
| certs | array | no | — |
| formats | array | no | — |
| industries | array | no | — |
| signals | array | no | — |
| machines | array | no | — |
| lead_time_days | integer | no | — |
| min_order_qty | integer | no | — |
| notes | string | no | — |
| notify_email | string | no | — |
| authorised | boolean | yes | — |
| supplier_token | string | no | Only if your client cannot send the Authorization: Bearer header |
- 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 Vibe Manufacturing 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 Vibe Manufacturing 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.