mcpdirectory.dev
9,129 servers · updated 23 Sept

Slicer MCP server

community Active last commit 54 d
{
  "mcpServers": {
    "fabtally-slicer": {
      "type": "http",
      "url": "https://fabtally.com/mcp"
    }
  }
}
file .mcp.json (in your project root)version 1.0.0

What it does

MCP server that exposes FDM 3D-printing slicing, quoting, and design-for-manufacturability (DFM) analysis. Free tools run against 12 printer profiles and 12 filament materials with rate limiting; premium tools require x402 payment per call. Useful for anyone designing parts for 3D printing who wants accurate quotes, printability checks, and orientation optimization before committing to print.

  • Check if a 3D model is printable on specific printer and material combinations, with support material and wall-thickness estimates.
  • Get slicer-accurate print time, filament weight, and cost quotes with optional custom pricing parameters.
  • Find the best model orientation to minimize support material usage by comparing multiple slices.

Tools this server exposes

ToolDoes
list_printersReturns the 12 available printer profiles with bed dimensions and nozzle size, 12 filament materials, and x402 pricing tiers.
check_printabilityAnalyzes model geometry for printability; free mode gives geometry preview, watertight check, wall-thickness estimate, and overhang heuristic; full mode returns
analyze_modelReturns geometry metadata: bounding box, volume, triangle count, watertight status, bed fit, and printable verdict.
get_print_quoteGenerates slicer-accurate quote with print time, filament weight, and price; supports optional custom pricing inputs or FabTally hobbyist defaults.
optimize_orientationSlices up to 4 model orientations and recommends the one requiring the least support material, showing exact savings (x402-metered).
slice_modelProduces full slice for any printer: layer count, time, filament; optionally returns preview PNG or G-code (x402-metered).

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.