MCP 3D Printer Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is MCP 3D Printer Server?

MCP 3D Printer Server is a server application that allows users to connect and manage various 3D printers through their APIs, enabling seamless interaction and control.

How to use MCP 3D Printer Server?

To use the MCP 3D Printer Server, install it via npm or from source, configure your printer settings in a .env file, and connect it to your 3D printer management system. You can then interact with your printer through commands in the Claude Desktop application.

Key features of MCP 3D Printer Server?

  • Connects to multiple 3D printer management systems (e.g., OctoPrint, Klipper, Duet).
  • Provides real-time printer status updates and job monitoring.
  • Allows uploading and managing G-code files.
  • Advanced STL file manipulation capabilities.
  • Comprehensive error handling and diagnostics.

Use cases of MCP 3D Printer Server?

  1. Monitoring and controlling 3D print jobs remotely.
  2. Modifying STL files for better print quality.
  3. Automating the workflow from STL modification to printing.

FAQ from MCP 3D Printer Server?

  • Can I connect multiple printers?

Yes, you can connect multiple printers as long as they are supported by the server.

  • Is there a limit on STL file size?

Yes, large STL files can be memory-intensive, and it's recommended to keep them under 10MB for optimal performance.

  • How do I troubleshoot connection issues?

Ensure your printer is on the same network and that the API keys and connection settings are correctly configured.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
License
GPL-2.0 license

Recommend Servers

View All
Payai X402 Tools

an hour ago
Payai X402 Tools

an hour ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago