Home / MCP registry index / io.simplyprint/simplyprint

SimplyPrint: 3D Print Farm Management

io.simplyprint/simplyprint in the official MCP registry. Endpoint https://simplyprint.io/api/mcp. Source: github.com/simplyprint/simplyprint-claude-plugin.

The registry describes it as: 3D print farm management for AI. Monitor, queue, and control prints on your SimplyPrint account.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http simplyprint https://simplyprint.io/api/mcp

{
  "mcpServers": {
    "simplyprint": {
      "url": "https://simplyprint.io/api/mcp"
    }
  }
}

code --add-mcp '{"name":"simplyprint","type":"http","url":"https://simplyprint.io/api/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

list_printers get_printer get_farm_overview pause_print resume_print cancel_print send_gcode create_print_job list_scheduled_prints reschedule_print cancel_scheduled_print home_printer move_printer_axis set_printer_fans set_printer_motors set_printer_temperatures list_queue get_queue_item remove_from_queue add_to_queue update_queue_item reorder_queue_item move_queue_item revive_queue_item empty_queue inspect_printer_queue get_queue_item_cost get_next_queue_item get_next_queue_items_for_printers list_queue_groups save_queue_group delete_queue_group reorder_queue_group list_pending_queue_items approve_queue_item deny_queue_item send_back_for_revision resubmit_queue_item list_queue_comments add_queue_comment update_queue_comment delete_queue_comment list_custom_fields list_custom_fields_for set_custom_field_values list_files get_folder estimate_file_cost match_file_to_printers set_file_printers update_file assign_tags create_folder delete_folder move_file move_folder delete_file get_slicer_settings_for_file list_filaments get_filament and 33 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-30): b7391f3153ade13c. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-simplyprint-simplyprint/badge.svg)](https://lazaretto.dev/mcp-registry/io-simplyprint-simplyprint)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.