ipp-bridge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IPP_BRIDGE_API_KEY | No | Optional auth key for Upload API. | |
| IPP_BRIDGE_BACKEND | No | Print backend to use: auto, ipp, or lp. | auto |
| IPP_BRIDGE_FILE_TTL | No | Staging TTL in seconds. | 3600 |
| IPP_BRIDGE_INSECURE | No | Disable TLS certificate verification (1/true). | false |
| IPP_BRIDGE_UPLOAD_DIR | No | Staging directory for uploaded files. | <temp>/ipp-bridge-uploads |
| IPP_BRIDGE_PRINTER_URI | No | Target IPP/IPPS/HTTP(S) printer URI. | |
| IPP_BRIDGE_CUPS_PRINTER | No | Default CUPS destination for lp. | |
| IPP_BRIDGE_UPLOAD_API_URL | No | Remote Upload API URL. | |
| IPP_BRIDGE_MAX_UPLOAD_BYTES | No | Max upload size in bytes. | 52428800 |
| IPP_BRIDGE_ALLOW_LOCAL_PATHS | No | Allow printing paths outside upload_dir. | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
HTTP Upload + IPP/CUPS Bridge MCP Server. Use list_uploaded_files or upload_file to inspect/stage files, validate_print_job to preflight check compatibility, and print_file to send staged files directly to the IPP printer or CUPS lp command.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bridge_statusA | Return bridge configuration, staging directory, and active backend availability. |
| upload_fileA | Stage a text or base64-encoded binary file through the upload bridge. Returns file_id and local_path that can be passed to validate_print_job or print_file. |
| list_uploaded_filesA | List non-expired files currently staged in the temporary upload store. |
| get_uploaded_fileA | Retrieve metadata and local_path for a staged uploaded file by file_id. |
| delete_uploaded_fileB | Delete a staged uploaded file from temporary storage by file_id. |
| list_printersB | List configured IPP printers and/or local CUPS destinations. |
| get_printer_attributesC | Query detailed printer status, supported formats, media, and marker levels. |
| validate_print_jobB | Validate an uploaded file_id or local_path against the printer without printing. |
| print_fileC | Print a staged file (by file_id or local_path) directly via IPP or CUPS lp. |
| list_jobsB | List active or completed print jobs on the IPP printer or CUPS queue. |
| get_job_statusC | Get attributes and state for a specific print job ID. |
| cancel_jobB | Cancel a queued or active print job by job_id. |
| identify_printerC | Trigger IPP Identify-Printer (e.g. display message on printer panel or flash). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| print_uploaded_document | Guided workflow for validating and printing an uploaded file. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| resource_status | |
| resource_files | |
| resource_printer_attributes |
TDQS
Scored across 13 tools
Each tool maps to a distinct resource+action across three clear groups (uploaded files, print jobs, printers), and descriptions make boundaries readable. Minor overlap exists between bridge_status and get_printer_attributes (both report 'status' at different layers), which could cause an occasional misselection.
Strong snake_case verb_noun convention throughout (upload_file, list_jobs, get_job_status, cancel_job, delete_uploaded_file). The lone deviation is bridge_status, which puts the noun first instead of following the get_/list_ verb pattern.
13 tools is well within the ideal range for a print-bridge server, with sensible coverage of uploads, jobs, and printer discovery. Each tool appears to earn its place; nothing looks redundant or padded.
Full lifecycle is covered for staged uploads (upload, list, get, delete) and jobs (list, status, cancel, submit via print_file), plus printer discovery and validation. Gaps remain around job control (hold/release/pause/resume) and any cleanup of expired jobs, but core workflows have no dead ends.