3dprint Oracle
Give agents authoritative filament and materials guidance while you design parts, slicer presets, or maker-commerce SKUs.
Overview
3D Print Oracle is a MCP server for the Build phase that supplies filament and materials knowledge to agents working on 3D printing projects.
What is this MCP server?
- Filament and materials knowledge specialized for 3D printing workflows
- npm stdio package identifier 3dprint-oracle for local agent runs
- GitHub-hosted gregario/3dprint-oracle at version 0.1.0
- Reduces guesswork on material choice during agent-assisted design sessions
- Package version 0.1.0
- Transport: stdio via npm registry
- Repository: github.com/gregario/3dprint-oracle
What problem does it solve?
Agents recommend the wrong filament temperatures and material pairings because general LLM training is thin on shop-floor 3D printing detail.
Who is it for?
Indie hardware hackers and tool builders who want a dedicated materials oracle inside Claude Code or Cursor workflows.
Skip if: Teams needing live printer telemetry, G-code generation, or enterprise PLM—not a substitute for slicer software itself.
What do I get? / Deliverables
After installing the stdio MCP package, your agent can pull structured materials knowledge while you code slicer presets, docs, or inventory features.
- Configured stdio 3D Print Oracle MCP server
- Agent-accessible filament and materials reference queries
- More consistent material recommendations in generated code and docs
Recommended MCP Servers
Journey fit
Materials knowledge MCPs support Build when you implement hardware-adjacent software, config generators, or maker tools that must reference real filament behavior. Integrations is the right shelf for an npm stdio MCP that agents invoke alongside CAD, inventory, or docs code—not pure frontend polish.
How it compares
Domain knowledge MCP for filaments, not a CAD plugin marketplace or OctoPrint monitoring server.
Common Questions / FAQ
Who is 3D Print Oracle for?
Solo builders and makers who use AI coding agents to develop 3D printing tools, documentation, or ecommerce listings and need reliable material context.
When should I use 3D Print Oracle?
Use it during Build when choosing filaments, writing material comparison tables, or generating configs where material properties should drive the answer.
How do I add 3D Print Oracle to my agent?
Install the npm package 3dprint-oracle, register it as a stdio MCP server in your client config pointing at the published binary, then invoke its material knowledge tools from the agent.