Plugged.in Proxy vs SimplyPrint: 3D Print Farm Management
Plugged.in Proxy is an MCP server published by VeriTeknik. Marketplaces we read that list it: 1 (Docker MCP Catalog). SimplyPrint: 3D Print Farm Management is an MCP server published by simplyprint.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Plugged.in Proxy |  SimplyPrint: 3D Print Farm Management |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:b7c32590b270 Forks (GitHub): 29 Pulls (Docker Hub): 36 587 Stars (Docker Hub): 3 Stars (GitHub): 138 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Plugged.in Proxy | SimplyPrint: 3D Print Farm Management |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 138 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 36 587 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 29 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/pluggedin-mcp-proxy) | Remote server (simplyprint.io/api/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 6 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/veriteknik/pluggedin-mcp-proxy | github.com/simplyprint/simplyprint-claude-plugin |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Plugged.in Proxy
A unified MCP proxy that aggregates multiple MCP servers into one interface, enabling seamless tool discovery and management across all your AI interactions. Manage all your MCP servers from a single connection point with RAG capabilities and real-time notifications.
SimplyPrint: 3D Print Farm Management
3D print farm management for AI. Monitor, queue, and control prints on your SimplyPrint account.
How to run each
Plugged.in Proxy As a local MCP server: Docker image
claude mcp add --env "PLUGGEDIN_API_KEY=<YOUR_PLUGGEDIN_API_KEY>" --transport stdio pluggedin-mcp-proxy -- docker run -i --rm -e PLUGGEDIN_API_KEY mcp/pluggedin-mcp-proxyRequires: PLUGGEDIN_API_KEY (secret)
SimplyPrint: 3D Print Farm Management As a remote MCP server
claude mcp add --transport http simplyprint https://simplyprint.io/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only SimplyPrint: 3D Print Farm Management has a remote endpoint we check. How we check endpoints
Tools each declares
Only Plugged.in Proxy has
pluggedin_ask_knowledge_basepluggedin_delete_notificationpluggedin_discover_toolspluggedin_list_notificationspluggedin_mark_notification_donepluggedin_send_notification
Only SimplyPrint: 3D Print Farm Management has
add_queue_commentadd_to_queueadjust_filament_weightapprove_queue_itemarchive_print_jobassign_filamentassign_maintenance_taskassign_tagscancel_maintenance_jobcancel_printcancel_scheduled_printcomplete_maintenance_job
Show the remaining 81
complete_maintenance_taskcreate_foldercreate_print_jobdelete_filedelete_folderdelete_queue_commentdelete_queue_groupdeny_queue_itemempty_queueestimate_file_costget_account_statisticsget_farm_overviewget_filamentget_filament_historyget_folderget_maintenance_dashboardget_maintenance_jobget_maintenance_status_mapget_next_queue_itemget_next_queue_items_for_printersget_partner_maintenance_overviewget_print_jobget_printerget_printer_maintenance_profileget_queue_itemget_queue_item_costget_referral_statsget_slicer_settings_for_fileget_webhook_samplehome_printerinspect_printer_queuelist_accounts_due_maintenance_visitlist_brand_filamentslist_custom_fieldslist_custom_fields_forlist_filament_colorslist_filamentslist_fileslist_maintenance_jobslist_maintenance_problemslist_partner_maintenance_alertslist_partner_maintenance_visitslist_pending_queue_itemslist_print_jobslist_printerslist_queuelist_queue_commentslist_queue_groupslist_scheduled_printslist_spare_partsmark_filament_driedmatch_file_to_printersmove_filemove_foldermove_printer_axismove_queue_itempause_printremove_from_queuereorder_queue_groupreorder_queue_itemreschedule_printresubmit_queue_itemresume_printrevive_queue_itemsave_queue_groupsend_back_for_revisionsend_gcodeset_custom_field_valuesset_file_printersset_printer_fansset_printer_motorsset_printer_temperaturesskip_maintenance_taskstart_maintenance_jobunarchive_print_jobunassign_filamentuncomplete_maintenance_taskunskip_maintenance_taskupdate_fileupdate_queue_commentupdate_queue_item
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (SimplyPrint: 3D Print Farm Management as of 2026-10-26). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of SimplyPrint: 3D Print Farm Management publish no settings it asks for, so we do not compare settings.
What it can do: Plugged.in Proxy · What it can do: SimplyPrint: 3D Print Farm Management · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.