ezeep MCP Server

The ezeep MCP server is a Model Context Protocol server that lets an AI assistant (Claude Desktop, Claude Code, GitHub Copilot, Cursor, and other MCP-aware clients) talk to the ezeep API on your behalf. Connecting it takes about a minute and does not require you to implement any OAuth flow yourself — the client handles authorization automatically.

Why connect the MCP before you read the rest of the docs

Once the MCP is connected, three tools work without any credentials at all and are aimed specifically at understanding the ezeep API:

Tool What you can ask
get_integration_guide “Walk me through the shortest end-to-end path from zero to a printed page.”
get_api_reference “Which endpoint do I call to list a user’s printers, and what are the required parameters?”
get_code_example “Give me a curl example for uploading a document and printing it.”

You do not need an ezeep account to use these three tools — they document the API. Only the ezeep-API-backed tools (list printers, upload document, print, register OAuth client, and so on) require authentication, and the MCP client negotiates that for you the first time you use one.

If you prefer to read the docs directly, everything the MCP surfaces is derived from the pages in this reference; the MCP is a convenience layer, not a substitute.

Connect the ezeep MCP (OAuth — recommended)

The recommended /mcp endpoint uses OAuth 2.1 with PKCE. No credentials in any config file — the client opens a browser for you to sign in to ezeep, obtains its own tokens, and rotates them. Copy the snippet for your client below.

Claude Desktop

Remote MCP servers with OAuth are configured through the Custom Connectors UI, not claude_desktop_config.json. Open Claude Desktop and:

  1. Go to Settings → Connectors (or Customize → Connectors depending on version).
  2. Click the + button under Custom connectors and choose Add custom connector.
  3. Enter:
    • Name: ezeep
    • URL: https://mcp.ezeep.com/mcp
  4. Save. Claude Desktop opens a browser window for you to sign in to ezeep on first use.

Claude Code (CLI) 

claude mcp add --transport http ezeep https://mcp.ezeep.com/mcp

Verify with claude mcp list.

GitHub Copilot (VS Code)

Add to .vscode/mcp.json in your workspace (or the user-level mcp.json opened via MCP: Open User Configuration in the command palette):

{
  "servers": {
    "ezeep": {
      "type": "http",
      "url": "https://mcp.ezeep.com/mcp"
    }
  }
}

VS Code discovers the new server automatically; no reload required. On first use, Copilot opens a browser window for you to sign in to ezeep.

Cursor

In Cursor Settings → MCP Servers, add:

{
  "mcpServers": {
    "ezeep": {
      "url": "https://mcp.ezeep.com/mcp"
    }
  }
}

Alternative: static refresh token

If your MCP client does not yet implement the MCP OAuth flow, the server also accepts a static refresh token via HTTP headers (X-Refresh-Token, and optionally X-Client-ID if you are using your own registered client rather than the shared public demo client). This path pairs naturally with the API Token Generator — the token it issues works out of the box because both sides use the shared public demo client. It is intended only for evaluation and prototyping.

Most MCP clients (Claude Desktop, Claude Code, GitHub Copilot, Cursor) support this via the mcp-remote helper. Example for Claude Desktop:

{
  "mcpServers": {
    "ezeep": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.ezeep.com/mcp",
        "--header", "X-Refresh-Token:${EZEEP_REFRESH_TOKEN}"
      ],
      "env": {
        "EZEEP_REFRESH_TOKEN": "<refresh token from the API Token Generator>"
      }
    }
  }
}

The other three clients follow the same mcp-remote pattern; adapt the wrapping config-file shape to the client’s schema.

What the MCP can do beyond documentation

Once authenticated, the MCP can list printers, upload documents, submit print jobs, retrieve job status, and — for organization administrators — register a new OAuth Client ID for your production application via a conversational prompt.

Reference

  • Production endpoint: https://mcp.ezeep.com/mcp
  • For advanced configuration questions (multi-tenant setups, self-hosting, custom clients), contact the ezeep Integration Team via the API Contact Form.