Phasio
Server Details
Quoting, pricing, production and part data for contract manufacturers (3D printing, CNC).
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 21 tools
Most tools target clearly distinct resources or actions, and the many describe/get tools are differentiated by their specific subject (data model, fields, pricing contract, production status, etc.). Minor overlap exists between query and aggregate and between publishEquation and save(entity=typescriptEquation) with isLive=true, but the descriptions generally steer selection correctly.
The set mixes several conventions: mostly camelCase verb_noun names (describeQueryableFields, getProductionHistory), bare verb names (aggregate, delete, query, save), and snake_case names (import_read, import_write). It remains readable, but the inconsistency prevents a fully predictable pattern.
At 21 tools the surface is slightly over the typical 3-15 range, but the server spans a broad manufacturing platform with distinct areas such as querying, pricing, production, configuration, and bulk import. Each tool appears to earn its place for that scope, though the count is on the heavy side.
Core lifecycle coverage is strong: datasets can be queried and aggregated, writable entities can be saved and deleted, pricing equations can be drafted, tested, and published, and production and configuration have dedicated read/diagnostic tools. Some gaps remain, such as direct create/update operations for orders/requisitions, full document-template editing, and write access to entities like discounts or shipping boxes.
Publisher details
- Operator
- Phasio
- Operator website
- https://phas.io · Publisher source
- Vendor relationship
- First-party
- Documentation
- https://docs.phas.io · Publisher source
- Privacy policy
- Not provided
- Trust center
- https://www.phas.io/security · Publisher source
- Restrictions
- Manufacturers will require a Phasio free trial or paid account
Available Tools
21 toolsaggregateARead-onlyIdempotentInspect
Aggregate a dataset: sum/avg/count/min/max of a field, optionally grouped by one or more fields, with an optional RSQL filter. Use this for cross-cutting questions like highest-value customers (aggregate order, sum, localPrice, groupBy=[customerOrganisationName], filter="state==ORDER") or revenue by process. Datasets that carry a voided/deleted flag exclude those rows by default (see the Scope line from describeQueryableFields); line-item datasets like requisition are NOT scoped by their parent order's status, so filter explicitly for placed-orders-only revenue. Datasets: order, partRevision, partSpecification, productionStep, customerOrganisation, cart, requisition, workOrder, processPrices, materialPrices, postProcessing, typescriptEquation, operationScheduling, operation, batchMovement, scrap, material, color, jurisdiction, leadTime, precisionPrices, infill, taxJurisdiction, taxComponent, paymentTerm, discount, shippingBox, shippingMethod, productionResource, routingTemplate, kanbanColumn, documentTemplate. Call describeQueryableFields(entity) for valid field names.
Inputs: entity (required), metric (required), sort, field, +3 more.
deleteADestructiveIdempotentInspect
Delete one row of a writable entity: leadTime, materialPrices, operation, operationScheduling, operatorSettings, paymentTerm, postProcessing, processPrices, productionResource, scheduleSettings, shippingMethod, taxComponent, taxJurisdiction, typescriptEquation. Irreversible. Each entity has its own refusals (see describeQueryableFields(entity)); e.g. a live pricing equation is refused.
Inputs: id (required), entity (required).
describeConfigurationARead-onlyIdempotentInspect
Describe the manufacturer's setup: a summary of processes, materials, finishing, tax, shipping and documents, plus the operator-level settings that have no dataset — storefront controls (login, order limits, invoice/PO, feature flags), currencies and exchange rates, accounting integration, contact details, permitted and email domains, payment information, onboarding progress, and the production schedule's setup (time zone, freeze window, resources and how each operation is planned). Pass 'section' to read one part. For row-level detail use query(entity=...); for problems in the setup use lintConfiguration.
Inputs: section.
describeDataModelARead-onlyIdempotentInspect
Explain the manufacturer's data model: what each query dataset means and how they relate (part -> specification -> requisition -> order, with production and pricing attached). Call this first to understand how to traverse between datasets.
Inputs: no named parameters.
describePricingEquationApiARead-onlyIdempotentInspect
Start here before reading, writing or changing a pricing equation. Returns the TypeScript contract the equation runs against (specification, revision, requisition, customer, workflow, done(), variable(), round, useDimension, createBands; for scope ORDER: parts, subtotal, customer, addLineItem), narrowed to the given scope + ownerId: its technology, material names and material variable names, lead-time names, and which modules the manufacturer has. Explains the loop: save(entity=typescriptEquation) to validate and store a draft, generateQuote(equationId) to test it, then — only on the manufacturer's explicit request — publishEquation to make it live. Pass includeSource=true to also get the live equation's source, or equationId= to get the source of one specific equation (a draft, for example) with its live/not-live state.
Inputs: scope (required), ownerId, equationId, includeSource.
describeQueryableFieldsARead-onlyIdempotentInspect
List the filterable fields (and enum values) for a query dataset, so you can build a valid RSQL filter. For a writable entity it also lists the fields save() accepts and what delete() refuses; for a write-only entity such as operatorSettings it lists only those.
Inputs: entity (required).
explainPriceARead-onlyIdempotentInspect
Explain why an existing requisition (order line) costs what it does. Recomputes its price from its actual configuration on the equation versions, material versions and settings it was quoted on, returns the price breakdown plus the pricing-equation variables behind it, compares it against the stored quotedPrice, and reports whether newer pricing is available. Individual pricing-equation variables can be manually overridden per line, so a returned variable value may be an override rather than what the equation would compute. To understand a price, examine these variables and reconcile them against describePricingEquationApi(includeSource=true) (the formula and how each variable is derived) and query materialPrices (by processPricesId + materialId, for the material's density and the rate values the equation reads off the material); a variable that doesn't reconcile with the equation and material rates has been overridden. For a hypothetical or what-if part, use generateQuote instead.
Inputs: requisitionId (required).
findSimilarPartsARead-onlyIdempotentInspect
Find the part revisions most similar in shape to a given one. Similarity is a geometric shape-descriptor distance: 0 = identical shape, up to ~1.414 = unrelated (cosine ~= 1 - d^2/2). It is rotation- and scale-invariant, so it matches shape/proportion and ignores absolute size and orientation — two parts of the same shape at different sizes score as very similar; use inspectPartRevision for real dimensions. As a rule of thumb distance < 0.05 is a near-duplicate. Requires the part revision's UUID (find one via query(entity="partRevision")). Needs a subscription to the PRO module.
Inputs: partRevisionId (required), limit, maxDistance.
generateQuoteARead-onlyIdempotentInspect
Price a part configuration on demand and return the price breakdown plus the pricing-equation variables that make up the price. Use for a part not yet ordered, or to test a change (different process/material/quantity, or override an input variable). Pass equationId to test a draft equation saved via save(entity=typescriptEquation); call once with and once without it to compare it against live. Purely a calculation — nothing is saved. To explain the price of an EXISTING order line, use explainPrice instead.
Inputs: quantity (required), processId (required), materialId (required), revisionId (required), +10 more.
getCustomerOverridesARead-onlyIdempotentInspect
Return the pricing configured specifically for one customer organisation, as opposed to the storefront defaults: customer-specific processes (with their bounding box and bulk quantities), material rates, precision and infill options, and catalogue price tiers on the customer's article references. Use it to answer 'does customer X have special pricing?'.
Inputs: customerOrganisationId (required).
getDocumentTemplateARead-onlyIdempotentInspect
Return one document template in full: its type, language, page size and the HTML content that is rendered for confirmations, invoices, estimates, traveller sheets or labels. List templates first with query(entity="documentTemplate").
Inputs: documentTemplateId (required).
getOnboardingProgressARead-onlyIdempotentInspect
Return the manufacturer's onboarding-wizard progress: each step (setup-processes, setup-pricing-equations, setup-post-processing, setup-tax-jurisdictions, setup-tax, configure-shipping, configure-payment-options, add-terms-of-service) with its status and completion time. lintConfiguration findings reference these step ids.
Inputs: no named parameters.
getProductionHistoryARead-onlyIdempotentInspect
What has happened to ONE requisition's parts in production: a chronological log of batch moves and scrap events (with the scrap reason), plus other requisitions that passed through the same build step as any scrap (i.e. parts impacted by the same failure). Find a requisition id via query(entity="requisition"). This is scoped to a single requisition — for scrap across the shop floor (totals, most common reasons, scrap by stage/operation, or over a time window) use query(entity="scrap") or aggregate(entity="scrap", ...) directly; do NOT loop this tool over requisitions. Needs a subscription to the FACTORY_FLOOR module.
Inputs: requisitionId (required).
getProductionProgressARead-onlyIdempotentInspect
Where a requisition's parts are right now: the quantity sitting at each production step/operation, in routing order. Find a requisition id via query(entity="requisition"). Needs a subscription to the FACTORY_FLOOR module.
Inputs: requisitionId (required).
import_readARead-onlyIdempotentInspect
Read import plans. action=operations: the operations and their args. action=plans: the plans of the account. action=plan (planId): status, counts, the first errors and the files to upload; for a batch, its queue and whose turn it is. action=errors (planId, page?): every operation with an error, 50 a page. See import_write for the workflow.
Inputs: action (required), page, planId.
import_writeADestructiveInspect
Import historic data into Phasio: companies, contacts, addresses, parts with their files, quotes and orders, and the history of an order: routings, production, shipments and messages. You resolve every ambiguity yourself: find existing rows with the query tools and name them {"id": "..."}; give each operation a key (the item's id in the source system) and name rows of this or an earlier import {"ref": ""}. Add operations in dependency order (a company before its address, a part before its order, an order before its production, shipments and messages). The user reviews each operation before the approval. Give an operation a note when the user must know why: for example why you matched an existing row, or what you assumed for a missing value. Workflow: action=create (title) -> action=add (planId, operations [{key, op, args, note?}], in parts; the same key replaces an operation) -> after the last add, action=split (planId): a large plan becomes a queue of batches, each a plan with its own planId, run in order; a small plan stays as it is -> action=dry_run (planId); a dry run splits a large plan on its own, keeps batch 1 under the planId and tests batch 1 only -> fix the errors with add or remove (planId, keys) and run again -> when the dry run has no errors, ask the user to review, approve and apply the plan in Phasio (Imports); you cannot approve or apply -> when the status is APPLIED (import_read action=plan), upload each file: POST a multipart form with the part "file" to its uploadUrl, with your bearer token. Upload ONE file at a time and wait for the answer; each CAD file starts an analysis. The limit is 20 uploads a minute; on HTTP 429 wait one minute. Only the user can undo an applied plan, in Phasio (Imports); you cannot undo. An undo is refused after the first file of the plan is uploaded: ask the user to confirm the applied plan before you upload. Batches: the answer of a batch names its queue and the batch whose turn it is (turn). Work only on the batch whose turn it is: dry-run it and fix it with add or remove on its own planId (a batch takes at most a tenth more operations than the batch size, room for fixes: IMPORT_BATCH_FULL); a later batch that names rows of an earlier one fails its dry run until the user applied that batch. import_read action=operations describes the args of each operation.
Inputs: action (required), keys, title, planId, +1 more.
inspectPartRevisionARead-onlyIdempotentInspect
Inspect a single part revision: returns its geometric metrics (volume, surface area, bounding box, minimum wall thickness, convex hull volume, watertightness) together with a single image showing the six orthogonal views (+X, -X, +Y, -Y, +Z, -Z) of the part, each cell labelled with its camera direction. Use this to answer any question about a part's geometry, manufacturability, size, or appearance. Requires the part revision's UUID.
Inputs: partRevisionId (required).
lintConfigurationARead-onlyIdempotentInspect
Check the manufacturer's setup for problems and report them by severity. BLOCKER = quoting or checkout cannot work (no process, no live pricing equation, a material missing an equation variable, no default tax jurisdiction, no shipping method, no payment path); WARNING = works but likely wrong (finish not offered on any process, jurisdiction with no components, no terms of service, unverified email domain, expired exchange rate); INFO = worth a look. Each finding names the onboarding step that fixes it and the entity involved. Call this first when asked whether the setup is complete or why quoting fails.
Inputs: level.
publishEquationADestructiveInspect
SENSITIVE — changes live storefront prices immediately. Makes a saved, validated draft typescriptEquation the LIVE pricing equation of its process, post-processing, or the order level; the previously live equation stops pricing at once, and every customer quote from now on uses the new one. Do this ONLY when the manufacturer explicitly asked to make this specific equation live, after generateQuote(equationId) on several real parts compared against the live price, and after telling them what will change. Never publish to 'try it out': generateQuote(equationId) tests a draft without publishing. Requires confirm=true and the id of the equation you are replacing (or NONE). Before this, a new draft prices nothing (lint PROCESS_NO_LIVE_EQUATION). Reversal: publish the previously live equation again with this tool. The same action is also available as save(entity="typescriptEquation", id=, data={isLive: true, replacesLiveEquationId, confirm: true}).
Inputs: confirm (required), equationId (required), replacesLiveEquationId (required).
queryARead-onlyIdempotentInspect
Query the manufacturer's live data with an RSQL filter. Datasets: order (Orders and quotes share the same entity. The state field distinguishes QUOTE, ORDER, and DRAFT. Payment status is independent: a placed PO/invoice order can remain UNPAID until settlement. 'price' is the order total in the order's own 'currency'; 'localPrice' is the same total converted to the operator's home currency ('localCurrency'). Sum localPrice (not price) to compare revenue across orders in different currencies. 'source' is the sales channel: INBOUND = placed by the customer through the storefront (self-service, online); OUTBOUND = created and sent out by the manufacturer's team (a staff-built quote). Filter or group by source to split self-service vs staff-created orders.); partRevision (Part revisions (a versioned 3D part). 'designName' is the manufacturer's INTERNAL name for the part design — not what the customer sees; when a user names a part they usually mean the customer-facing requisition.name, so prefer that for matching user references. Geometry detail is via inspectPartRevision.); partSpecification (Part specifications: how a part revision is to be made (process, material, finish).); productionStep (A stage in production: a build group of parts undergoing one operation (e.g. 3D Print, Post-Process, Quality Control). Parts move from step to step as they are manufactured. Needs a subscription to the FACTORY_FLOOR module.); customerOrganisation (Customer organisations (the manufacturer's customers).); cart (Storefront shopping carts (status OPEN, CONVERTED to an order, or DELETED). Use for conversion analysis.); requisition (Requisitions: a part specification ordered on an order (the order line item; carries quantity and pricing). 'name' is the CUSTOMER-FACING part name — this is what customers and users call the line, so match it when someone refers to a part by name (filter name=="...", or name-contains via RSQL). It is distinct from the manufacturer's internal partRevision.designName; the same physical part can have a different customer-facing name here. pricePaid is the actual per-line revenue in the parent order's currency; localPricePaid is the same in the operator's home currency (sum this for cross-order revenue). quotedPrice is the stored quote price; explainPrice recomputes on the versions and settings it was quoted on and reports pricing freshness.); workOrder (Work orders: production execution for a requisition (quantity to build, routing template). 'steps' is the ordered list of operations this work order will go through on the shop floor (its routing) — read it to know what will be done to build this order. Needs a subscription to the FACTORY_FLOOR module.); processPrices (Manufacturing processes and their pricing configuration. 'pricingAlgo' says how a process is priced: TS_EQUATION processes use a TypeScript pricing equation (activeTypescriptEquationId; read it with describePricingEquationApi(includeSource=true)); any other value is a legacy built-in algorithm with no equation to read. The row folds in the process's setup: boundingBox (max part size L x W x H), bulkQuantities (the quantity breaks shown for bulk pricing), materialVariables (the per-material variable names the equation reads), and counts of materials, post-processings, precision and infill options. isInternal processes are hidden from the storefront. A row with a customerOrganisationId is a customer-specific copy of a process.); materialPrices (A material's pricing configuration for one process (a process x material pairing). Carries the material (materialId/materialName), its density, and 'variables' — the material's TypeScript-equation variable values (operator-defined name=value pairs the pricing equation reads off the material). Use to see a material's rates without reverse-engineering them from quotes: filter by processPricesId and materialId (both from partSpecification). The 'variables' text isn't itself filterable — filter on materialId/processPricesId/density/isDefault instead. Rates are process-specific, so the same material can appear once per process.); postProcessing (Post-processing / finishing options the manufacturer offers (e.g. painting, polishing). 'type' says how it is priced: TS_EQUATION ones have their own TypeScript equation (activeTypescriptEquationId; read it with describePricingEquationApi(scope=POST_PROCESSING, ownerId, includeSource=true)); any other type is a legacy built-in formula with no equation to read. 'processes' lists the processes it is available on, 'operations' the shop-floor operations it adds, 'colors' its colour choices and 'incompatibleMaterials' the materials it cannot be applied to. Options sharing a mutuallyExclusiveGroup cannot be combined on one part.); typescriptEquation (TypeScript pricing equations (metadata only — describePricingEquationApi(includeSource=true) for the live source). 'scope' is PROCESS (processPricesId), POST_PROCESSING (postProcessingId) or ORDER (the operator's single order-level equation that adds whole-order line items; both ids null); 'isLive' tells whether it is the one currently used for quoting. Several draft equations can sit next to the live one; 'origin' is UI or MCP (written through save) and 'createdBy' the authoring user.); operationScheduling (How the production schedule runs each operation (one row per operation, the completed one excluded; 'id' is the operation id). 'needs' are the machines or people it holds at the same time (none = a wait such as cooling); 'batching' is how parts go through: NONE one work order at a time, VOLUME builds filled by part volume (usableVolumePercent of each machine's build volume), COUNT batches of partsPerBatch, KEEP_PREVIOUS the build from the operation before stays together. A build or batch starts when its machine is free unless it is below minFillPercent; then it waits for more parts, at most maxWaitHours. Time is durationHours per job or batch, or setupMinutes + minutesPerPart per part. runsUnattended: only the start must be in open hours. 'problems' are what the plan would warn about. Needs a subscription to the FACTORY_FLOOR and SCHEDULING modules.); operation (Manufacturing operations (shop-floor stations) in 'sequence' order, e.g. 3D Print, Post-Process, Quality Control. Parts move operation to operation; batches moved at an operation are grouped into production steps (build groups). Column meanings: productionStepType is the station kind — BASE (a normal station), DOWNLOAD_PARTS_AS_GROUP (parts are downloaded as one build file), UPLOAD_THREED_NESTED (a nested build / bill of parts is uploaded), QUALITY_CONTROL (inspection; scrap is recorded here). viewType is the backlog's default view at this station: PART lists individual parts, BUILD lists build groups. buildConstraint says which parts may share one build group: NONE, MATERIAL (same material), MATERIAL_AND_COLOR, MATERIAL_AND_SHEET_THICKNESS. stepNamePrefix + stepNamingStrategy control how a new build group is named when a batch arrives: ALWAYS_RENAME (new name every time), RENAME_IF_BUILD_CHANGED (new name only when the build composition changed), INHERIT_FROM_PREVIOUS (keep the previous station's group name). allowOverproduction lets staff move more parts than the ordered balance. durationHours is the planning estimate for time spent at the station. isCompletedStatus marks the station whose exit means the part is finished. automations run when staff progress parts here (NOTIFY_ON_ORDER_COMPLETED). Referenced by productionStep.operationId and scrap.operationId. Needs a subscription to the FACTORY_FLOOR module.); batchMovement (Forward batch moves through production: each row is a batch of parts ADVANCING from one operation to the next (throughput). Scrap events are NOT here — see the scrap dataset for those. 'batchSize' is the quantity that moved; 'operationName' is the operation the batch left; 'toOperationName' is the one it moved to. Filter by createdAt for a time window or requisitionId/workOrderId for one job. For a SCRAP RATE by operation, aggregate sum(batchSize) here grouped by [operationName] (the parts that passed) and aggregate scrap the same way (the parts scrapped); rate = scrap / (scrap + moved) at each operation. Needs a subscription to the FACTORY_FLOOR module.); scrap (Scrap events: parts scrapped as they move through production. This is the floor-wide scrap log — query or aggregate it DIRECTLY for any scrap question; do not gather scrap by iterating requisitions or getProductionHistory. 'reason' is the free-text scrap cause; 'batchSize' is the quantity scrapped; 'operationName' is the operation the scrap happened at; filter by createdAt for a time window or requisitionId/workOrderId for one job. To find what causes the most scrap, aggregate sum(batchSize) grouped by reason (or operationName). For a scrap RATE you also need the parts that passed — aggregate the batchMovement dataset by operationName and divide. Needs a subscription to the FACTORY_FLOOR module.); material (The material catalogue (platform materials plus the manufacturer's own). Rates are NOT here — a material only has prices once it is paired with a process; query materialPrices (materialId==) for those.); color (Colour options. Each colour belongs to one materialPrices row (a material on a process) or to one post-processing; 'kind' says which and the matching *Id column points at the parent.); jurisdiction (The platform's tax-jurisdiction catalogue: every code a taxJurisdiction can be created for, with its name and country. Platform reference data, identical for every manufacturer (not tenant data). Use it to find the isoCode for save(entity="taxJurisdiction"): filter by country (the Country enum name, e.g. GERMANY) and read the region names; DEFAULT and EXEMPT are the two special codes.); leadTime (Lead-time options offered at checkout. 'buffer' is the number of days added to the production estimate; the default one is pre-selected on the storefront and read by the pricing equation.); precisionPrices (Precision / tolerance options sold per process, each with a price adder. A row with a customerOrganisationId is a customer-specific override of the base option.); infill (Infill options per process (FDM-style density presets). 'infillValue' is the fill percentage; the default is pre-selected on the storefront. A row with a customerOrganisationId is a customer override.); taxJurisdiction (Tax setup per jurisdiction (country / region). 'components' lists the tax components applied (name and percentage) and 'totalPercentage' their sum. The DEFAULT jurisdiction is the fallback when a customer's address matches nothing; EXEMPT is used for tax-exempt customers.); taxComponent (Reusable tax components (e.g. VAT 19%) that jurisdictions combine. See taxJurisdiction.components for where each is applied.); paymentTerm (Payment terms offered to customers (e.g. Net 30). accountingSystemTermId links the term to the connected accounting system.); discount (Discounts: GENERIC (a code any customer can use), CUSTOMER (a code for one customer) or INSTANT (applied automatically). Active means endTime is in the future.); shippingBox (Shipping box sizes used to pack orders (dimensions in unitBasis).); shippingMethod (Shipping methods offered at checkout. shippingMode is FIXED_PRICE (flat price, optional weight tiers and a country list), CARRIER_ACCOUNT (live rates from the manufacturer's carrier account) or SELF_COLLECTION (pick-up). Tier and country detail is folded into the row.); productionResource (The machines, people and stations the production schedule seats work on. 'capacity' is how many jobs it holds at once; 'buildVolumeCm3' is set on machines that run many parts as one build (an MJF or SLS printer); 'tags' are its skills, which an operation can ask for; 'openHours' are its weekly hours in the shop's time zone ("always" = no limit). Which operations use it: describeConfiguration(section="scheduling"). Needs a subscription to the FACTORY_FLOOR and SCHEDULING modules.); routingTemplate (Routing templates: the ordered operations a work order goes through. 'steps' is the sequence of operation names. A template can be generic or bound to one partSpecification. When the storefront setting isApprovedRoutingTemplateRequired is on, only approved templates can be used. Needs a subscription to the FACTORY_FLOOR module.); kanbanColumn (Order-board (kanban) columns in display order. 'automations' lists what fires when an order enters the column (NOTIFY_CUSTOMER_OF_NEW_STATUS, SEND_INVOICE, SEND_ORDER_CONFIRMATION).); documentTemplate (Document templates (order confirmation, invoice, estimate, traveller sheets, labels) per language. Metadata only — use getDocumentTemplate(id) to read the HTML content.). Operators: == != =gt= =ge= =lt= =le= =in=(a,b) =out=(a,b); combine with ';' (AND) and ',' (OR). Each row is returned as 'field=value' pairs and always includes its id and foreign keys (the join keys); pass 'fields' to select specific columns (any field from describeQueryableFields). Call describeDataModel to see how datasets relate, and describeQueryableFields(entity) to learn a dataset's filterable fields.
Inputs: entity (required), sort, limit, fields, +1 more.
saveADestructiveInspect
Create (no id) or update (with id) one row of a writable entity: leadTime, materialPrices, operation, operationScheduling, operatorSettings, paymentTerm, postProcessing, processPrices, productionResource, scheduleSettings, shippingMethod, taxComponent, taxJurisdiction, typescriptEquation. Field list and rules per entity: describeQueryableFields(entity). Some updates change live behaviour at once (e.g. overwriting a live pricing equation); the reply says when that happened.
Inputs: data (required), entity (required), id.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Quotes, orders, manufacturing orders and invoices for contract manufacturers and their clients.
Instant parametric cost estimates for custom manufacturing: CNC, molding, sheet metal, 3DP, PCB.
Price CNC and sheet metal parts from STEP models or PDF drawings at your job shop's own rates.
Manufacturing cost of CNC and sheet-metal parts from STEP or DXF: process plan, times, 10 lot sizes.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceIntelligently generates cost estimates and lead times for manufacturing RFPs by parsing requests, matching against historical quotes, and calculating activity-based costs with confidence scoring and human approval workflows.MIT

Cliff MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables MCP clients to search hardware parts, save STEP files for CAD tools, upload and decompose models, and obtain machining quotes, priced BOMs, and human-reviewed checkouts via its API.Apache 2.0- FlicenseAqualityBmaintenanceCross-OEM industrial machine intelligence. Normalizes telemetry across 16 manufacturer families (Fanuc, Siemens, Haas, DMG Mori, Mazak), enables plain-English operational automation, and produces tamper-evident work records. 14 MCP tools.14-
- AlicenseAqualityCmaintenanceMCP server for real FDM 3D-printing slicing, quoting, and design-for-manufacturability analysis via the FabTally API, supporting 12 printer profiles and 12 materials. Includes free discovery/printability tools and paid slice/quote/orientation tools settled via x402 (USDC on Base).6MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.