@printyourduck/mcp

PrintYourDuck MCP

MCP server for sending local 3D print files to PrintYourDuck manual quote review. It is built for coding-agent workflows where the user has generated or selected a local .stl, .step, .stp, .3mf, .obj, or .zip file and wants help preparing a quote request.

The server is preconfigured for https://printyourduck.com. Users do not need to supply an API URL, API key, or shop routing configuration.

Status

Surface	Status
Remote MCP	Live at https://printyourduck.com/api/mcp
Local stdio package	Pre-publication
npm package	Planned: @printyourduck/mcp
OCI image	Planned: ghcr.io/printyourduck/printyourduck-mcp
MCP Registry	Planned after npm/GHCR/GitHub release artifacts exist

Until those package artifacts are public, treat npx and Docker commands below as post-publication examples.

Why This Exists

3D-print quote workflows are easy to get wrong when a user is coming from code, CAD generation, or rapid prototyping. This MCP server gives agents a narrow, auditable workflow:

• Read the public quote requirements.
• Find recent printable files in the current project.
• Ask the user to choose one file and confirm the required safety statements.
• Upload that file through PrintYourDuck's private upload flow.
• Submit the manual quote request.
• Check public-safe quote status by quote ID and customer email.

It does not calculate instant pricing, collect payment at upload, automate checkout, or expose private operational details.

Install

After npm publication:

npx -y @printyourduck/mcp

Most stdio-capable MCP clients use a configuration like this:

{
  "mcpServers": {
    "printyourduck": {
      "command": "npx",
      "args": ["-y", "@printyourduck/mcp"]
    }
  }
}

Docker after OCI publication:

docker run --rm -i ghcr.io/printyourduck/printyourduck-mcp:<version>

Remote-capable MCP clients can connect today:

https://printyourduck.com/api/mcp

Tools

Tool	Purpose	Network/File Access
get_printyourduck_quote_requirements	Returns accepted file types, material choices, required confirmations, and safety boundaries.	No local file access. No network.
find_recent_printable_files	Finds recent printable files under an allowed local project directory.	Read-only local file metadata.
submit_local_file_for_quote	Uploads one user-approved local file and creates a manual quote request.	Reads one allowed local file, uploads privately, then submits to PrintYourDuck.
get_quote_status	Looks up public-safe quote status with quote ID and matching email.	Network request to PrintYourDuck only.

Local file discovery and upload are limited to the current working directory by default. Set PRINTYOURDUCK_MCP_ALLOWED_ROOTS to a path-delimited allowlist when the MCP client should access additional project directories.

submit_local_file_for_quote derives a stable submissionId from the selected file and quote details unless the caller provides one. Reuse that ID on retry to avoid duplicate manual quote requests.

Guardrails

This server preserves the PrintYourDuck manual-quote boundary:

• no instant pricing today;
• no payment at upload;
• no checkout automation;
• no local-production, Canadian-made-production, or guaranteed-delivery claims;
• no supplier locations, fulfilment routes, carrier strategy, supplier costs, margin logic, private file references, or customer data in public responses.

Price ranges or instant estimates are a valid future capability only when they are explicitly scoped, tested, publicly documented, and clearly separated from checkout or payment collection.

Development

pnpm install
pnpm check:release

Useful checks:

pnpm check          # lint, tests, typecheck
pnpm check:security # audit, gitleaks, trufflehog
pnpm check:mcp      # stdio initialize, tool list, fixture discovery, path guard
pnpm check:pack     # npm tarball allowlist

pnpm check:mcp builds the server, starts it over stdio, verifies initialize and tool metadata, creates a temporary .stl fixture, verifies local discovery, and verifies files outside allowed roots are rejected before upload.

Run the live production smoke only when you intentionally want to create a real quote request:

PRINTYOURDUCK_MCP_LIVE_SMOKE=1 \
PRINTYOURDUCK_MCP_SMOKE_EMAIL=[e-mail] \
pnpm smoke:live

The live smoke uploads a tiny fixture through https://printyourduck.com, submits one manual quote request, and verifies get_quote_status returns.

Release Checklist

Only claim public local-helper installability after all of these pass:

pnpm check:release
npm view @printyourduck/mcp version
VERSION="$(npm view @printyourduck/mcp version)"
docker manifest inspect "ghcr.io/printyourduck/printyourduck-mcp:${VERSION}"
gh release view "mcp-v${VERSION}"
PRINTYOURDUCK_MCP_LIVE_SMOKE=1 PRINTYOURDUCK_MCP_SMOKE_EMAIL=[e-mail] pnpm smoke:live

When the package is deliberately ready for publication, remove private: true from package.json and release from this dedicated MCP repository, not from the website repository.

The MCP Registry name is com.printyourduck/quote, so publication uses domain-based HTTP authentication for printyourduck.com. Serve the public v=MCPv1; ... record from https://printyourduck.com/.well-known/mcp-registry-auth and keep the matching private key only in the MCP_REGISTRY_PRIVATE_KEY GitHub Actions secret for this repository.

Contributing

See CONTRIBUTING.md. Good first areas include client setup docs, path-safety hardening, MCP metadata safety, package release checks, and public-safe examples.

For security issues, see SECURITY.md. Do not include secrets, customer files, private file references, supplier/cost/margin details, or dashboard screenshots in public issues.