Printix MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTH_MODE | No | `env` (default, reads the vars above) or `gateway` (credentials arrive per-request via `X-Printix-*` headers, injected by the Conduit gateway). | env |
| LOG_LEVEL | No | `debug` | `info` (default) | `warn` | `error`. | info |
| MCP_TRANSPORT | No | `stdio` (default) or `http`. | stdio |
| PRINTIX_CLIENT_ID | No | Client ID from the Printix Administrator dashboard. | |
| CONDUIT_S2S_SECRET | No | When set, the HTTP transport requires a valid `X-Gateway-S2S` header (Conduit sidecar auth) on every `/mcp` request. | |
| PRINTIX_CLIENT_SECRET | No | Client secret paired with the client ID. |
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 | {} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| printix_get_tenantA | Get the Printix tenant this credential pair is scoped to (tenant ID and its API root link). |
| printix_list_printersA | List Printix print queues/printers for the tenant, optionally filtered by search query and paged. |
| printix_get_printerA | Get a single Printix printer/queue and its properties/capabilities by ID. |
| printix_list_sitesA | List Printix sites (physical locations) for the tenant, paged. |
| printix_get_siteB | Get a single Printix site (physical location) by ID. |
| printix_list_workstationsA | List Printix workstations (client-device monitoring data) for the tenant, paged. |
| printix_get_workstationA | Get a single Printix workstation by ID. |
| printix_list_usersA | List Printix users for the tenant, optionally filtered by search query or role, paged. |
| printix_get_userA | Find a single Printix user by ID. |
| printix_list_groupsA | List/search Printix groups for the tenant, paged. |
| printix_get_groupA | Fetch a single Printix group and its details by ID. |
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 11 tools
Every tool targets a distinct resource/action pair: each of the five core resources has one list operation and one get-by-ID operation, with no overlapping verbs. The only singleton, get_tenant, is clearly unique.
All tool names use the same printix_ prefix with a consistent verb_noun pattern: printix_list_* for collection queries and printix_get_* for single-resource lookups. There is no mixing of styles or vague verb usage.
11 tools is a well-scoped count for a Printix query surface: five resources are each covered by a list/get pair, plus the tenant lookup. No tool is redundant or unnecessary.
The read-only resource coverage is broad, but the server has no create/update/delete or print-job/lifecycle operations, so any management workflow beyond listing and fetching dead-ends. This is a significant gap for a Printix administration context.