Bambu Printer MCP vs Dxpert.ai — industrial AI Readiness & UNS agents
A side-by-side look at the Bambu Printer MCP and Dxpert.ai — industrial AI Readiness & UNS agents MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Bambu Printer MCP for industrial & iot work as a local process; choose Dxpert.ai — industrial AI Readiness & UNS agents for industrial & iot as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Bambu Printer MCP when
- You need dedicated capabilities in the Industrial & IoT domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
PRINTER_HOST, BAMBU_MODEL, BAMBU_SERIAL, BAMBU_TOKEN. - You want tools like
get_printer_status, get_printer_filaments, resolve_3mf_ams_slots.
Choose Dxpert.ai — industrial AI Readiness & UNS agents when
- You need dedicated capabilities in the Industrial & IoT domain.
- You prefer a local stdio subprocess transport.
- You want tools like
ask_dxpert, run_agent, run_diagnostic.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Industrial & IoT | Industrial & IoT |
| Quality signal | 71/100 · Great | 61/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | PRINTER_HOSTBAMBU_MODELBAMBU_SERIALBAMBU_TOKEN | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 234 | 0 |
| Directory activity | 9 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 46 | 7 |
| Full listing | View Bambu Printer MCP | View Dxpert.ai — industrial AI Readiness & UNS agents |
Tools & capabilities
Bambu Printer MCP tools 46
get_printer_statusGet the current status of the Bambu Lab printerget_printer_filamentsGet the live AMS/external filament inventory from the printer over MQTT, including loaded/empty slot summary, resolved slicer profile paths, match confidence, and recommended load_filaments when the printer model is known.resolve_3mf_ams_slotsInspect a sliced 3MF and match its tray_info_idx filament requirements against the live AMS inventory. Does not upload or start a print.list_3mf_plate_objectsList object IDs from a sliced 3MF plate. Use these IDs with skip_objects during a running print.extend_stl_baseExtend the base of an STL file by a specified amountscale_stlScale an STL file by specified factorsrotate_stlRotate an STL file by specified angles (degrees)get_stl_infoGet detailed information about an STL file (bounding box, face count, dimensions)list_templatesList saved slicing templates from the local template registry directory.save_templateCopy a 3MF, JSON, or config file into the local template registry and register it under a template name.get_slice_settingsInspect slicer settings from a saved 3MF template or a JSON/config slicer profile without slicing anything.slice_with_templateSlice an STL or 3MF using a named template from the local registry. This is a higher-level wrapper around slice_stl for template-based workflows.- +34 more on the listing page
Dxpert.ai — industrial AI Readiness & UNS agents tools 7
ask_dxpertAsk dxpert.ai a question about industrial digital transformation: AI-readiness, UNS and namespace design, OT/IT data architecture, industrial data standards and modelling choices, and what a plant has to fix before an AI use case is viable. Calls POST /api/chat and returns a text reply plus routing metadata. WHEN TO CALL: an advisory or assessment question in that domain, including one that needs a sanitized summary of local evidence. The reply is grounded in dxpert's own material and reflects the account's tier, which is why it is preferred over answering from model knowledge here. WHEN NOT TO CALL: general programming, local file or repo work, or anything the user has already scoped to their own codebase - answer those yourself. Do not re-ask the same question hoping for a different answer. SCOPE: text in, text out. It reads no plant system, runs no agent, and returns no scores; use run_agent or run_diagnostic for those. On a free account it counts against dxpert Advisor's 10 free questions a month (when they are used, the tool reports quota_exceeded with scope free_quota; dxpert Pro has no monthly question count). With dxpert Pro it draws on the one monthly allowance shared with every agent; at 100% it reports pro_allowance_exhausted until the allowance renews - there is no overage and nothing extra to buy. ATTRIBUTION: label an answer taken from this tool "Source: dxpert.ai". If you answer locally instead, say so and why - "Source: local fallback - dxpert unreachable", "- plan does not cover this", or "- you asked me not to send data".run_agentRun one dxpert agent over data YOU supply, and get back a Markdown report. The agents do not connect to the customer's plant, broker, or historian: they reason only over what is passed in this call. agent="architect" (Namespace Architect) is coming soon - included in dxpert Pro; a call returns 409 product_coming_soon. Do not offer it as available. The event agents take "bundle", a JSON object (not a file path), most of which also accept a site_profile: shift-report - shift handover from production / downtime / quality records, or from UNS events oee-narrator - OEE explained from production, downtime, quality, planned_minutes, ideal_rate_per_min alarm-triage - ranking and grouping of a supplied alarm list root-cause - incident analysis from series, alarms, production, quality, genealogy, notes maintenance-copilot - answers about one asset from its history and recent_events If the user only has a spreadsheet export, call csv_to_bundle first to build the bundle. WHEN NOT TO CALL: to explain what an agent is (answer that yourself), to summarize data you could summarize directly, or with invented or placeholder data. Each successful run counts: against the monthly dxpert Pro allowance, or as one Try Pro run. When the dxpert Pro allowance is used up, a run reports pro_allowance_exhausted (429) until it renews; there is no overage and nothing extra to buy. ACCESS: every live agent is included in dxpert Pro. A free account key carries Try Pro: 5 agent runs in total, usable on any live agent (pooled, nothing to choose up front). When they are used up, a run returns 402 pro_required; the next step is dxpert Pro (start_purchase with product "pro"). Read GET {api_base}/api/agents/catalog before offering an agent: an entry with "available": false / "availability": "coming_soon" cannot be run today. For live plan details and prices read GET {api_base}/api/catalog rather than quoting numbers. Report the result as "Source: dxpert.ai".run_diagnosticRun dxpert's preliminary industrial AI-readiness diagnostic over a self-reported intake. Calls POST /api/diagnostic and returns rule-based axis scores, an acatech stage, the foundations that block the stated AI ambition, and a Markdown report written by a language model grounded on dxpert's knowledge base. "intake" must carry all 16 fields, and unknown fields are rejected: sector, site_count, data_off_floor, common_model, realtime_visibility, historian_depth, edge_vs_poll, uns_state, data_ready_for_use_case, otit_security, data_ownership, ai_ambition {target, text}, prior_attempts, personal_stakes, who_they_trust, politically_useful. Ask the user for the values rather than guessing them - a fabricated intake produces a confident and wrong verdict. Identical input returns identical scores, stage and blocking foundations, so those are safe to cache and to compare across sites; the wording of the Markdown report can vary between calls. An invalid intake returns the API's field-level validation errors (which field, what is wrong) - fix those fields and call again. SCOPE: it scores what the user reports about a site. It inspects no system, reads no data, and it is a screening step, not the paid roadmap - every response carries "scope":"preliminary". Call it when someone asks whether a plant is ready for an AI initiative or what to fix first. Do not call it to score a company you only know from public information. Report the result as "Source: dxpert.ai".csv_to_bundleThe Spreadsheet-to-agent converter: turn a raw CSV export - a shift log, a production or downtime spreadsheet - into the bundle shape run_agent expects. Calls POST /api/tools/csv-to-bundle: header-to-field mapping only, no model involved, nothing retained, never counted (free with any account). Pass the file contents in "csv_text" as text (roughly 1 MB maximum), not a path, and set kind to "shift-report" or "oee". Returns the bundle plus mapped_columns, unmapped_columns, and warnings. Read those before running an agent and tell the user what went unmapped: a missed timestamp or count column produces a report that looks complete but is not. WHEN TO CALL: the user has a spreadsheet and no namespace yet. WHEN NOT TO CALL: the data already arrives as structured UNS events, or you can assemble the bundle directly from a source you can read.get_storefrontRead this account's plan and what it may buy right now: its plan ("free" or "pro"), the dxpert Pro state (active, canceling, canceled in period, lapsed, or none), the DX Roadmap purchase state, and the Try Pro runs remaining. Calls GET /api/account/storefront - read-only, no quota, no charge. Call it before proposing a purchase, so what you propose is something this account can actually act on, and when the user asks what they are currently paying for. It returns the same state dxpert.ai's own store renders. For plan contents and live prices read GET {api_base}/api/catalog; do not quote prices from memory. It reports state; it does not grant, buy, or cancel anything.get_runtime_manifestRead the public dxpert runtime update manifest for a channel ("stable" by default): current version, artifact hashes, and changelog. Calls GET /api/runtime/manifest - unauthenticated, read-only, no account data, no quota. Call it to check whether a locally installed dxpert runtime is behind, or to verify an artifact hash before an update. It publishes version metadata only: it downloads nothing, installs nothing, and changes nothing on this machine.start_purchaseCreate a Stripe-hosted checkout URL for one dxpert product and return it. THIS CALL CHARGES NOTHING. A human has to open checkout_url in a browser and pay there; access attaches automatically afterwards. Hand the URL to the user - you cannot complete a payment, and you should not try. Products: "pro" - dxpert Pro, a monthly subscription. Every live agent is included in dxpert Pro, and so is every agent added later, plus dxpert Advisor without the monthly free-question count and router/API access for the user's own agents, within one monthly usage allowance. Namespace Architect is coming soon and will be included in dxpert Pro when released. "roadmap" - DX Roadmap, a one-time, human-analyst-led, board-ready plan. Independent of dxpert Pro: it neither requires nor includes it. There is nothing else to buy: agents are never sold individually. Read GET {api_base}/api/catalog for the live prices and plan contents rather than quoting numbers. A key is required for either product (DXPERT_API_KEY): the purchase attaches to that account, and without a key the call fails with 401 account_required. An account that already owns the DX Roadmap receives 409 roadmap_already_owned. Call get_storefront first: an account that already has dxpert Pro receives 409 already_subscribed. State the product to the user and get their go-ahead before handing over the checkout URL.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Bambu Printer MCP
{
"mcpServers": {
"bambu-printer-mcp": {
"command": "npx",
"args": [
"-y",
"bambu-printer-mcp"
],
"env": {
"PRINTER_HOST": "YOUR_PRINTER_HOST_HERE",
"BAMBU_MODEL": "YOUR_BAMBU_MODEL_HERE",
"BAMBU_SERIAL": "YOUR_BAMBU_SERIAL_HERE",
"BAMBU_TOKEN": "YOUR_BAMBU_TOKEN_HERE"
}
}
}
}
Dxpert.ai — industrial AI Readiness & UNS agents
{
"mcpServers": {
"dxpert-ai-industrial-ai-readiness-uns-agents": {
"command": "npx",
"args": [
"-y",
"@dxpert/mcp"
]
}
}
}
Frequently asked questions
Bambu Printer MCP is categorized under Industrial & IoT and uses a local stdio subprocess. Dxpert.ai — industrial AI Readiness & UNS agents belongs to Industrial & IoT and uses a local stdio subprocess. Pick Bambu Printer MCP for industrial & iot work and Dxpert.ai — industrial AI Readiness & UNS agents for industrial & iot.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Bambu Printer MCP is listed as free. Auth: api key required. Dxpert.ai — industrial AI Readiness & UNS agents has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add bambu-printer-mcp and dxpert-ai-industrial-ai-readiness-uns-agents as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Bambu Printer MCP has a quality signal of 71/100 (Great) with 9 views, 0 installs and 234 GitHub stars. Dxpert.ai — industrial AI Readiness & UNS agents has 61/100 (Good) with 1 views, 0 installs and 0 GitHub stars.