Once ezeep is connected, your assistant has a set of print tools it can call for you. You describe what you want and it picks the tool, so the names below matter only when you want to be precise about something. This page covers what each tool does, what it needs from you, and what comes back.
Finding and inspecting printers
| Tool | Purpose |
| List Printers | Returns every printer the connected account can reach, with an identifier, display name, location and whether the entry is a queue. Printer status is not part of this response, so questions about what is down get answered from connectors instead. |
| Get Printers Properties | Needs a printer identifier. Returns the fullest picture any single tool gives: color and duplex support with their defaults, collation, every supported paper size with dimensions and which one is default, the tray list, orientations and resolutions. Questions about what a given printer can physically do are answered here in one call. |
| Check Supported File Types | Returns the platform configuration, which carries the supported file extensions along with a good deal of unrelated system detail. Ask for the extensions specifically and the assistant will pull them out for you. |
| List Printers with issues | Returns a count and the printers currently reporting a problem. Nothing wrong means an empty list and a count of zero, not an error. |
Printing a document
| Tool | Purpose |
| Print from a URL | Needs the file URL, a filename and a printer identifier. Copies, color, duplex and paper size are optional. Returns a job identifier. |
| Print a local or generated file | Preparing an upload needs a filename and returns a time-limited upload location. Once the file is placed there, the print call needs the file identifier and a printer identifier, with the same optional settings. |
Tracking a job
| Tool | Purpose |
| Get Print Job Status | Needs a job identifier, which comes back when a job is submitted. Returns the current state. The same job appears in the admin portal, so anything printed from an AI client is auditable in the usual place. |
Connector and printer health
| Tool | Purpose |
| List Connectors | Returns a page at a time. Each connector carries its identifier, readable name, description, type, online or offline status, location, hostname, internal address, operating system, software version, when it was last seen online and when its printers last updated. |
| List offline Connectors | Returns the offline ones directly. |
| Get Connector Status | Needs a connector identifier and returns that connector's detail. |
Managing people and access
| Tool | Purpose |
| List Groups | Needs nothing, returns a page at a time. Each group carries its identifier, name, description, local printing and personal printer flags, where the group came from (an identity provider or ezeep itself) and its member and printer counts. |
| Create a Group | Needs a name. A description is optional. |
| Add a User to a Group | Needs a group identifier and a user identifier. |
| Assign a printer to a group | Needs a group identifier and a printer identifier. |
| List Users | Returns the organization's full user list in one response, with contact details, sign-in identifiers, verification state, feature flags and group memberships for each person. Worth knowing before you ask an AI client to read it. |
| Invite a User | Needs an email address. First and last name and the invitation lifetime are optional. |
Checking your account
| Tool | Purpose |
| Get Account Info | Returns the connected account's display name, organization, roles, verification state, language and identity provider. Ask for this first whenever results look unfamiliar or a management call gets refused. |
| Get Organization | Returns the organization record, including its name and the identity provider it is tied to.
|
Developer support
The server carries its own documentation as callable tools: an integration guide, an API reference and code examples. These work before you have signed in, which is why an assistant can scaffold an ezeep integration and then walk you through connecting it. Build an app that prints with the ezeep API covers that path.
What the MCP server does not do
Deleting a user, deleting a group, removing a printer from a group and canceling a job in flight are not available through the MCP server. The REST API does expose deletes for printers, connectors and users, so these are not platform limits, just tools the MCP surface does not carry. Use the admin portal.
