Bambuddy MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BAMBUDDY_API_URL | No | Bambuddy API root URL | http://127.0.0.1:8000/api/v1 |
| BAMBUDDY_AGENT_ID | No | Client identifier written to request headers | mcp-client |
| BAMBUDDY_API_TOKEN | No | Bambuddy API key; can be omitted if authentication is disabled | |
| BAMBUDDY_HTTP_HOST | No | HTTP listen address; use 0.0.0.0 for remote listening | 127.0.0.1 |
| BAMBUDDY_HTTP_PATH | No | Streamable HTTP MCP path | /mcp |
| BAMBUDDY_HTTP_PORT | No | HTTP listen port | 8765 |
| BAMBUDDY_TRANSPORT | No | Transport mode: stdio or streamable-http | stdio |
| BAMBUDDY_HTTP_STATELESS | No | Whether to use session-less HTTP; currently recommended to keep false | false |
| BAMBUDDY_HTTP_PUBLIC_URL | No | Full public/VPN URL accessible to clients | |
| BAMBUDDY_MCP_BEARER_TOKEN | No | Separate token that MCP clients use to access /mcp | |
| BAMBUDDY_ENABLE_WRITE_TOOLS | No | Whether to allow the bambuddy_start_print tool to create queue tasks | false |
| BAMBUDDY_HTTP_ALLOWED_HOSTS | No | Allowed Host values, comma-separated | |
| BAMBUDDY_HTTP_JSON_RESPONSE | No | Whether to disable SSE responses and return JSON only | false |
| BAMBUDDY_API_TIMEOUT_SECONDS | No | HTTP request timeout, maximum 120 seconds | 20 |
| BAMBUDDY_HTTP_ALLOWED_ORIGINS | No | Allowed Origin values, comma-separated; non-browser clients usually do not send Origin | |
| BAMBUDDY_API_MAX_RESPONSE_BYTES | No | JSON response limit | 2097152 |
| BAMBUDDY_HTTP_MAX_REQUEST_BYTES | No | MCP HTTP request body limit | 1048576 |
| BAMBUDDY_SNAPSHOT_MAX_RESPONSE_BYTES | No | Snapshot response limit | 8388608 |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bambuddy_list_printersA | List printers configured in Bambuddy. The result intentionally excludes IP addresses, serial numbers, access codes, and camera URLs. |
| bambuddy_get_printer_statusA | Get a sanitized live status snapshot for one Bambuddy printer, including print progress, temperatures, HMS issues, and non-secret AMS summaries. |
| bambuddy_get_current_printA | Get the current print job summary for one Bambuddy printer. |
| bambuddy_diagnose_printerA | Run Bambuddy's read-only connection diagnostic for an existing printer. IP addresses and diagnostic parameters are removed from the result. |
| bambuddy_get_camera_statusA | Get live-stream health for one printer camera without opening a stream. |
| bambuddy_get_camera_snapshotA | Capture one current camera frame as an image. This does not expose the camera URL, credentials, or a continuous video stream. |
| bambuddy_list_print_sourcesA | List recent archived .gcode.3mf print sources that can be selected for a Bambuddy queue job. Results exclude filesystem paths and archive internals. |
| bambuddy_prepare_printA | Validate one archived .gcode.3mf source and create a five-minute, one-use preflight token. This tool is read-only and does not queue or start a print. |
| bambuddy_start_printA | Consume a fresh one-use preflight token and create an ASAP, top-priority Bambuddy queue item. This can cause physical printer motion and must only be called after the user explicitly confirms the exact preflight summary. |
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 9 tools
Most tools target clearly distinct resources and actions, such as camera snapshot versus camera status or list printers versus diagnose printer. The only mild overlap is between get_printer_status and get_current_print, since both could reasonably be used to check ongoing print progress.
Every tool follows the same bambuddy_<verb>_<noun> snake_case pattern with verbs like get, list, prepare, start, and diagnose. This makes the API surface highly predictable and easy for an agent to navigate.
Nine tools is well within the ideal range and each tool serves a meaningful part of the printer monitoring and print-starting workflow. No tool feels redundant or unnecessary.
The core read-only monitoring, camera access, and safe print-start workflow are well covered, including preflight token handling. Minor lifecycle gaps exist, such as no cancel, pause, or print queue management tools, but the available surface supports the apparent primary use case.