You can ask which printers are down and get an answer, without opening the admin portal. Connecting ezeep to an AI client takes one URL and one sign-in. After that, the assistant can list your printers, submit print jobs, check on those jobs, watch your connectors, and handle routine user and group work while you stay in the conversation you were already having.
What is the ezeep MCP server?
The ezeep MCP server is a hosted server that exposes ezeep cloud printing as tools an AI client can call. Claude, Cursor, GitHub Copilot, Lovable and other clients that speak Model Context Protocol can discover those tools and use them on your behalf, in natural language, with no code and no SDK. Calls run on the same ezeep platform as the REST API, so rate limits and reporting behave the way they always have. One tool call counts as one API call against your quota.
Before you start
You need an ezeep Admin account and a AI client that supports remote MCP servers over HTTP. ezeep's setup guidance is to connect using an organization admin account, since the assistant acts entirely as the account you sign in with.
That last point is worth sitting with for a moment. Whatever the connected account can reach in ezeep, the assistant can reach. Choosing the right account is the real decision here, and it matters more than any setting you pick afterwards. Getting an ezeep account Get Started.
Step 1: Add the endpoint to your AI client
The server URL is:
https://mcp.ezeep.com/functions/v1/ezeep-mcp/oauth
Clients that read a configuration file accept a block in this shape:
{
"mcpServers": {
"ezeep": {
"type": "http",
"url": "https://mcp.ezeep.com/functions/v1/ezeep-mcp/oauth"
}
}
}
Clients with a connector interface, such as Claude's connector settings or Lovable's integrations panel, take the same URL through their own screen. Restart the client afterwards if it asks you to.
Step 2: Authorize
The client opens a browser window on first use. Sign in with the ezeep account the assistant should act as, then approve the request.
Authorization runs between your client and ezeep directly. Tokens and passwords never enter the conversation with the AI model, and they are not part of what the model sees.
Step 3: Confirm it worked
Ask the assistant to list your ezeep printers. Printers coming back means the connection is live.
Name ezeep in that request rather than asking about printers generally. Clients often carry several connectors at once, and naming the one you mean saves the assistant guessing.
What can you do once it is connected?
Printing, connector monitoring, and user administration, all through conversation. The assistant can list printers and read their capabilities, print from a URL or from a file you upload, track a submitted job, report which connectors are offline, and create groups, invite people and assign printers.
ezeep MCP server tools covers what each one needs from you and what comes back. If you want phrasing that works, start with Prompts that work with the ezeep MCP server.
Which plans include the MCP server? See ezeep pricing.
FAQs
Do I need to write any code to use the ezeep MCP server? No. The client discovers the tools and calls them for you. You add the endpoint, sign in once, and describe what you want in plain language. Code only enters the picture if you are building a deployed application, and even then the assistant can generate it.
Which AI clients work with it? Any client that implements Model Context Protocol as a remote HTTP server. ezeep names Claude Desktop, Claude Code, Cursor, Copilot in VS Code and Lovable.
Do I have to say ezeep when I ask the assistant for something? It helps, and in a client with several connectors attached it is what tells the assistant which tools to use. "List my ezeep printers" routes cleanly where "list my printers" may not.
Does the AI see my documents? No. Document data moves through ezeep infrastructure over HTTPS and reaches the printer you named. The model receives the tool call and the result of that call, not the rendered file.
Can the assistant print to the wrong printer by accident? Printing requires an explicit call naming both a printer and a file, so it cannot happen in the background. Name printers directly rather than describing them, and the assistant has nothing to guess at.
Which printers and file types are supported? Whatever your ezeep account already supports, including label hardware. Ask the assistant which file extensions ezeep supports and it will read the current list from the platform rather than working from memory.
How long does the connection stay valid? Access tokens are short-lived and refresh in the background. A session that worked earlier and now returns authorization errors usually needs the connection reconnected in your client, which forces a fresh sign-in.