{"id":"yadomi-repetier-server","name":"repetier-server","homepage":"https://hub.docker.com/r/yadomi/repetier-server","repo_url":"https://hub.docker.com/r/yadomi/repetier-server","category":"infrastructure","subcategories":[],"tags":["3d-printing","self-hosted","remote-monitoring","gcode","web-ui"],"what_it_does":"Repetier-Server is a self-hosted print-management server for 3D printers. It provides web-based control/monitoring and integrates with printers/firmware via common printer communication methods, enabling remote administration and job management.","use_cases":["Remote monitoring and starting/stopping 3D printer jobs via a web interface","Centralized management of one or more 3D printers from a home/lab network","Integrating printer workflows with external tooling (e.g., sending G-code / managing print files)"],"not_for":["Serverless/public SaaS usage without self-hosting requirements","Highly security-sensitive environments without additional network hardening and secrets management","Agent-driven environments needing a documented public REST/OpenAPI service contract"],"best_when":"You need self-hosted 3D printing control on a local network and can secure the deployment (reverse proxy, firewall, TLS).","avoid_when":"You cannot expose it safely (no TLS, no access controls, or open admin endpoints to the internet) or you require a standardized API spec and SDK for programmatic integration.","alternatives":["OctoPrint (self-hosted)","Klipper + mainsail/Fluidd (self-hosted ecosystem)","PrusaConnect / vendor cloud solutions (if you prefer hosted management)","Repetier-Host (desktop-side control rather than server orchestration)"],"af_score":26.0,"security_score":30.8,"reliability_score":32.5,"package_type":"mcp_server","discovery_source":["docker_mcp"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:34:06.668669+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":false,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":[],"oauth":false,"scopes":false,"notes":"Auth mechanisms are not described in the provided data. For self-hosted admin/control panels, expect typical session/password or basic auth, but details cannot be verified here."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"As a self-hosted server, pricing is typically deployment/hosting cost rather than a usage-based commercial plan."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":26.0,"security_score":30.8,"reliability_score":32.5,"mcp_server_quality":0.0,"documentation_accuracy":30.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":50.0,"rate_limit_clarity":0.0,"tls_enforcement":20.0,"auth_strength":35.0,"scope_granularity":20.0,"dependency_hygiene":40.0,"secret_handling":40.0,"security_notes":"No deployment/auth/TLS specifics were provided in the prompt content. For a self-hosted print control server, the main risks are exposing admin endpoints to the internet, weak authentication, and not enforcing HTTPS. Dependency/security hygiene cannot be determined from the provided data.","uptime_documented":0.0,"version_stability":50.0,"breaking_changes_history":50.0,"error_recovery":30.0,"idempotency_support":"false","idempotency_notes":null,"pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["Self-hosted web control is often not designed as an agent-friendly API surface (no stable, documented machine contract).","Print job operations are typically stateful; retries may duplicate or corrupt job state if endpoints are not explicitly idempotent.","Deployment-specific networking (reverse proxy/timeouts) can cause intermittent failures that agents may misinterpret."]}}