spoolman-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SPOOLMAN_URL | Yes | Base URL of your Spoolman instance | |
| SPOOLMAN_API_KEY | No | Bearer token (if behind a proxy with auth) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| spoolman_get_infoA | Get general Spoolman API information (version, database type, debug mode, paths). |
| spoolman_health_checkA | Check whether the Spoolman instance is healthy and reachable. |
| spoolman_trigger_backupA | Trigger a database backup on the Spoolman instance (SQLite only). Returns the backup file path. |
| spoolman_list_vendorsA | List and search vendors in Spoolman. Supports filtering by name and pagination. |
| spoolman_get_vendorA | Get a single vendor by its ID. |
| spoolman_create_vendorB | Create a new vendor in Spoolman. |
| spoolman_update_vendorA | Update an existing vendor by ID. Only provide the fields you want to change. |
| spoolman_delete_vendorA | Delete a vendor by ID. This will cascade to associated filaments. |
| spoolman_list_filamentsA | List and search filaments in Spoolman. Supports filtering by vendor, material, color, article number and more. |
| spoolman_get_filamentA | Get a single filament by its ID. |
| spoolman_create_filamentB | Create a new filament definition in Spoolman. Density and diameter are required. |
| spoolman_update_filamentA | Update an existing filament by ID. Only provide the fields you want to change. |
| spoolman_delete_filamentA | Delete a filament by ID. |
| spoolman_list_spoolsA | List and search spools in Spoolman. Filter by filament, vendor, material, location, lot number and more. |
| spoolman_get_spoolA | Get a single spool by its ID, including remaining weight and usage stats. |
| spoolman_create_spoolA | Create a new spool in Spoolman. A filament_id is required. Specify either remaining_weight or used_weight (not both). |
| spoolman_update_spoolB | Update an existing spool by ID. Only provide the fields you want to change. remaining_weight and used_weight are mutually exclusive. |
| spoolman_delete_spoolB | Delete a spool by ID. |
| spoolman_use_spoolA | Log filament consumption for a spool. Provide either use_length (mm) or use_weight (g), not both. |
| spoolman_measure_spoolA | Update a spool's remaining filament by providing a current weight measurement (spool + filament together in grams). |
| spoolman_get_all_settingsA | Retrieve all Spoolman configuration settings. |
| spoolman_get_settingB | Retrieve a single Spoolman configuration setting by key. |
| spoolman_set_settingB | Set a Spoolman configuration value by key. |
| spoolman_list_fieldsA | List all custom extra fields defined for a given entity type (vendor, filament, or spool). |
| spoolman_upsert_fieldB | Add or update a custom extra field for a given entity type. |
| spoolman_delete_fieldB | Remove a custom extra field from an entity type. |
| spoolman_list_materialsA | List all filament material types that exist in Spoolman (e.g. PLA, PETG, ABS). |
| spoolman_list_article_numbersA | List all article numbers of filaments currently tracked in Spoolman. |
| spoolman_list_lot_numbersA | List all lot/batch numbers of spools currently tracked in Spoolman. |
| spoolman_list_locationsA | List all spool storage locations defined in Spoolman. |
| spoolman_rename_locationA | Rename an existing spool storage location. All spools at the old location will be updated to the new name. |
| spoolman_export_spoolsA | Export all spools from Spoolman as JSON or CSV. |
| spoolman_export_filamentsA | Export all filaments from Spoolman as JSON or CSV. |
| spoolman_export_vendorsA | Export all vendors from Spoolman as JSON or CSV. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 34 tools
Most tools have clear, distinct purposes (e.g., list_filaments vs list_materials vs list_article_numbers). Some potential confusion exists between use_spool and measure_spool, or get_info and health_check, but descriptions clarify these differences.
Tools generally follow the spoolman_<verb>_<noun> pattern (e.g., list_vendors, create_filament). Minor deviations like health_check (object before verb) and trigger_backup are present but not disruptive.
With 34 tools, the server is well above the typical 3-15 range for coherence. While the breadth covers many Spoolman features, the large number makes it heavy and more complex for agents to navigate.
Full CRUD exists for vendors, filaments, and spools, plus exports and settings. However, locations only have list and rename—missing create, delete, and get-by-id—which is a notable gap for that entity.