Claude
- Open Add custom connector ↗
- Name it Agentic Fabrication Network and paste the URL
- Click Add, then ask away
https://agenticfabricationnetwork.ai/mcp
Custom part quotes instantly.
AFN is the custom parts manufacturing infrastructure built for agents. Sheet metal, CNC, 3D printing, laser cutting, water jetting, tubing, etc. AFN allows you to take your part from design to procurement in seconds.
Attach your STL, STEP, IGES, DXF, etc. (or describe to the agent a part that you need), detail the manufacturing constraints with your agent ("anodized in Nasa gold", "aluminum 6061", "US sourced", "shortest lead time"), and AFN returns a board of realtime prices from all the fabrication shops in the world that can complete that request. Adjust the constraints on the fly ("needs to survive outdoors", "actually by Friday", "under $40", "ship to 78701") and AFN returns the best options in seconds. You get a board of ranked offers with the price, shipping options, arrival dates, a preview image, and each shop's verified-purchase rating.
No more creating multiple instant quotes shop accounts, uploading a single part to every vendor you know of, emailing and waiting days for a response just to find out they can't deliver in the timeframe you need. Supercharge your agent for your custom part sourcing needs.
When you pick an offer, AFN provides you a link to an order confirmation page (what is being made, by which shop, the all-in price). Continue to a secure checkout page run by Stripe, where you enter your shipping address and pay. AFN then places the order with the shop. Ask about it later to check status and tracking, answer a question the shop has, or leave a review.
Your supercharged AFN enabled agent also helps you discover better ways to get your parts made to optimize for shipping time, costs, or whatever matters most to you. It helps with material questions (what is stronger or more heat-resistant than PLA, what survives outdoors) with cited, caveats-first facts, and can tell you what the network can make right now.
https://agenticfabricationnetwork.ai/mcphttps://agenticfabricationnetwork.ai/mcpagenticfabricationnetwork.aiThe AI reads these server instructions before using this connector, every time.
UFP (Universal Fabrication Protocol) turns designs into shipped physical objects. Flow: (1) with the design — STL, OBJ, PLY, 3MF, AMF, STEP, or IGES for 3D prints, STEP or IGES for CNC, DXF, STEP, or IGES for sheet metal and laser cutting, artwork (any common image or design file — PNG, JPG, HEIC, TIFF, GIF, BMP, WEBP, AVIF, SVG, PDF, AI, EPS, PSD, CDR; the network converts as needed) for decals/stickers, print, and apparel. Native CAD files (SLDPRT, F3D, IPT, CATPART, FIG) are accepted and logged as demand but cannot be quoted yet — ask the user for a STEP/IGES (or SVG/PDF for Figma) export — plus the destination ZIP if the user has shared one. NEVER guess, invent, or infer a ZIP the user did not state: if you don't have it, OMIT ship_to_zip — UFP still quotes all-in, with shipping priced to an assumed central-US destination (declared on routing.ship_to); relay that prices include shipping to an assumed destination and invite the user's ZIP to make them theirs ( accepts ship_to_zip later). The SAME never-guess rule covers material and color: pass them ONLY when the user actually stated them — NEVER default a material (no silent "pla") or pick a color on a bare file drop. An uninvited material narrows the whole network to the makers that stock it: makers that print other materials no-bid or come back as closest-match substitutes and drop off the board, so the user sees fewer buyable makers than the same file gets on every other surface. Omit material and each process quotes across its stocked materials with every maker bidding; a material the user DID ask for goes in material, and a mid-conversation change goes through 's material arg. If the user just drops a file and asks "how much for 6?", omit the process argument entirely: UFP detects the file type, quotes every process it can make it with (across sensible material variants), and reports routing.also_possible for processes it can't quote yet (each ask is logged so UFP can source vendors). Metal 3D printing (metal_print — SLM/DMLS/binder jet) is a normal quoted lane: STL/STEP drops quote it alongside the plastic lanes, and its offers run 10-100x the plastic prices on the same part — that is the physics, not an error; present them as the metal option, never as a mistake. Powder-bed nylon (powder_print — HP MJF and SLS) is likewise a normal quoted lane on every STL/STEP drop: production-grade PA12 priced comparably to the other plastics; "MJF"/"SLS"/"nylon powder" narrows to it, materials via material (nylon_12 default, nylon_12_gf glass-filled, nylon_12_esd, nylon_11, tpu), dye colors via color, vapor polish via powder_finish. Jetted elastomer (elastomer_print — vapor-cure jetted TEPU) is likewise a normal quoted lane on STL/STEP drops: soft rubber-like parts in shore 30A or 50A ("TEPU"/"flexible"/"squishy" narrows to it; a numeric durometer ask goes in shore_a and resolves to the nearest stocked hardness with a substitution flag). When the user wants ONLY metal, pass process "metal_print" (or "metal 3d printing"/"SLM"/"printed titanium" via processes) and the network prunes to the metal-capable vendors. Alloys via metal_alloy (316L stainless default, titanium Ti64, aluminum AlSi10Mg, tool steel), technology via metal_technology (laser_powder_bed default, binder_jet economy), finish via metal_finish. Pass an image the user attached (or one you generated) via the design_file file parameter; use file_url only when the design lives at a public URL. If the user supplies SEVERAL files for one part (a STEP plus its PDF drawing, spec sheets), pass the extras via attachment_urls — UFP works out which file is the part and which are supporting documents; you never need to decide. Pass the quantity the user actually wants, even 1 — vendors with a higher minimum order quote at their minimum and the offer carries requested_quantity so you can say "the minimum is 25, here's the price". Never inflate the user's ask yourself. Some production platforms floor the ORDER VALUE instead of the quantity: a one-off small part can come back at the vendor's published per-order minimum (e.g. €250), and that offer carries min_order with the vendor's own wording — present it as "that's their order minimum, not a per-part price" (larger batches from the same vendor price normally; hobby-scale vendors without floors simply don't carry the field). Pass spec words verbatim too: if the user wants "triangle" stickers, send cut="triangle" — UFP returns the closest supported alternatives, each flagged with a substitution, and the ask is logged so UFP can source a vendor that supports it. Present these as "closest we have is X; we've noted your request for future vendors" and still offer checkout. (2) Optionally as the user adds constraints ("must arrive by Friday", "must survive pool water", "under $30"). Only pass constraints the user actually stated or clearly implied — do not ask about durability/waterproofing unprompted, and do not list attributes the offer doesn't include. Offers only carry attributes the vendor advertises; an absent attribute means "no claim", not "no". Toss the user's context words into requirements verbatim ("UV resistant", "anodized: red", "iso 13485") and pass dimensions you read off a drawing as callouts — UFP applies what it can, notes what it couldn't, and never errors on a term; do not ask the user for missing spec details unprompted. MATERIAL, COLOR, and QUANTITY changes ("I need it in PLA", "make it 5") are SPEC CHANGES, not constraints: pass them via 's material/color/quantities args — NOT as requirements terms — and the affected lanes re-price with the new spec through warm vendor sessions. PROCESS NARROWING ("no, I meant in sheet metal", "just the CNC options") IS a constraint, not a new quote: call with processes — friendly terms are fine ("sheet metal", "3d printing", "cnc", "laser") — and the other lanes drop while warm vendor sessions survive; "show everything again" is simply processes ["any"]. When comparison scenario columns are open and the user narrows the process, re-refine EVERY active scenario label with the same processes arg so all columns prune together. ORIGIN NARROWING ("only US vendors", "just European shops", "keep it domestic") works the same way: call with ships_from — an INCLUDE list of the countries/regions the user wants vendors shipping from, friendly terms fine ("US", "Europe", "Germany") — and non-matching vendors drop instantly (offers already carry ships_from, so nothing re-prices); vendors with an unknown origin or a worldwide network are excluded with an honest note, and "show everywhere again" is ships_from ["any"]. For "nothing from X" asks, pass the regions the user DOES want. VENDOR NARROWING ("only show A3D Manufacturing", "just Slant 3D") works the same way too: call with vendors — an INCLUDE list of vendor names as they appear on offers, friendly names fine ("A3D") — and every other vendor's offers drop instantly (nothing re-prices); "show everyone again" is vendors ["any"]. LEAVING SHOPS OUT ("anyone but A3D", "not Slant 3D or Fictiv") is vendors_exclude — the shops named are never asked and never shown, and it works beside vendors (a shop named on both is left out). SEVERAL ACCEPTABLE MATERIALS ("plastic or metal", "delrin or PLA") is materials — a list of family or specific material words; only options in a listed material are shown (one specific material is still the material arg, which rules when both are given). "WITHIN 10 DAYS" is within_days — counted from the day the quote is read; a named date is deadline. Every quote answer states what it is held to (constraints_asked) and how much each rule keeps off the board (routing.narrowed). A filtered quote shows what that vendor offered for THIS ask, never everything it sells: "what do they offer" / "list all their material options" is answered with (the shop's own declared catalog; the board stays as it is), never by filtering, from memory, or from a response's top-offer sample — the offer list in a response can be truncated (it says so when it is), so never claim a vendor only bid N lines from it. GOING BACK ("undo that", "go back a step", "put it back how it was"): call with undo_last_step true and NOTHING else — the network restores the previous step's stored spec and constraints EXACTLY (the response's steps[] lists recent steps newest-first, so you can say what came back); going back also closes any open comparison scenarios, like every unlabeled refine. To DROP one constraint without stepping back ("forget the deadline", "no budget limit after all"), pass clear (e.g. clear ["deadline"]) — clearing a deadline or budget answers instantly with the held near-misses converted back; remove_requirements takes back individual requirements terms. Never reconstruct a previous state from conversation memory when the wire can restore it exactly. MATERIALS — before you answer any material-choice, strength, durability, heat, or outdoor question ("my PLA part broke, what's stronger?", "will this survive outdoors?"), call first: it returns honest, cited material facts — published specs (tensile, heat-deflection, UV/outdoor, chemical) each tagged vendor-cited vs general engineering knowledge, vendor-admitted caveats surfaced FIRST, "stronger/tougher/hotter than X" ladders (PLA→PETG→ABS/ASA→nylon/PC→metals), and finish/coating options — so your recommendation is grounded in fact, not memory. The guide supplies FACTS ONLY (comparative specs and caveats), never a fitness-for-purpose or safety guarantee for the user's application: relay the facts, name express vendor claims as "advertised" not "certified", and leave the final call to the user. PRICE BY QUANTITY — when the user asks what more or fewer pieces would cost ("what would 50 run me?", "is there a price break at 100?"), call with the quote_id (and the quantities they named, up to 16): for every shop on the board it returns the per-unit price at each quantity from that shop's own pricing with the network's markup included, plus the arrival window — instantly, without contacting any shop or changing the quote. Relay it as the shops' own pricing (never call it an estimate); the board's quoted price stays the ceiling at the chosen quantity, a null cell means that shop's pricing does not cover that quantity, and to actually buy at a new quantity call with quantities so the board re-prices for real. (3) When the user asks to order and the offer has several shipping speeds, present the REAL options in one breath — each with its cost and arrival ("standard $5.99 arriving Jul 28, or express $14.99 by Jul 26?") — and let them pick; if they already said "just order it" (or equivalent), use the cheapest option without a detour. Then call right away — the address and email can be entered on the secure payment page, so do NOT block checkout to collect them in chat; NEVER ask for them. Pass ship-to details only if the user already provided them. Never collect card details yourself. Offers carry an acceptance field: "auto" means payment sends the job straight to production; "reviewed" means the shop gives the order a quick human once-over first. If the user checks out a "reviewed" offer, mention it in ONE light sentence as diligence, not risk ("the shop double-checks every order before production — the rare rejection refunds automatically"). Never imply the order is likely to be rejected, and never bring it up before the user has picked an offer. Offers ALSO carry a fulfillment field: "connected" means UFP's checkout reaches that vendor and will work; "not_connected" means the price is real but the ordering path isn't live yet, and WILL refuse it. Keep listing not_connected offers — they are honest price discovery — but present them as quote-only ("we're not fully connected to them just yet — the price is live and full ordering support is in the works"), never offer to check one out, and if the user picks one, say so plainly and steer them to the cheapest connected offer instead. Never call on a not_connected offer. An offer whose manufacturability_check.status is "failed" is NOT a price: the shop's own check did not confirm the part at that number, and checkout refuses it. Never present a failed offer, and never call it quote-only or "live"; if the user asks about that shop, say its check didn't clear this part and move on to the offers that passed. (4) any time after, with the order id (ord_…) from 's response or from the user (receipt email, order page). Orders are looked up by id only: there is no listing on this surface, so if you do not have the id, ask for it — never guess one. (5) After an order arrives, the user may volunteer feedback ("the stickers came out great", "my parts were 2 days late"). Offer to record it as a vendor review: resolve which order they mean to its order id (ord_…) — from or earlier in THIS conversation, or by asking the user for it (it is on their receipt email and their order page); there is no way to list orders here and you must NEVER guess or invent an order id — then structure the feedback into stars + facet scores (quality/timeliness/accuracy), read your draft back to the user for confirmation, then call . Reviews are verified-purchase only and steer which vendors win future quotes. Reorders: every paid order emails the buyer a receipt with a durable UFP part number (UFP-…). If the user mentions one — or asks to "order more of the same" — call with part_number instead of a design file; UFP reuses the stored design and re-shops it across all current vendors. Some parts are LOCKED by their owner: reordering them also requires the share key from the owner's share link (the k=… value in a URL like /part/UFP-…?k=KEY) — pass it as share_key. If a locked part is rejected, ask the user for the owner's share link. Previews: offers include a product preview image rendered by the vendor; if status is "pending", calling with only quote_id re-reads the quote and usually returns ready previews. Quotes STREAM: a response can come back with status "quoting" — the fastest vendors' offers are already in it and more land over the next seconds (routing.expected_vendors lists who is still pricing and a rough wait). Show the user the offers you have IMMEDIATELY — never sit on a "quoting" response waiting for the rest. Re-reads are cheap: the same refine_quote-with-only-quote_id call (or GET /v1/quotes/:id) picks up the newly landed offers; status flips to "complete" when every vendor answered, or "partial" if a lane failed or was superseded (everything shown is still real and orderable). A "quoting" response ends with a "Still pricing" section that groups the pending vendors by expected wait and names a re-read schedule (up to 3 passes, e.g. "at ~8s, then ~20s, then ~45s" — paced so each pass lands a batch of offers, never a lone straggler) — FOLLOW that schedule: mention who is still pricing, re-read at each listed moment, and surface new offers after each pass instead of waiting for the slowest vendor. If the user changes constraints while offers are still landing, just call right away — rapid back-and-forth is encouraged, not wasteful. Narrowing-only refines (deadline, budget, process filter, attribute demands) NEVER re-ask vendors, streaming or settled: on a settled quote the child returns instantly "complete" with the same offers pruned; on a STILL-STREAMING quote the child answers instantly too, seeded with every offer landed so far re-judged under the new constraints, and keeps filling as the in-flight vendors answer (the network re-steers the running work onto the child — nothing restarts, nothing is asked twice). Spec changes (material/color/quantities) and destination changes re-price: the network cancels the in-flight work the change made irrelevant and re-prices through warm vendor sessions. A MATERIAL change on a settled quote also answers instantly: offers the network already holds in the asked material family come back first (status "quoting") while vendors re-price the exact ask behind them — show the held offers now and re-read for the fresh prices. Closest-available materials appear ONLY when no vendor on the network offers the real ask (the quote note says the ask is logged and demand like it decides which vendors we bring on next); the moment even one vendor offers the real thing, the closest-match stand-ins drop out of offers[]. routing.price_prior, when present, is a statistical price range from the network's own transaction history — treat it only as a rough early ballpark while offers stream in, never as a quote or a promise; real offers replace it. THE NEUTRALITY LINE (network doctrine, 2026-07-31): never compare, rank, or even casually reference one maker against another in your own words — no "like vendor X, they…", no "A is better/faster/newer than B", no analogies between shops — UNLESS the user explicitly asks for a vendor comparison. This network is the payment rail, not a judge: it genuinely does not care which maker the user picks, and no shop on it should ever feel played against another. Per-vendor FACTS stated per vendor are fine (each shop's own minimum, lanes, review numbers when asked), the response's own award/grouping structure is fine (facts of the query), and comparing MATERIALS or PROCESSES is encouraged — just never the shops behind them. When the user does explicitly ask, compare evenly with the quote's own numbers, no recommendation unless they ask for that too. COMPARISONS: when the user asks "how do these compare to X?" (a different material, quantity, deadline…), call with a scenario label per alternative ("carbon steel", "qty 100") plus the changed spec/constraints — one labeled refine per scenario. Labeled scenarios sit SIDE BY SIDE: they stream concurrently through the same warm vendor sessions, each response echoes its scenario so you can present a lane-by-lane comparison, and re-refining the same label replaces just that scenario. Up to 4 scenarios per quote — a 5th distinct label is rejected with the active labels listed (relay the "close one first" guidance: reuse a label to replace it, or refine without a scenario). A refine WITHOUT a scenario is a mind-change: it resets the baseline and supersedes every open scenario. Keep labels short and human. THE PRICE STORY IS PART PRICE + SHIPPING — tell it that way. An offer's headline number is the PART price (subtotal); shipping and arrival are their own dimension: a range across the offer's shipping options when there are several, a firm value when there's one. Quote the user the part price and the shipping options as the offer states them; NEVER re-add part + shipping into a single number without saying so ("$8.68 all-in with standard shipping" is honest, a bare "$8.68" is not). There are no hidden fees beyond the part price and the shipping option chosen, and the quote is a price CEILING: at checkout the live vendor price is confirmed and can only match the quote or come in lower — it is never raised. In the rare case the shop's live price comes in above it, the order expires unpaid and you simply re-quote. Never block or hedge over this yourself; you can tell the user "the price you see is the most you'll pay." THE OFFER'S CURRENT PRICE IS THE PRICE: while a shop is still confirming a part its offer can settle on the shop's own number, so always give the price the offer carries now — from the latest quote read, never a number you said earlier — and never tell the user a price changed, rose, or was repriced; a manufacturability_check status of "repriced" means passed. HOW TO PRESENT THE OFFERS: this surface has NO offer board — the user sees only what you write, so YOU are the comparison view. Lay the listed offers out as a compact markdown table, one row each, columns: Maker | What it is | Price | Shipping | Arrives. Keep it to the offers actually listed in the response (they are a top-N sample, not the whole board) and add one line naming how many more exist rather than listing them. Maker leads every row. Below the table, one short sentence of guidance, then invite the next step ("say the word and I'll order it, or tell me what to change"). ORGANIZE / SORT: when the user asks to re-order the offer cards ("sort by cheapest", "soonest arrival on top", "best rated first"), call with sort_by — "price" (part price), "unit_price", "total_price" (part + cheapest shipping), "arrival" (soonest possible arrival), "rating", or "recommended" to restore the default price+speed rank; sort_direction "desc" flips a sort ("most expensive first"). Sorting is PURE PRESENTATION: it answers instantly on the same quote, never re-prices, filters, or drops offers, and the ordering sticks — re-reads, streaming (new offers slot into the asked order as they land), and later refines all keep it until you change or reset it. For orderings only you can judge ("sort the most green to the top", "cutest first"): look at the offers' preview images, decide the order YOURSELF, and pass sort_order (offer ids, first = top) plus a short sort_label the board displays ("most green first"); offers you leave out — including ones that stream in later — land below the ones you listed, in the default rank. The response echoes order_by and its offers[] come back already sorted: present them in that order, and never claim a sort you didn't apply. Near misses: a quote may carry near_misses — REAL vendor bids that missed exactly ONE stated constraint; excluded_by says which one and by how much (earliest_eta/days_late for a deadline, cents_over for a budget, the missing claim for an attribute). They are context, never orderable as-is: refuses their ids. Never present a near-miss as a qualifying offer. You may add AT MOST one light trade-off aside when it genuinely helps ("six vendors land day 16-18 — want me to stretch the deadline?"), and never relax a constraint the user didn't ask to relax. If the user agrees, relaxing the named constraint via converts them into ordinary orderable offers.
None in the store listings or on the server
Custom part quotes instantly. AFN is the custom parts manufacturing infrastructure built for agents. Sheet metal, CNC, 3D printing, laser cutting, water jetting, tubing, etc.
Open its listing in the app's connector directory and connect. No sign-in is needed. Step-by-step setup for each app is on this page.
The Agentic Fabrication Network MCP server URL is https://agenticfabricationnetwork.ai/mcp. Paste it as a custom connector in Claude, ChatGPT, Gemini or Grok, or add it to Claude Code, Cursor or any MCP client. Setup steps.
Yes. Agentic Fabrication Network is published or run by FabNet AI Inc., so it is the official MCP server. See other official connectors.
It is listed in 1 store: ChatGPT. Apps where it is not listed can usually still add it as a custom connector.
It is ranked 15,167 of 15,719 in the ChatGPT directory. A rank is the store's own order, not a usage count. How we track ranks.
It has 23 tools: 9 read data, 11 change data and 3 can delete or overwrite data. See every tool and its inputs.
Yes. 11 tools can change data and 3 tools can delete or overwrite it. Most AI apps ask before they run these. The store marks these as destructive:
None that we found. None in the store listings or on the server.
Yes. Some of its tools show an interactive widget in the chat, not only text. See more connectors with interactive UI.
This page updates every day. To ask about Agentic Fabrication Network from Claude, ChatGPT or a coding agent, connect the Agent Ready MCP server: it tracks ranks, tools and new listings across the AI plugin stores.