How do I add ezeep-mcp to Claude, ChatGPT, or Cursor?

Add ezeep-mcp to Claude, ChatGPT, or Cursor by connecting its remote MCP URL in each client's MCP settings. In Claude, add a custom connector. In ChatGPT, add an MCP app. In Cursor, add an MCP server under Settings. The MCP URL is https://mcp.ezeep.com/mcp.

Is ezeep-mcp MCP ready for ChatGPT and Claude?

As of November 12, 2026, ezeep-mcp scores 78/100 on Manufact's MCP publishing checklist. The scan does not yet meet ChatGPT publishing checks and does not yet meet Claude publishing checks. Passing these checks does not guarantee marketplace approval.

How clear is ezeep-mcp's MCP tool documentation?

As of November 12, 2026, ezeep-mcp scores 55/100 in Manufact's review of tool titles, descriptions, input and output schemas, and behavior annotations. The review covers 34 of 34 discovered tools. The quality score measures documentation clarity; runtime behavior and marketplace readiness require separate checks.

What are the best alternatives to ezeep-mcp?

As of November 12, 2026, alternatives to ezeep-mcp in developer-tools on the Manufact MCP leaderboard include Speko, Manufact, AgentMail, Context, and Speko.

ezeep-mcp: 56/100 Quality

Q: How can ezeep-mcp improve its MCP documentation?

get_api_reference is the lowest-scoring reviewed tool at 30/100. 0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values. Open its review for feedback and a copyable fix prompt, then rerun the documentation review after updating your tool metadata.

list_printersTitles 53Descriptions 78Inputs 50Annotations 0Outputs 048/100

list_printers

Title53/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description78/100

⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets. List all printers available to the authenticated user. This calls the live ezeep cloud printing API and returns real printers connected to the user's organization. **ENDPOINT REFERENCE — there are exactly TWO valid ezeep endpoints for listing printers. Use ONLY one of these EXACT URLs (host + path together — you cannot mix them):** 1. `GET https://printapi.ezeep.com/sfapi/GetPrinter/` — Print API (printers usable by the current user for printing). This is what THIS tool calls. The `/sfapi/GetPrinter/` path is MANDATORY on this host. 2. `GET https://api2.ezeep.com/printing/v1/printers/` — Printing Management API (admin view of all org printers, paginated). The `/printing/v1/` prefix is MANDATORY on this host. **INVALID — DO NOT USE (these hosts/paths do NOT exist and will cause DNS, 404, or HTML-error responses):** - ❌ `https://api.ezeep.com/printers/` (wrong host — there is no `api.ezeep.com`) - ❌ `https://ezeep.com/printers/` - ❌ `https://api2.ezeep.com/printers/` (missing `/printing/v1` prefix) - ❌ `https://printapi.ezeep.com/printers/` (WRONG — `printapi.ezeep.com` ONLY serves the `/sfapi/...` namespace; there is no `/printers/` route on this host) - ❌ `https://printapi.ezeep.com/v1/printers/` or any other path on `printapi.ezeep.com` other than `/sfapi/GetPrinter/` Rule of thumb: `printapi.ezeep.com` → ALWAYS `/sfapi/<Operation>/` (e.g. `/sfapi/GetPrinter/`, `/sfapi/Print/`, `/sfapi/Status/`). `api2.ezeep.com` → ALWAYS `/printing/v1/<resource>/`. Never combine `printapi` host with a `/printers/` path or `api2` host without the `/printing/v1/` prefix. Never invent a different host or shorten these paths. **⚠️ THIS IS A WHOLE-API PROBLEM, NOT JUST `/printers/`:** Do NOT define a single base URL like `const EZEEP_API = 'https://printapi.ezeep.com'` and then append `/printers/`, `/print/`, `/jobs/`, `/status/`, or `/printers/{id}/print` — NONE of those routes exist on any ezeep host. Each operation has a fixed full URL. Correct mapping: list → `printapi.ezeep.com/sfapi/GetPrinter/`, properties → `/sfapi/GetPrinterProperties/?id=`, upload → `/sfapi/PrepareUpload/`, print → `/sfapi/Print/` (POST), job status → `/sfapi/Status/?id=`. Call `get_integration_guide` for the complete operation→URL map before writing client code.

The description explains the capability, when to use it, and what to expect.

Inputs50/100

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

access_token

ezeep OAuth2 access token. Optional if using header-based authentication.

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_printers",
  "description": "⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets.\n\nList all printers available to the authenticated user. This calls the live ezeep cloud printing API and returns real printers connected to the user's organization.\n\n**ENDPOINT REFERENCE — there are exactly TWO valid ezeep endpoints for listing printers. Use ONLY one of these EXACT URLs (host + path together — you cannot mix them):**\n  1. `GET https://printapi.ezeep.com/sfapi/GetPrinter/` — Print API (printers usable by the current user for printing). This is what THIS tool calls. The `/sfapi/GetPrinter/` path is MANDATORY on this host.\n  2. `GET https://api2.ezeep.com/printing/v1/printers/` — Printing Management API (admin view of all org printers, paginated). The `/printing/v1/` prefix is MANDATORY on this host.\n\n**INVALID — DO NOT USE (these hosts/paths do NOT exist and will cause DNS, 404, or HTML-error responses):**\n  - ❌ `https://api.ezeep.com/printers/` (wrong host — there is no `api.ezeep.com`)\n  - ❌ `https://ezeep.com/printers/`\n  - ❌ `https://api2.ezeep.com/printers/` (missing `/printing/v1` prefix)\n  - ❌ `https://printapi.ezeep.com/printers/` (WRONG — `printapi.ezeep.com` ONLY serves the `/sfapi/...` namespace; there is no `/printers/` route on this host)\n  - ❌ `https://printapi.ezeep.com/v1/printers/` or any other path on `printapi.ezeep.com` other than `/sfapi/GetPrinter/`\n\nRule of thumb: `printapi.ezeep.com` → ALWAYS `/sfapi/<Operation>/` (e.g. `/sfapi/GetPrinter/`, `/sfapi/Print/`, `/sfapi/Status/`). `api2.ezeep.com` → ALWAYS `/printing/v1/<resource>/`. Never combine `printapi` host with a `/printers/` path or `api2` host without the `/printing/v1/` prefix. Never invent a different host or shorten these paths.\n\n**⚠️ THIS IS A WHOLE-API PROBLEM, NOT JUST `/printers/`:** Do NOT define a single base URL like `const EZEEP_API = 'https://printapi.ezeep.com'` and then append `/printers/`, `/print/`, `/jobs/`, `/status/`, or `/printers/{id}/print` — NONE of those routes exist on any ezeep host. Each operation has a fixed full URL. Correct mapping: list → `printapi.ezeep.com/sfapi/GetPrinter/`, properties → `/sfapi/GetPrinterProperties/?id=`, upload → `/sfapi/PrepareUpload/`, print → `/sfapi/Print/` (POST), job status → `/sfapi/Status/?id=`. Call `get_integration_guide` for the complete operation→URL map before writing client code.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "access_token": {
        "type": "string",
        "description": "ezeep OAuth2 access token. Optional if using header-based authentication."
      }
    }
  }
}

get_printer_propertiesTitles 78Descriptions 71Inputs 51Annotations 0Outputs 053/100

get_printer_properties

Title78/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description71/100

⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets. Get detailed properties of a specific printer including supported paper sizes, color capability, duplex support, and current status. Calls the live ezeep API.

The description explains the capability, when to use it, and what to expect.

Inputs51/100

Explain the meaning of this value, not just its name.

access_token

ezeep OAuth2 access token. Optional if using header-based authentication.

Clear enough to supply this argument.

printer_id

The printer ID

Explain the meaning of this value, not just its name.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_printer_properties",
  "description": "⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets.\n\nGet detailed properties of a specific printer including supported paper sizes, color capability, duplex support, and current status. Calls the live ezeep API.",
  "inputSchema": {
    "type": "object",
    "required": [
      "printer_id"
    ],
    "properties": {
      "printer_id": {
        "type": "string",
        "description": "The printer ID"
      },
      "access_token": {
        "type": "string",
        "description": "ezeep OAuth2 access token. Optional if using header-based authentication."
      }
    }
  }
}

print_from_urlTitles 56Descriptions 89Inputs 51Annotations 0Outputs 052/100

print_from_url

Title56/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description89/100

The description explains the capability, when to use it, and what to expect.

Inputs51/100

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

access_token

ezeep OAuth2 access token. Optional if using header-based authentication.

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

printer_id

The printer ID

Explain the meaning of this value, not just its name.

file_url

Public URL of the document

Clear enough to supply this argument.

filename

Filename (e.g., 'document.pdf')

Clear enough to supply this argument.

copies

Number of copies

Clear enough to supply this argument.

color

Print in color

Clear enough to supply this argument.

duplex

Duplex mode

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

paper

Paper format

Explain the meaning of this value, not just its name.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "print_from_url",
  "description": "⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets.\n\nPrint a document from a publicly accessible URL to a real physical printer via the ezeep cloud printing service. This sends an actual print job — the document will be printed. Supports PDF, Office documents, and images.",
  "inputSchema": {
    "type": "object",
    "required": [
      "printer_id",
      "file_url",
      "filename"
    ],
    "properties": {
      "color": {
        "type": "boolean",
        "description": "Print in color"
      },
      "paper": {
        "type": "string",
        "description": "Paper format"
      },
      "copies": {
        "type": "number",
        "description": "Number of copies"
      },
      "duplex": {
        "enum": [
          "None",
          "Long",
          "Short"
        ],
        "type": "string",
        "description": "Duplex mode"
      },
      "file_url": {
        "type": "string",
        "description": "Public URL of the document"
      },
      "filename": {
        "type": "string",
        "description": "Filename (e.g., 'document.pdf')"
      },
      "printer_id": {
        "type": "string",
        "description": "The printer ID"
      },
      "access_token": {
        "type": "string",
        "description": "ezeep OAuth2 access token. Optional if using header-based authentication."
      }
    }
  }
}

get_print_job_statusTitles 69Descriptions 75Inputs 50Annotations 0Outputs 052/100

get_print_job_status

Title69/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description75/100

The description explains the capability, when to use it, and what to expect.

Inputs50/100

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

access_token

ezeep OAuth2 access token. Optional if using header-based authentication.

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

job_id

The job ID

Explain the meaning of this value, not just its name.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_print_job_status",
  "description": "⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets.\n\nGet the real-time status of a print job submitted via ezeep. Returns whether the job is queued, printing, completed, or failed.",
  "inputSchema": {
    "type": "object",
    "required": [
      "job_id"
    ],
    "properties": {
      "job_id": {
        "type": "string",
        "description": "The job ID"
      },
      "access_token": {
        "type": "string",
        "description": "ezeep OAuth2 access token. Optional if using header-based authentication."
      }
    }
  }
}

get_supported_filetypesTitles 64Descriptions 62Inputs 50Annotations 0Outputs 047/100

get_supported_filetypes

Title64/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description62/100

Describe the returned information so the agent knows whether it will answer the request.

Inputs50/100

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

access_token

ezeep OAuth2 access token. Optional if using header-based authentication.

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_supported_filetypes",
  "description": "⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets.\n\nGet the list of file types supported for printing by the ezeep service.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "access_token": {
        "type": "string",
        "description": "ezeep OAuth2 access token. Optional if using header-based authentication."
      }
    }
  }
}

prepare_file_uploadTitles 81Descriptions 94Inputs 75Annotations 0Outputs 067/100

prepare_file_upload

Title81/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description94/100

⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets. Prepare a file for upload to ezeep. Returns a SAS URI where the file must be uploaded via HTTP PUT before calling print_uploaded_file. This is for files that are not publicly accessible via URL. **API CONTRACT (strict — provider rejects anything else with HTTP 405):** - Method: **GET** (NEVER POST, PUT, or any other verb) - URL: `https://printapi.ezeep.com/sfapi/PrepareUpload/?filename=<urlencoded-filename>` - `filename` MUST be passed as a URL query parameter — never in a JSON body - No request body. Only the `Authorization: Bearer <token>` header - If you (or downstream code) send POST/JSON the provider returns: `405 Method Not Allowed` This MCP tool calls the endpoint correctly on your behalf — just pass `filename` as the tool argument.

The description explains the capability, when to use it, and what to expect.

Inputs75/100

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

access_token

ezeep OAuth2 access token. Optional if using header-based authentication.

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

filename

Filename to upload (e.g. 'report.pdf'). Sent as the ?filename= query param to GET /sfapi/PrepareUpload/.

Clear enough to supply this argument.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "prepare_file_upload",
  "description": "⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets.\n\nPrepare a file for upload to ezeep. Returns a SAS URI where the file must be uploaded via HTTP PUT before calling print_uploaded_file. This is for files that are not publicly accessible via URL.\n\n**API CONTRACT (strict — provider rejects anything else with HTTP 405):**\n  - Method: **GET** (NEVER POST, PUT, or any other verb)\n  - URL: `https://printapi.ezeep.com/sfapi/PrepareUpload/?filename=<urlencoded-filename>`\n  - `filename` MUST be passed as a URL query parameter — never in a JSON body\n  - No request body. Only the `Authorization: Bearer <token>` header\n  - If you (or downstream code) send POST/JSON the provider returns: `405 Method Not Allowed`\n\nThis MCP tool calls the endpoint correctly on your behalf — just pass `filename` as the tool argument.",
  "inputSchema": {
    "type": "object",
    "required": [
      "filename"
    ],
    "properties": {
      "filename": {
        "type": "string",
        "description": "Filename to upload (e.g. 'report.pdf'). Sent as the ?filename= query param to GET /sfapi/PrepareUpload/."
      },
      "access_token": {
        "type": "string",
        "description": "ezeep OAuth2 access token. Optional if using header-based authentication."
      }
    }
  }
}

print_uploaded_fileTitles 90Descriptions 89Inputs 42Annotations 0Outputs 059/100

print_uploaded_file

Title90/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description89/100

⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets. Print a previously uploaded file to a real physical printer via ezeep. The file must have been uploaded to the SAS URI from prepare_file_upload first. This sends an actual print job.

The description explains the capability, when to use it, and what to expect.

Inputs42/100

4 of 8 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

access_token

ezeep OAuth2 access token. Optional if using header-based authentication.

Clear enough to supply this argument.

file_id

File ID from prepare_file_upload

Clear enough to supply this argument.

printer_id

Printer ID

Explain the meaning of this value, not just its name.

filename

Original filename (e.g., 'report.pdf') — sent as 'alias' to identify the print job

Clear enough to supply this argument.

copies

Not provided

Missing description. Explain what this value means and how to supply it.

color

Not provided

Missing description. Explain what this value means and how to supply it.

duplex

Not provided

Missing description. Explain what this value means and how to supply it.

paper

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "print_uploaded_file",
  "description": "⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets.\n\nPrint a previously uploaded file to a real physical printer via ezeep. The file must have been uploaded to the SAS URI from prepare_file_upload first. This sends an actual print job.",
  "inputSchema": {
    "type": "object",
    "required": [
      "file_id",
      "printer_id"
    ],
    "properties": {
      "color": {
        "type": "boolean"
      },
      "paper": {
        "type": "string"
      },
      "copies": {
        "type": "number"
      },
      "duplex": {
        "enum": [
          "None",
          "Long",
          "Short"
        ],
        "type": "string"
      },
      "file_id": {
        "type": "string",
        "description": "File ID from prepare_file_upload"
      },
      "filename": {
        "type": "string",
        "description": "Original filename (e.g., 'report.pdf') — sent as 'alias' to identify the print job"
      },
      "printer_id": {
        "type": "string",
        "description": "Printer ID"
      },
      "access_token": {
        "type": "string",
        "description": "ezeep OAuth2 access token. Optional if using header-based authentication."
      }
    }
  }
}

list_connectorsTitles 70Descriptions 65Inputs 50Annotations 0Outputs 049/100

list_connectors

Title70/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description65/100

Describe the returned information so the agent knows whether it will answer the request.

Inputs50/100

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

access_token

ezeep OAuth2 access token. Optional if using header-based authentication.

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_connectors",
  "description": "⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets.\n\nList all connectors (hubs/print servers). Requires admin access.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "access_token": {
        "type": "string",
        "description": "ezeep OAuth2 access token. Optional if using header-based authentication."
      }
    }
  }
}

get_organizationTitles 70Descriptions 70Inputs 75Annotations 0Outputs 057/100

get_organization

Title70/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description70/100

⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets. Get the current organization's details (name, ID, settings, subscription). Requires admin access.

The description explains the capability, when to use it, and what to expect.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

access_token

ezeep OAuth2 access token. Optional if using header-based authentication.

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_organization",
  "description": "⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets.\n\nGet the current organization's details (name, ID, settings, subscription). Requires admin access.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "access_token": {
        "type": "string",
        "description": "ezeep OAuth2 access token. Optional if using header-based authentication."
      }
    }
  }
}

get_connector_statusTitles 88Descriptions 59Inputs 48Annotations 0Outputs 052/100

get_connector_status

Title88/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description59/100

Describe the returned information so the agent knows whether it will answer the request.

Inputs48/100

Explain the meaning of this value, not just its name.

access_token

ezeep OAuth2 access token. Optional if using header-based authentication.

Clear enough to supply this argument.

connector_id

Connector ID

Explain the meaning of this value, not just its name.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_connector_status",
  "description": "⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets.\n\nGet status of a specific connector.",
  "inputSchema": {
    "type": "object",
    "required": [
      "connector_id"
    ],
    "properties": {
      "access_token": {
        "type": "string",
        "description": "ezeep OAuth2 access token. Optional if using header-based authentication."
      },
      "connector_id": {
        "type": "string",
        "description": "Connector ID"
      }
    }
  }
}

list_offline_connectorsTitles 74Descriptions 57Inputs 50Annotations 0Outputs 048/100

list_offline_connectors

Title74/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description57/100

Describe the returned information so the agent knows whether it will answer the request.

Inputs50/100

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

access_token

ezeep OAuth2 access token. Optional if using header-based authentication.

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_offline_connectors",
  "description": "⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets.\n\nList all offline connectors.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "access_token": {
        "type": "string",
        "description": "ezeep OAuth2 access token. Optional if using header-based authentication."
      }
    }
  }
}

list_printers_with_issuesTitles 68Descriptions 61Inputs 50Annotations 0Outputs 048/100

list_printers_with_issues

Title68/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description61/100

Describe the concrete operation and its scope instead of restating the tool name.

Inputs50/100

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

access_token

ezeep OAuth2 access token. Optional if using header-based authentication.

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_printers_with_issues",
  "description": "⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets.\n\nList printers with issues or errors.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "access_token": {
        "type": "string",
        "description": "ezeep OAuth2 access token. Optional if using header-based authentication."
      }
    }
  }
}

list_groupsTitles 46Descriptions 59Inputs 75Annotations 0Outputs 048/100

list_groups

Title46/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description59/100

Describe the returned information so the agent knows whether it will answer the request.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

access_token

ezeep OAuth2 access token. Optional if using header-based authentication.

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_groups",
  "description": "⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets.\n\nList all user groups.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "access_token": {
        "type": "string",
        "description": "ezeep OAuth2 access token. Optional if using header-based authentication."
      }
    }
  }
}

create_groupTitles 73Descriptions 56Inputs 50Annotations 0Outputs 048/100

create_group

Title73/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description56/100

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs50/100

2 of 3 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

access_token

ezeep OAuth2 access token. Optional if using header-based authentication.

Clear enough to supply this argument.

name

Group name

Explain the meaning of this value, not just its name.

description

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "create_group",
  "description": "⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets.\n\nCreate a new user group.",
  "inputSchema": {
    "type": "object",
    "required": [
      "name"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "Group name"
      },
      "description": {
        "type": "string"
      },
      "access_token": {
        "type": "string",
        "description": "ezeep OAuth2 access token. Optional if using header-based authentication."
      }
    }
  }
}

assign_printer_to_groupTitles 73Descriptions 53Inputs 30Annotations 0Outputs 042/100

assign_printer_to_group

Title73/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description53/100

Describe the concrete operation and its scope instead of restating the tool name.

Inputs30/100

1 of 3 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

access_token

ezeep OAuth2 access token. Optional if using header-based authentication.

Clear enough to supply this argument.

group_id

Not provided

Missing description. Explain what this value means and how to supply it.

printer_id

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "assign_printer_to_group",
  "description": "⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets.\n\nAssign a printer to a group.",
  "inputSchema": {
    "type": "object",
    "required": [
      "group_id",
      "printer_id"
    ],
    "properties": {
      "group_id": {
        "type": "string"
      },
      "printer_id": {
        "type": "string"
      },
      "access_token": {
        "type": "string",
        "description": "ezeep OAuth2 access token. Optional if using header-based authentication."
      }
    }
  }
}

list_usersTitles 61Descriptions 71Inputs 73Annotations 0Outputs 055/100

list_users

Title61/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description71/100

The description explains the capability, when to use it, and what to expect.

Inputs73/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

access_token

ezeep OAuth2 access token. Optional if using header-based authentication.

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "list_users",
  "description": "⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets.\n\nList all users in the organization with full account details (email, name, roles).",
  "inputSchema": {
    "type": "object",
    "properties": {
      "access_token": {
        "type": "string",
        "description": "ezeep OAuth2 access token. Optional if using header-based authentication."
      }
    }
  }
}

invite_userTitles 65Descriptions 57Inputs 45Annotations 0Outputs 045/100

invite_user

Title65/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description57/100

Explain mutations, irreversible effects, or prerequisites that matter before calling this tool.

Inputs45/100

3 of 5 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

access_token

ezeep OAuth2 access token. Optional if using header-based authentication.

Clear enough to supply this argument.

Email address

Explain the meaning of this value, not just its name.

first_name

Not provided

Missing description. Explain what this value means and how to supply it.

last_name

Not provided

Missing description. Explain what this value means and how to supply it.

expire_days

Days until expiration (default: 7)

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "invite_user",
  "description": "⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets.\n\nInvite a new user by email.",
  "inputSchema": {
    "type": "object",
    "required": [
      "email"
    ],
    "properties": {
      "email": {
        "type": "string",
        "description": "Email address"
      },
      "last_name": {
        "type": "string"
      },
      "first_name": {
        "type": "string"
      },
      "expire_days": {
        "type": "number",
        "description": "Days until expiration (default: 7)"
      },
      "access_token": {
        "type": "string",
        "description": "ezeep OAuth2 access token. Optional if using header-based authentication."
      }
    }
  }
}

add_user_to_groupTitles 59Descriptions 54Inputs 27Annotations 0Outputs 037/100

add_user_to_group

Title59/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description54/100

Describe the concrete operation and its scope instead of restating the tool name.

Inputs27/100

1 of 3 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

access_token

ezeep OAuth2 access token. Optional if using header-based authentication.

Clear enough to supply this argument.

group_id

Not provided

Missing description. Explain what this value means and how to supply it.

user_id

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "add_user_to_group",
  "description": "⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets.\n\nAdd a user to a group.",
  "inputSchema": {
    "type": "object",
    "required": [
      "group_id",
      "user_id"
    ],
    "properties": {
      "user_id": {
        "type": "string"
      },
      "group_id": {
        "type": "string"
      },
      "access_token": {
        "type": "string",
        "description": "ezeep OAuth2 access token. Optional if using header-based authentication."
      }
    }
  }
}

get_integration_guideTitles 59Descriptions 82Inputs 0Annotations 0Outputs 038/100

get_integration_guide

Title59/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description82/100

Get the ezeep printing integration guide. The supported integration path is direct REST calls from a server-side edge function — NOT the ezeep-js library or the `<ezp-printing>` web component. The guide covers authentication (pairing-code flow is the ONLY supported path for deployed apps), refresh-token rotation (single-use, must be persisted to a writable DB row — never to env / platform secrets), and the default ezeep client ID (do NOT prompt the user for a client_id; call `get_default_client_id`).

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

framework

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_integration_guide",
  "description": "Get the ezeep printing integration guide. The supported integration path is direct REST calls from a server-side edge function — NOT the ezeep-js library or the `<ezp-printing>` web component. The guide covers authentication (pairing-code flow is the ONLY supported path for deployed apps), refresh-token rotation (single-use, must be persisted to a writable DB row — never to env / platform secrets), and the default ezeep client ID (do NOT prompt the user for a client_id; call `get_default_client_id`).",
  "inputSchema": {
    "type": "object",
    "properties": {
      "framework": {
        "enum": [
          "react",
          "vue",
          "angular",
          "vanilla"
        ],
        "type": "string"
      }
    }
  }
}

get_api_referenceTitles 61Descriptions 53Inputs 0Annotations 0Outputs 030/100

get_api_reference

Title61/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description53/100

Get API reference documentation. Auth notes: the MCP server provides a default ezeep client ID (do not ask the user for one); refresh tokens are single-use and rotate on every `/oauth/access_token/` exchange — persist the new refresh_token from each response to a writable DB row, never to env / platform secrets.

Describe the concrete operation and its scope instead of restating the tool name.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_api_reference",
  "description": "Get API reference documentation. Auth notes: the MCP server provides a default ezeep client ID (do not ask the user for one); refresh tokens are single-use and rotate on every `/oauth/access_token/` exchange — persist the new refresh_token from each response to a writable DB row, never to env / platform secrets.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "category": {
        "enum": [
          "printing",
          "printers",
          "connectors",
          "groups",
          "users",
          "all"
        ],
        "type": "string"
      }
    }
  }
}

get_code_exampleTitles 62Descriptions 75Inputs 0Annotations 0Outputs 037/100

get_code_example

Title62/100

Not provided

Add a human-readable title so users do not have to interpret the tool identifier.

Description75/100

Get code examples for ezeep operations. The `oauth_flow` and `error_handling` examples show the pairing-code flow (the only supported path for deployed apps) and the rotate-and-persist pattern for refresh tokens (read from DB → exchange → overwrite the same DB row with the new refresh_token from the response). Do NOT read the refresh token from env / platform secrets — it rotates on every exchange.

The description explains the capability, when to use it, and what to expect.

Inputs0/100

0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

operation

Not provided

Missing description. Explain what this value means and how to supply it.

language

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_code_example",
  "description": "Get code examples for ezeep operations. The `oauth_flow` and `error_handling` examples show the pairing-code flow (the only supported path for deployed apps) and the rotate-and-persist pattern for refresh tokens (read from DB → exchange → overwrite the same DB row with the new refresh_token from the response). Do NOT read the refresh token from env / platform secrets — it rotates on every exchange.",
  "inputSchema": {
    "type": "object",
    "required": [
      "operation"
    ],
    "properties": {
      "language": {
        "enum": [
          "javascript",
          "typescript",
          "python",
          "curl"
        ],
        "type": "string"
      },
      "operation": {
        "enum": [
          "print_pdf",
          "upload_and_print",
          "list_printers",
          "oauth_flow",
          "error_handling",
          "batch_print"
        ],
        "type": "string"
      }
    }
  }
}

choose_integration_flowTitles 66Descriptions 95Inputs 100Annotations 0Outputs 070/100

choose_integration_flow

Title66/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description95/100

⛔ FIRST STEP — call this BEFORE any other ezeep tool when the user asks to connect, authenticate, get a token, generate an app token, set up printing, or print something and no token is configured yet. This tool returns a hard-stop picker between two integration models. Surface its output to the user verbatim, then END YOUR TURN and WAIT for the user to reply with 'A' or 'B'. Never auto-select. After the user picks, call `get_integration_steps` with `{ "model": "A" }` or `{ "model": "B" }` and follow its output verbatim — that tool output is the live source of truth and may be newer than any cached description text. Models at a glance: - **A) Shared account** — one ezeep identity for the whole app; self-service via the pairing flow. - **B) Per-user OAuth (multi-user)** — each end-user signs in; setup is self-service via `POST https://account.ezeep.com/v1/oauth-clients/public/` (or reuse an existing `client_id`); 404 fallback only: https://www.ezeep.com/contact/api. This tool takes no input and has no side effects.

The description explains the capability, when to use it, and what to expect.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "choose_integration_flow",
  "description": "⛔ FIRST STEP — call this BEFORE any other ezeep tool when the user asks to connect, authenticate, get a token, generate an app token, set up printing, or print something and no token is configured yet.\n\nThis tool returns a hard-stop picker between two integration models. Surface its output to the user verbatim, then END YOUR TURN and WAIT for the user to reply with 'A' or 'B'. Never auto-select. After the user picks, call `get_integration_steps` with `{ \"model\": \"A\" }` or `{ \"model\": \"B\" }` and follow its output verbatim — that tool output is the live source of truth and may be newer than any cached description text.\n\nModels at a glance:\n- **A) Shared account** — one ezeep identity for the whole app; self-service via the pairing flow.\n- **B) Per-user OAuth (multi-user)** — each end-user signs in; setup is self-service via `POST https://account.ezeep.com/v1/oauth-clients/public/` (or reuse an existing `client_id`); 404 fallback only: https://www.ezeep.com/contact/api.\n\nThis tool takes no input and has no side effects.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  }
}

get_integration_stepsTitles 53Descriptions 96Inputs 75Annotations 0Outputs 060/100

get_integration_steps

Title53/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description96/100

AUTHORITATIVE step-by-step for the integration model the USER explicitly picked. Call this ONLY AFTER `choose_integration_flow` and ONLY AFTER the user has replied 'A' or 'B'. Its output is the live source of truth — it always reflects the current flow and supersedes any cached `instructions` or tool-description text. Pass `{ "model": "A" }` for shared account / pairing, or `{ "model": "B" }` for per-user OAuth.

The description explains the capability, when to use it, and what to expect.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

model

The integration model the USER explicitly picked: A = shared account, B = per-user OAuth.

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_integration_steps",
  "description": "AUTHORITATIVE step-by-step for the integration model the USER explicitly picked. Call this ONLY AFTER `choose_integration_flow` and ONLY AFTER the user has replied 'A' or 'B'. Its output is the live source of truth — it always reflects the current flow and supersedes any cached `instructions` or tool-description text. Pass `{ \"model\": \"A\" }` for shared account / pairing, or `{ \"model\": \"B\" }` for per-user OAuth.",
  "inputSchema": {
    "type": "object",
    "required": [
      "model"
    ],
    "properties": {
      "model": {
        "enum": [
          "A",
          "B"
        ],
        "type": "string",
        "description": "The integration model the USER explicitly picked: A = shared account, B = per-user OAuth."
      }
    }
  }
}

start_hereTitles 40Descriptions 91Inputs 100Annotations 0Outputs 062/100

start_here

Title40/100

Not provided

Name the specific action and subject instead of using a generic label such as ‘manage’ or ‘tool’.

Description91/100

⛔ FIRST STEP for ANY ezeep integration request — alias of `choose_integration_flow`. Returns a hard-stop picker between (A) shared account and (B) per-user OAuth (self-service via `POST /v1/oauth-clients/public/`; 404 fallback only: https://www.ezeep.com/contact/api). Surface the output verbatim, end your turn, and wait for the user to reply 'A' or 'B'. Then call `get_integration_steps` with their choice — that tool's output is the live source of truth.

The description explains the capability, when to use it, and what to expect.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "start_here",
  "description": "⛔ FIRST STEP for ANY ezeep integration request — alias of `choose_integration_flow`. Returns a hard-stop picker between (A) shared account and (B) per-user OAuth (self-service via `POST /v1/oauth-clients/public/`; 404 fallback only: https://www.ezeep.com/contact/api). Surface the output verbatim, end your turn, and wait for the user to reply 'A' or 'B'. Then call `get_integration_steps` with their choice — that tool's output is the live source of truth.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  }
}

get_default_client_idTitles 65Descriptions 97Inputs 100Annotations 0Outputs 070/100

get_default_client_id

Title65/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description97/100

Returns the default ezeep `client_id` that this MCP server uses for the pairing flow. Use this value when generating runtime code (e.g. a Supabase edge function that calls `https://account.ezeep.com/oauth/access_token/`) so you do NOT need to prompt the user for a client_id. Only override with a custom client_id if the user has explicitly been provisioned one by ezeep (per-user OAuth, option B).

The description explains the capability, when to use it, and what to expect.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_default_client_id",
  "description": "Returns the default ezeep `client_id` that this MCP server uses for the pairing flow. Use this value when generating runtime code (e.g. a Supabase edge function that calls `https://account.ezeep.com/oauth/access_token/`) so you do NOT need to prompt the user for a client_id. Only override with a custom client_id if the user has explicitly been provisioned one by ezeep (per-user OAuth, option B).",
  "inputSchema": {
    "type": "object",
    "properties": {}
  }
}

get_access_tokenTitles 53Descriptions 90Inputs 79Annotations 0Outputs 059/100

get_access_token

Title53/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description90/100

⛔ STOP — DO NOT CALL THIS TOOL YET. Before any ezeep authentication, you MUST first call `choose_integration_flow`. Only call this tool after you have a refresh token from a previous successful pairing flow or from app_config. Otherwise call `generate_app_token_pairing_code_authorize` first. --- Exchange a refresh token for an access token. This tool handles authentication internally. **Preferred order for obtaining a refresh token (and you MUST surface the URL/code to the user BEFORE prompting them for any token):** 1. **Pairing code flow (ONLY supported path for deployed apps):** call `generate_app_token_pairing_code_authorize` → show the returned `auth_url` + pairing code to the user as a clickable link → call `generate_app_token_exchange_pairing_code_for_tokens` with the SAME `pairing_code`. **Do NOT ask the user for a refresh token first.** Always present the pairing `auth_url` before any prompt for a token. **Client ID:** Uses the default ezeep client ID provided by the MCP server. **Do not ask the user to provide one.** Only override via `client_id` if the caller has explicitly supplied their own. **⚠️ Refresh-token rotation — CRITICAL:** ezeep refresh tokens are **single-use** and rotate on every exchange. The response of this tool contains a NEW `refresh_token` that MUST be persisted to a **mutable store** (DB row, encrypted KV) by overwriting the previous value. **Never store the refresh token as a long-lived environment variable or platform secret** (e.g. `EZEEP_REFRESH_TOKEN` in `.env`, Supabase / Vercel / Lovable secrets, Vault) — those stores are not safely writable from the running app, so the integration will break the first time the token rotates. Correct pattern: read from DB → exchange → write the new token back to the same DB row. **CRITICAL: The ezeep OAuth endpoint requires the client_id in an Authorization: Basic header (base64 of 'clientId:'), NOT as a form body parameter. This tool handles it correctly automatically.** Authentication paths: 1. **For MCP host clients (Claude Desktop, Cursor, etc.):** Connect via the /oauth endpoint — automatic, no manual tokens needed. 2. **For deployed apps:** Use the pairing flow above; persist tokens to a DB row (NOT to secrets) for reuse and rotation. If the user needs per-user OAuth (each end-user authenticates separately) with full authorization-code + PKCE, that is **self-service**: REUSE an existing public PKCE `client_id` + registered `redirect_uri` if available, otherwise an ezeep org admin registers one via `POST https://account.ezeep.com/v1/oauth-clients/public/` (admin Bearer [redacted]; returns a public `client_id`, no `client_secret`). 404 fallback: if that endpoint is disabled, request provisioning via https://www.ezeep.com/contact/api (or [email protected]). Call `get_integration_guide` for the full step-by-step. Do NOT offer the pairing flow as a substitute for per-user OAuth — the pairing flow gives the whole app one shared ezeep identity. **Error handling — HTTP 400 {"error": "client_invalid"}:** This is a GENERIC error — it does NOT necessarily mean the client_id is invalid. Common causes: - Missing or malformed Authorization: Basic header - client_id passed in the POST body instead of the header - Refresh token already consumed (single-use; confirm you persisted the NEW token from the previous response) - Expired or revoked refresh token

The description explains the capability, when to use it, and what to expect.

Inputs79/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

refresh_token

OAuth2 refresh token obtained via the generate_app_token_pairing_code_authorize + generate_app_token_exchange_pairing_code_for_tokens flow. The response of this tool returns a NEW refresh_token (the old one is invalid); persist it to a DB row and overwrite on each refresh — never store in env / platform secrets.

Clear enough to supply this argument.

client_id

Optional override for the default ezeep client ID. Only set if the caller has explicitly supplied their own client_id — do NOT prompt the user for this. Sent as Authorization: Basic header, NEVER as a form body parameter.

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

scope

OAuth scope

Explain the meaning of this value, not just its name.

acknowledged_integration_flow

Set to true ONLY after `choose_integration_flow` has been called in this conversation and the user has picked an integration model. Setting this without first running the picker is a protocol violation.

Clear enough to supply this argument.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_access_token",
  "description": "⛔ STOP — DO NOT CALL THIS TOOL YET.\n\nBefore any ezeep authentication, you MUST first call `choose_integration_flow`. Only call this tool after you have a refresh token from a previous successful pairing flow or from app_config. Otherwise call `generate_app_token_pairing_code_authorize` first.\n\n---\n\nExchange a refresh token for an access token. This tool handles authentication internally.\n\n**Preferred order for obtaining a refresh token (and you MUST surface the URL/code to the user BEFORE prompting them for any token):**\n1. **Pairing code flow (ONLY supported path for deployed apps):** call `generate_app_token_pairing_code_authorize` → show the returned `auth_url` + pairing code to the user as a clickable link → call `generate_app_token_exchange_pairing_code_for_tokens` with the SAME `pairing_code`.\n\n**Do NOT ask the user for a refresh token first.** Always present the pairing `auth_url` before any prompt for a token.\n\n**Client ID:** Uses the default ezeep client ID provided by the MCP server. **Do not ask the user to provide one.** Only override via `client_id` if the caller has explicitly supplied their own.\n\n**⚠️ Refresh-token rotation — CRITICAL:** ezeep refresh tokens are **single-use** and rotate on every exchange. The response of this tool contains a NEW `refresh_token` that MUST be persisted to a **mutable store** (DB row, encrypted KV) by overwriting the previous value. **Never store the refresh token as a long-lived environment variable or platform secret** (e.g. `EZEEP_REFRESH_TOKEN` in `.env`, Supabase / Vercel / Lovable secrets, Vault) — those stores are not safely writable from the running app, so the integration will break the first time the token rotates. Correct pattern: read from DB → exchange → write the new token back to the same DB row.\n\n**CRITICAL: The ezeep OAuth endpoint requires the client_id in an Authorization: Basic header (base64 of 'clientId:'), NOT as a form body parameter. This tool handles it correctly automatically.**\n\nAuthentication paths:\n1. **For MCP host clients (Claude Desktop, Cursor, etc.):** Connect via the /oauth endpoint — automatic, no manual tokens needed.\n2. **For deployed apps:** Use the pairing flow above; persist tokens to a DB row (NOT to secrets) for reuse and rotation.\n\nIf the user needs per-user OAuth (each end-user authenticates separately) with full authorization-code + PKCE, that is **self-service**: REUSE an existing public PKCE `client_id` + registered `redirect_uri` if available, otherwise an ezeep org admin registers one via `POST https://account.ezeep.com/v1/oauth-clients/public/` (admin Bearer [redacted]; returns a public `client_id`, no `client_secret`). 404 fallback: if that endpoint is disabled, request provisioning via https://www.ezeep.com/contact/api (or [email protected]). Call `get_integration_guide` for the full step-by-step. Do NOT offer the pairing flow as a substitute for per-user OAuth — the pairing flow gives the whole app one shared ezeep identity.\n\n**Error handling — HTTP 400 {\"error\": \"client_invalid\"}:**\nThis is a GENERIC error — it does NOT necessarily mean the client_id is invalid. Common causes:\n- Missing or malformed Authorization: Basic header\n- client_id passed in the POST body instead of the header\n- Refresh token already consumed (single-use; confirm you persisted the NEW token from the previous response)\n- Expired or revoked refresh token",
  "inputSchema": {
    "type": "object",
    "required": [
      "refresh_token"
    ],
    "properties": {
      "scope": {
        "enum": [
          "printing",
          "accounts"
        ],
        "type": "string",
        "description": "OAuth scope"
      },
      "client_id": {
        "type": "string",
        "description": "Optional override for the default ezeep client ID. Only set if the caller has explicitly supplied their own client_id — do NOT prompt the user for this. Sent as Authorization: Basic header, NEVER as a form body parameter."
      },
      "refresh_token": {
        "type": "string",
        "description": "OAuth2 refresh token obtained via the generate_app_token_pairing_code_authorize + generate_app_token_exchange_pairing_code_for_tokens flow. The response of this tool returns a NEW refresh_token (the old one is invalid); persist it to a DB row and overwrite on each refresh — never store in env / platform secrets."
      },
      "acknowledged_integration_flow": {
        "type": "boolean",
        "description": "Set to true ONLY after `choose_integration_flow` has been called in this conversation and the user has picked an integration model. Setting this without first running the picker is a protocol violation."
      }
    }
  }
}

generate_app_token_pairing_code_authorizeTitles 55Descriptions 97Inputs 67Annotations 0Outputs 058/100

generate_app_token_pairing_code_authorize

Title55/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description97/100

⛔ STOP — DO NOT CALL THIS TOOL YET. Before calling this tool, you MUST first call `choose_integration_flow`. This tool provisions a single ezeep identity for your app (personal / API printing mode). If the user needs per-user OAuth (each end-user authenticates separately), do NOT use this tool — instead register a public PKCE client self-service via `POST https://account.ezeep.com/v1/oauth-clients/public/` (admin Bearer [redacted]; returns a public `client_id`, no `client_secret`) — or REUSE an existing one — and run standard OAuth 2.0 Authorization Code + PKCE per user. **404 fallback:** if that endpoint is disabled in the environment, request provisioning via https://www.ezeep.com/contact/api (or [email protected]). Call `get_integration_guide` for the full step-by-step. Only call this tool after calling `choose_integration_flow`, and you must pass `acknowledged_shared_account_model: true`. The server will reject the call otherwise. --- STEP 1 of 2 — Generate App Token: request a pairing code and return the authorization URL. This tool POSTs to ezeep `/oauth/pair/` and returns immediately. It does NOT block, queue, or poll. **IMPORTANT:** the first response content item is already the exact user-facing message and its FIRST LINE is the raw auth URL. Show that first content item to the user verbatim and end the turn immediately. Do NOT call another tool, do NOT keep thinking, do NOT say you are waiting, and do NOT add extra analysis. The human must finish authorization in the browser before STEP 2 can happen. **Call it once per pairing:** every call issues a NEW pairing_code and auth_url. In STEP 2, pass the pairing_code that belongs to the auth_url you showed the user. Do not loop — show the URL and stop. **Default client ID:** if `client_id` is omitted, this tool uses the public ezeep client ID `yjavNwKpd4HgbQes0ekYHBGjxIoszJgayIc0JkdB`. After the user confirms authorization in chat, IMMEDIATELY call STEP 2: `finalize_app_token_no_user_action` (legacy alias `generate_app_token_exchange_pairing_code_for_tokens`) with the same pairing_code. STEP 2 has NO user step — do NOT say you are "waiting for approval" or "waiting for confirmation" between Step 1 and Step 2. Endpoint (handled by this tool): POST https://account.ezeep.com/oauth/pair/ Authorization: Basic base64(client_id + ":") body {"scope":"printing","mode":"user"}

The description explains the capability, when to use it, and what to expect.

Inputs67/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

acknowledged_shared_account_model

REQUIRED. Must be true. Set this to true ONLY after you have called `choose_integration_flow` and confirmed the single-user / personal / API printing mode is appropriate. The server will reject this call if this flag is missing or false.

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

scope

OAuth scope for the token. Default: printing.

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

client_id

Optional OAuth2 client ID. If omitted, uses the default ezeep public client ID.

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "generate_app_token_pairing_code_authorize",
  "description": "⛔ STOP — DO NOT CALL THIS TOOL YET.\n\nBefore calling this tool, you MUST first call `choose_integration_flow`. This tool provisions a single ezeep identity for your app (personal / API printing mode). If the user needs per-user OAuth (each end-user authenticates separately), do NOT use this tool — instead register a public PKCE client self-service via `POST https://account.ezeep.com/v1/oauth-clients/public/` (admin Bearer [redacted]; returns a public `client_id`, no `client_secret`) — or REUSE an existing one — and run standard OAuth 2.0 Authorization Code + PKCE per user. **404 fallback:** if that endpoint is disabled in the environment, request provisioning via https://www.ezeep.com/contact/api (or [email protected]). Call `get_integration_guide` for the full step-by-step.\n\nOnly call this tool after calling `choose_integration_flow`, and you must pass `acknowledged_shared_account_model: true`. The server will reject the call otherwise.\n\n---\n\nSTEP 1 of 2 — Generate App Token: request a pairing code and return the authorization URL.\n\nThis tool POSTs to ezeep `/oauth/pair/` and returns immediately. It does NOT block, queue, or poll.\n\n**IMPORTANT:** the first response content item is already the exact user-facing message and its FIRST LINE is the raw auth URL. Show that first content item to the user verbatim and end the turn immediately.\n\nDo NOT call another tool, do NOT keep thinking, do NOT say you are waiting, and do NOT add extra analysis. The human must finish authorization in the browser before STEP 2 can happen.\n\n**Call it once per pairing:** every call issues a NEW pairing_code and auth_url. In STEP 2, pass the pairing_code that belongs to the auth_url you showed the user. Do not loop — show the URL and stop.\n\n**Default client ID:** if `client_id` is omitted, this tool uses the public ezeep client ID `yjavNwKpd4HgbQes0ekYHBGjxIoszJgayIc0JkdB`.\n\nAfter the user confirms authorization in chat, IMMEDIATELY call STEP 2: `finalize_app_token_no_user_action` (legacy alias `generate_app_token_exchange_pairing_code_for_tokens`) with the same pairing_code. STEP 2 has NO user step — do NOT say you are \"waiting for approval\" or \"waiting for confirmation\" between Step 1 and Step 2.\n\nEndpoint (handled by this tool): POST https://account.ezeep.com/oauth/pair/  Authorization: Basic base64(client_id + \":\")  body {\"scope\":\"printing\",\"mode\":\"user\"}",
  "inputSchema": {
    "type": "object",
    "required": [
      "acknowledged_shared_account_model"
    ],
    "properties": {
      "scope": {
        "enum": [
          "printing",
          "accounts"
        ],
        "type": "string",
        "description": "OAuth scope for the token. Default: printing."
      },
      "client_id": {
        "type": "string",
        "description": "Optional OAuth2 client ID. If omitted, uses the default ezeep public client ID."
      },
      "acknowledged_shared_account_model": {
        "type": "boolean",
        "description": "REQUIRED. Must be true. Set this to true ONLY after you have called `choose_integration_flow` and confirmed the single-user / personal / API printing mode is appropriate. The server will reject this call if this flag is missing or false."
      }
    }
  }
}

finalize_app_token_no_user_actionTitles 97Descriptions 89Inputs 75Annotations 100Outputs 080/100

finalize_app_token_no_user_action

Title97/100

Finalize App Token (server-side, no user step)

Shorten the title to an action and subject; move usage details into the description.

Description89/100

⛔ STOP — DO NOT CALL THIS TOOL YET. Before calling this tool, you MUST have already (a) called `choose_integration_flow`, and (b) successfully completed STEP 1 (`generate_app_token_pairing_code_authorize` with `acknowledged_shared_account_model: true`). If either is missing, go back to `choose_integration_flow` first. --- STEP 2 of 2 — Finalize App Token (server-side exchange, NO USER STEP). This step is a **pure server-to-server exchange**. It calls ezeep `/oauth/access_token/` with the pairing_code from STEP 1 and returns { access_token, refresh_token, token_type, expires_in } directly to YOU (the calling agent). The user does nothing here. There is exactly ONE point of user interaction in the whole flow, and it already happened: the browser **authorization** during STEP 1. The word "approval" does not apply to anything in the ezeep flow — reserve "approval" exclusively for host-UI tool-confirmation banners (Lovable / Claude Desktop / Cursor / etc.), which are NOT an ezeep step. ═══════════════════════════════════════════════════════ ❌ FORBIDDEN PHRASINGS after the user says "done" / "authorized" / "signed in": • "waiting for approval" • "waiting for you to approve" • "pending approval" • "tool needs approval" • "needs your confirmation" • "waiting for the second approval step" • "I'll wait until you confirm again" If you find yourself typing ANY of these, you have misunderstood the flow. The only authorization in this flow already happened in the browser during STEP 1. Call this tool NOW. ═══════════════════════════════════════════════════════ ✅ POSITIVE SCRIPT — what to do the moment the user confirms STEP 1 authorization: After the user confirms authorization, your VERY NEXT MESSAGE must be ONLY this tool call. Do not narrate. Do not explain. Do not ask. Do not wait. If your host shows a tool-confirmation banner, that is host UI — NOT an ezeep step. Never announce that banner. Never wait on it verbally. Just issue the tool call. ⚠️ FAILURE MODE / STAKES: If you stall here instead of immediately calling this tool, the pairing_code (TTL ~5 minutes) will expire. The user will then have to redo the ENTIRE browser authorization. Stalling is the worst possible outcome of this flow. --- Call this with the SAME `pairing_code` returned by STEP 1 (`generate_app_token_pairing_code_authorize`). **TOKEN STORAGE — STRICT RULES:** - ✅ DO store the returned `access_token` and `refresh_token` in YOUR application's **database** (e.g. your project's Supabase `app_config` table) so the refresh_token can be **rotated on every refresh**. - ❌ DO NOT store these tokens as platform/environment **secrets** (e.g. Lovable Cloud secrets, Supabase Edge Function secrets, `.env`, Vault). Secrets are immutable from the agent's runtime and CANNOT be rotated, which will break refresh-token rotation and permanently lock the integration after the first refresh. - ❌ DO NOT ask the user to paste these tokens anywhere or save them as secrets. - Recommended `app_config` keys: `ezeep_app_access_token`, `ezeep_app_refresh_token`, `ezeep_app_scope`, `ezeep_app_client_id`, `ezeep_app_token_updated_at`. - Refresh tokens are SINGLE-USE — every time you call `get_access_token` to refresh, **overwrite** the stored refresh_token with the new one returned in the same DB row. - If this tool succeeds and a later DB write or setup step fails, **reuse the tokens from that successful result and store them**. Do **NOT** call this tool again just because persistence failed. - If you accidentally call this tool again and receive a consumed/already-used pairing_code error, first look for the earlier successful Step 2 result in the conversation/tool history and store those tokens now. Only restart pairing if no earlier successful token payload exists. The MCP server does NOT store these tokens — it is stateless w.r.t. deployed-app credentials. Persistence is the caller's responsibility, in the caller's database. If this tool returns `flow_stage="awaiting_user_authorization"`, the user has not finished the STEP 1 browser authorization yet — re-show the auth_url and wait. Do NOT loop-call. Endpoint (handled by this tool): https://account.ezeep.com/oauth/access_token/ with the authorized pairing_code (Authorization: Basic base64(client_id + ":")).

The description explains the capability, when to use it, and what to expect.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

pairing_code

The pairing code returned by generate_app_token_pairing_code_authorize (Step 1). Required.

Clear enough to supply this argument.

scope

OAuth scope for the token. Must match the scope used in Step 1. Default: printing.

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

client_id

Optional OAuth2 client ID. Must match the one used in Step 1 (or omit in both calls).

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

Annotations100/100

All four behavior hints are declared.

{
  "title": "Finalize App Token (server-side, no user step)",
  "readOnlyHint": false,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "finalize_app_token_no_user_action",
  "description": "⛔ STOP — DO NOT CALL THIS TOOL YET.\n\nBefore calling this tool, you MUST have already (a) called `choose_integration_flow`, and (b) successfully completed STEP 1 (`generate_app_token_pairing_code_authorize` with `acknowledged_shared_account_model: true`). If either is missing, go back to `choose_integration_flow` first.\n\n---\n\nSTEP 2 of 2 — Finalize App Token (server-side exchange, NO USER STEP).\n\nThis step is a **pure server-to-server exchange**. It calls ezeep `/oauth/access_token/` with the pairing_code from STEP 1 and returns { access_token, refresh_token, token_type, expires_in } directly to YOU (the calling agent). The user does nothing here.\n\nThere is exactly ONE point of user interaction in the whole flow, and it already happened: the browser **authorization** during STEP 1. The word \"approval\" does not apply to anything in the ezeep flow — reserve \"approval\" exclusively for host-UI tool-confirmation banners (Lovable / Claude Desktop / Cursor / etc.), which are NOT an ezeep step.\n\n═══════════════════════════════════════════════════════\n❌ FORBIDDEN PHRASINGS after the user says \"done\" / \"authorized\" / \"signed in\":\n  • \"waiting for approval\"\n  • \"waiting for you to approve\"\n  • \"pending approval\"\n  • \"tool needs approval\"\n  • \"needs your confirmation\"\n  • \"waiting for the second approval step\"\n  • \"I'll wait until you confirm again\"\n\nIf you find yourself typing ANY of these, you have misunderstood the flow.\nThe only authorization in this flow already happened in the browser during STEP 1.\nCall this tool NOW.\n═══════════════════════════════════════════════════════\n\n✅ POSITIVE SCRIPT — what to do the moment the user confirms STEP 1 authorization:\n\n  After the user confirms authorization, your VERY NEXT MESSAGE must be ONLY this tool call.\n  Do not narrate. Do not explain. Do not ask. Do not wait.\n  If your host shows a tool-confirmation banner, that is host UI — NOT an ezeep step.\n  Never announce that banner. Never wait on it verbally. Just issue the tool call.\n\n⚠️ FAILURE MODE / STAKES:\n\n  If you stall here instead of immediately calling this tool, the pairing_code\n  (TTL ~5 minutes) will expire. The user will then have to redo the ENTIRE\n  browser authorization. Stalling is the worst possible outcome of this flow.\n\n---\n\nCall this with the SAME `pairing_code` returned by STEP 1 (`generate_app_token_pairing_code_authorize`).\n\n**TOKEN STORAGE — STRICT RULES:**\n- ✅ DO store the returned `access_token` and `refresh_token` in YOUR application's **database** (e.g. your project's Supabase `app_config` table) so the refresh_token can be **rotated on every refresh**.\n- ❌ DO NOT store these tokens as platform/environment **secrets** (e.g. Lovable Cloud secrets, Supabase Edge Function secrets, `.env`, Vault). Secrets are immutable from the agent's runtime and CANNOT be rotated, which will break refresh-token rotation and permanently lock the integration after the first refresh.\n- ❌ DO NOT ask the user to paste these tokens anywhere or save them as secrets.\n- Recommended `app_config` keys: `ezeep_app_access_token`, `ezeep_app_refresh_token`, `ezeep_app_scope`, `ezeep_app_client_id`, `ezeep_app_token_updated_at`.\n- Refresh tokens are SINGLE-USE — every time you call `get_access_token` to refresh, **overwrite** the stored refresh_token with the new one returned in the same DB row.\n- If this tool succeeds and a later DB write or setup step fails, **reuse the tokens from that successful result and store them**. Do **NOT** call this tool again just because persistence failed.\n- If you accidentally call this tool again and receive a consumed/already-used pairing_code error, first look for the earlier successful Step 2 result in the conversation/tool history and store those tokens now. Only restart pairing if no earlier successful token payload exists.\n\nThe MCP server does NOT store these tokens — it is stateless w.r.t. deployed-app credentials. Persistence is the caller's responsibility, in the caller's database.\n\nIf this tool returns `flow_stage=\"awaiting_user_authorization\"`, the user has not finished the STEP 1 browser authorization yet — re-show the auth_url and wait. Do NOT loop-call.\n\nEndpoint (handled by this tool): https://account.ezeep.com/oauth/access_token/ with the authorized pairing_code (Authorization: Basic base64(client_id + \":\")).",
  "inputSchema": {
    "type": "object",
    "required": [
      "pairing_code"
    ],
    "properties": {
      "scope": {
        "enum": [
          "printing",
          "accounts"
        ],
        "type": "string",
        "description": "OAuth scope for the token. Must match the scope used in Step 1. Default: printing."
      },
      "client_id": {
        "type": "string",
        "description": "Optional OAuth2 client ID. Must match the one used in Step 1 (or omit in both calls)."
      },
      "pairing_code": {
        "type": "string",
        "description": "The pairing code returned by generate_app_token_pairing_code_authorize (Step 1). Required."
      }
    }
  },
  "annotations": {
    "title": "Finalize App Token (server-side, no user step)",
    "readOnlyHint": false,
    "openWorldHint": true,
    "idempotentHint": false,
    "destructiveHint": false
  }
}

generate_app_token_exchange_pairing_code_for_tokensTitles 90Descriptions 86Inputs 75Annotations 100Outputs 077/100

generate_app_token_exchange_pairing_code_for_tokens

Title90/100

Finalize App Token (server-side, no user step)

Shorten the title to an action and subject; move usage details into the description.

Description86/100

The description explains the capability, when to use it, and what to expect.

Inputs75/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

pairing_code

The pairing code returned by generate_app_token_pairing_code_authorize (Step 1). Required.

Clear enough to supply this argument.

scope

OAuth scope for the token. Must match the scope used in Step 1. Default: printing.

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

client_id

Optional OAuth2 client ID. Must match the one used in Step 1 (or omit in both calls).

Clarify units, where to obtain this value, or conventions not already expressed in the schema.

Annotations100/100

All four behavior hints are declared.

{
  "title": "Finalize App Token (server-side, no user step)",
  "readOnlyHint": false,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "generate_app_token_exchange_pairing_code_for_tokens",
  "description": "⛔ STOP — DO NOT CALL THIS TOOL YET.\n\nBefore calling this tool, you MUST have already (a) called `choose_integration_flow`, and (b) successfully completed STEP 1 (`generate_app_token_pairing_code_authorize` with `acknowledged_shared_account_model: true`). If either is missing, go back to `choose_integration_flow` first.\n\n---\n\nSTEP 2 of 2 — Finalize App Token (server-side exchange, NO USER STEP).\n\nThis step is a **pure server-to-server exchange**. It calls ezeep `/oauth/access_token/` with the pairing_code from STEP 1 and returns { access_token, refresh_token, token_type, expires_in } directly to YOU (the calling agent). The user does nothing here.\n\nThere is exactly ONE point of user interaction in the whole flow, and it already happened: the browser **authorization** during STEP 1. The word \"approval\" does not apply to anything in the ezeep flow — reserve \"approval\" exclusively for host-UI tool-confirmation banners (Lovable / Claude Desktop / Cursor / etc.), which are NOT an ezeep step.\n\n═══════════════════════════════════════════════════════\n❌ FORBIDDEN PHRASINGS after the user says \"done\" / \"authorized\" / \"signed in\":\n  • \"waiting for approval\"\n  • \"waiting for you to approve\"\n  • \"pending approval\"\n  • \"tool needs approval\"\n  • \"needs your confirmation\"\n  • \"waiting for the second approval step\"\n  • \"I'll wait until you confirm again\"\n\nIf you find yourself typing ANY of these, you have misunderstood the flow.\nThe only authorization in this flow already happened in the browser during STEP 1.\nCall this tool NOW.\n═══════════════════════════════════════════════════════\n\n✅ POSITIVE SCRIPT — what to do the moment the user confirms STEP 1 authorization:\n\n  After the user confirms authorization, your VERY NEXT MESSAGE must be ONLY this tool call.\n  Do not narrate. Do not explain. Do not ask. Do not wait.\n  If your host shows a tool-confirmation banner, that is host UI — NOT an ezeep step.\n  Never announce that banner. Never wait on it verbally. Just issue the tool call.\n\n⚠️ FAILURE MODE / STAKES:\n\n  If you stall here instead of immediately calling this tool, the pairing_code\n  (TTL ~5 minutes) will expire. The user will then have to redo the ENTIRE\n  browser authorization. Stalling is the worst possible outcome of this flow.\n\n---\n\nCall this with the SAME `pairing_code` returned by STEP 1 (`generate_app_token_pairing_code_authorize`).\n\n**TOKEN STORAGE — STRICT RULES:**\n- ✅ DO store the returned `access_token` and `refresh_token` in YOUR application's **database** (e.g. your project's Supabase `app_config` table) so the refresh_token can be **rotated on every refresh**.\n- ❌ DO NOT store these tokens as platform/environment **secrets** (e.g. Lovable Cloud secrets, Supabase Edge Function secrets, `.env`, Vault). Secrets are immutable from the agent's runtime and CANNOT be rotated, which will break refresh-token rotation and permanently lock the integration after the first refresh.\n- ❌ DO NOT ask the user to paste these tokens anywhere or save them as secrets.\n- Recommended `app_config` keys: `ezeep_app_access_token`, `ezeep_app_refresh_token`, `ezeep_app_scope`, `ezeep_app_client_id`, `ezeep_app_token_updated_at`.\n- Refresh tokens are SINGLE-USE — every time you call `get_access_token` to refresh, **overwrite** the stored refresh_token with the new one returned in the same DB row.\n- If this tool succeeds and a later DB write or setup step fails, **reuse the tokens from that successful result and store them**. Do **NOT** call this tool again just because persistence failed.\n- If you accidentally call this tool again and receive a consumed/already-used pairing_code error, first look for the earlier successful Step 2 result in the conversation/tool history and store those tokens now. Only restart pairing if no earlier successful token payload exists.\n\nThe MCP server does NOT store these tokens — it is stateless w.r.t. deployed-app credentials. Persistence is the caller's responsibility, in the caller's database.\n\nIf this tool returns `flow_stage=\"awaiting_user_authorization\"`, the user has not finished the STEP 1 browser authorization yet — re-show the auth_url and wait. Do NOT loop-call.\n\nEndpoint (handled by this tool): https://account.ezeep.com/oauth/access_token/ with the authorized pairing_code (Authorization: Basic base64(client_id + \":\")).",
  "inputSchema": {
    "type": "object",
    "required": [
      "pairing_code"
    ],
    "properties": {
      "scope": {
        "enum": [
          "printing",
          "accounts"
        ],
        "type": "string",
        "description": "OAuth scope for the token. Must match the scope used in Step 1. Default: printing."
      },
      "client_id": {
        "type": "string",
        "description": "Optional OAuth2 client ID. Must match the one used in Step 1 (or omit in both calls)."
      },
      "pairing_code": {
        "type": "string",
        "description": "The pairing code returned by generate_app_token_pairing_code_authorize (Step 1). Required."
      }
    }
  },
  "annotations": {
    "title": "Finalize App Token (server-side, no user step)",
    "readOnlyHint": false,
    "openWorldHint": true,
    "idempotentHint": false,
    "destructiveHint": false
  }
}

start_pairingTitles 61Descriptions 94Inputs 83Annotations 0Outputs 063/100

start_pairing

Title61/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description94/100

⛔ Step 1 of the shared-account pairing flow — alias of `generate_app_token_pairing_code_authorize`. Returns auth_url + pairing_code. Show auth_url to the user immediately, end the turn, then call `exchange_pairing` after the user confirms authorization.

The description explains the capability, when to use it, and what to expect.

Inputs83/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

acknowledged_shared_account_model

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

scope

OAuth scope for the token. Default: printing.

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

client_id

Optional OAuth2 client ID. If omitted, uses the default ezeep public client ID.

Clear enough to supply this argument.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "start_pairing",
  "description": "⛔ Step 1 of the shared-account pairing flow — alias of `generate_app_token_pairing_code_authorize`. Returns auth_url + pairing_code. Show auth_url to the user immediately, end the turn, then call `exchange_pairing` after the user confirms authorization.",
  "inputSchema": {
    "type": "object",
    "required": [
      "acknowledged_shared_account_model"
    ],
    "properties": {
      "scope": {
        "enum": [
          "printing",
          "accounts"
        ],
        "type": "string",
        "description": "OAuth scope for the token. Default: printing."
      },
      "client_id": {
        "type": "string",
        "description": "Optional OAuth2 client ID. If omitted, uses the default ezeep public client ID."
      },
      "acknowledged_shared_account_model": {
        "type": "boolean",
        "description": "REQUIRED. Must be true. Set this to true ONLY after you have called `choose_integration_flow` and confirmed the single-user / personal / API printing mode is appropriate. The server will reject this call if this flag is missing or false."
      }
    }
  }
}

exchange_pairingTitles 84Descriptions 91Inputs 92Annotations 100Outputs 081/100

exchange_pairing

Title84/100

Finalize App Token (server-side, no user step)

Shorten the title to an action and subject; move usage details into the description.

Description91/100

⛔ Step 2 of the shared-account pairing flow — alias of `generate_app_token_exchange_pairing_code_for_tokens`. Takes the pairing_code from `start_pairing` and exchanges it for {access_token, refresh_token}. Persist the tokens to a writable DB row.

Describe the returned information so the agent knows whether it will answer the request.

Inputs92/100

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

pairing_code

The pairing code returned by generate_app_token_pairing_code_authorize (Step 1). Required.

Clear enough to supply this argument.

scope

OAuth scope for the token. Must match the scope used in Step 1. Default: printing.

Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.

client_id

Optional OAuth2 client ID. Must match the one used in Step 1 (or omit in both calls).

Clear enough to supply this argument.

Annotations100/100

All four behavior hints are declared.

{
  "title": "Finalize App Token (server-side, no user step)",
  "readOnlyHint": false,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "exchange_pairing",
  "description": "⛔ Step 2 of the shared-account pairing flow — alias of `generate_app_token_exchange_pairing_code_for_tokens`. Takes the pairing_code from `start_pairing` and exchanges it for {access_token, refresh_token}. Persist the tokens to a writable DB row.",
  "inputSchema": {
    "type": "object",
    "required": [
      "pairing_code"
    ],
    "properties": {
      "scope": {
        "enum": [
          "printing",
          "accounts"
        ],
        "type": "string",
        "description": "OAuth scope for the token. Must match the scope used in Step 1. Default: printing."
      },
      "client_id": {
        "type": "string",
        "description": "Optional OAuth2 client ID. Must match the one used in Step 1 (or omit in both calls)."
      },
      "pairing_code": {
        "type": "string",
        "description": "The pairing code returned by generate_app_token_pairing_code_authorize (Step 1). Required."
      }
    }
  },
  "annotations": {
    "title": "Finalize App Token (server-side, no user step)",
    "readOnlyHint": false,
    "openWorldHint": true,
    "idempotentHint": false,
    "destructiveHint": false
  }
}

get_token_infoTitles 56Descriptions 75Inputs 91Annotations 0Outputs 059/100

get_token_info

Title56/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description75/100

⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets. Decode and return the claims from the current authenticated JWT access token. Shows sub, org, exp, scopes, roles, and other claims. Does NOT require any parameters when using header-based authentication.

The description explains the capability, when to use it, and what to expect.

Inputs91/100

Input documentation gives an agent enough context to populate the arguments.

access_token

Optional access token to inspect. If omitted, uses token from Authorization header or X-Client-ID/X-Refresh-Token auto-exchange.

Clear enough to supply this argument.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_token_info",
  "description": "⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets.\n\nDecode and return the claims from the current authenticated JWT access token. Shows sub, org, exp, scopes, roles, and other claims. Does NOT require any parameters when using header-based authentication.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "access_token": {
        "type": "string",
        "description": "Optional access token to inspect. If omitted, uses token from Authorization header or X-Client-ID/X-Refresh-Token auto-exchange."
      }
    }
  }
}

register_oauth_clientTitles 58Descriptions 97Inputs 90Annotations 0Outputs 065/100

register_oauth_client

Title58/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description97/100

⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets. Register (or reuse) a public PKCE OAuth client in the ezeep org of the currently-connected MCP account. Use this in integration model B (per-user OAuth) so the agent can provision the `client_id` automatically instead of asking the dev to run curl. Requires the MCP connection to be an ORG ADMIN with `accounts` scope. Reuse-first: if an existing client already covers all requested `redirect_urls`, returns its `client_id` with `reused: true`. The returned `client_id` is PUBLIC (no `client_secret` — PKCE protects it). Never use the pairing/device flow as a substitute for this.

The description explains the capability, when to use it, and what to expect.

Inputs90/100

Explain the meaning of this value, not just its name.

name

Display name for the OAuth client / your app.

Clear enough to supply this argument.

redirect_urls

Exact callback URL(s) for OAuth (HTTPS only; `localhost` allowed). No wildcards, no fragments. List both dev and prod if needed.

Clear enough to supply this argument.

allowed_scopes

Space-separated allowed scopes. Defaults to `printing.print printing.documents.upload printing.printers.readonly openid profile`.

Explain the meaning of this value, not just its name.

tenant_mode

`single` = only users of the owning org can sign in (most apps); `multi` = users from any ezeep org (true multi-tenant SaaS). IMMUTABLE after creation. Defaults to `single`.

Clear enough to supply this argument.

external_description

Optional short description shown on the consent screen.

Clear enough to supply this argument.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "register_oauth_client",
  "description": "⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets.\n\nRegister (or reuse) a public PKCE OAuth client in the ezeep org of the currently-connected MCP account. Use this in integration model B (per-user OAuth) so the agent can provision the `client_id` automatically instead of asking the dev to run curl. Requires the MCP connection to be an ORG ADMIN with `accounts` scope. Reuse-first: if an existing client already covers all requested `redirect_urls`, returns its `client_id` with `reused: true`. The returned `client_id` is PUBLIC (no `client_secret` — PKCE protects it). Never use the pairing/device flow as a substitute for this.",
  "inputSchema": {
    "type": "object",
    "required": [
      "name",
      "redirect_urls"
    ],
    "properties": {
      "name": {
        "type": "string",
        "description": "Display name for the OAuth client / your app."
      },
      "tenant_mode": {
        "enum": [
          "single",
          "multi"
        ],
        "type": "string",
        "description": "`single` = only users of the owning org can sign in (most apps); `multi` = users from any ezeep org (true multi-tenant SaaS). IMMUTABLE after creation. Defaults to `single`."
      },
      "redirect_urls": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Exact callback URL(s) for OAuth (HTTPS only; `localhost` allowed). No wildcards, no fragments. List both dev and prod if needed."
      },
      "allowed_scopes": {
        "type": "string",
        "description": "Space-separated allowed scopes. Defaults to `printing.print printing.documents.upload printing.printers.readonly openid profile`."
      },
      "external_description": {
        "type": "string",
        "description": "Optional short description shown on the consent screen."
      }
    }
  }
}

get_account_infoTitles 58Descriptions 88Inputs 90Annotations 0Outputs 063/100

get_account_info

Title58/100

Not provided

The title clearly communicates the tool’s action and subject. Keep it concise.

Description88/100

The description explains the capability, when to use it, and what to expect.

Inputs90/100

Input documentation gives an agent enough context to populate the arguments.

access_token

Optional access token with 'accounts' scope. If omitted, uses header-based authentication (auto-exchanged with accounts scope).

Clear enough to supply this argument.

Annotations0/100

Declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint based on the tool’s actual behavior.

Not declared

Output schema0/100

No output schema is declared. Add one for structured results so clients can interpret returned fields.

Not declared

Original tool metadata

{
  "name": "get_account_info",
  "description": "⛔ FIRST RUN ONLY: if `choose_integration_flow` has not been called in this conversation, call it FIRST and let the user pick the integration model. Do NOT prompt the user for a refresh token or store ezeep credentials in env / platform secrets.\n\nRetrieve the authenticated user's account details from the ezeep Account API. Returns user profile (name, email, roles, verification status, Azure AD / ID profile) and organization context. Requires an access token with 'accounts' scope – if using X-Client-ID/X-Refresh-Token headers, the token will be auto-exchanged with accounts scope.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "access_token": {
        "type": "string",
        "description": "Optional access token with 'accounts' scope. If omitted, uses header-based authentication (auto-exchanged with accounts scope)."
      }
    }
  }
}

Manufact

Server metadata

Discoverability

Protocol

Tools

MCP Apps

Tool documentation quality

Server metadata

Discoverability

Protocol

Tools

MCP Apps

Tool docsTool documentation quality

Title53/100

Description78/100

Inputs50/100

Annotations0/100

Output schema0/100

Title78/100

Description71/100

Inputs51/100

Annotations0/100

Output schema0/100

Title56/100

Description89/100

Inputs51/100

Annotations0/100

Output schema0/100

Title69/100

Description75/100

Inputs50/100

Annotations0/100

Output schema0/100

Title64/100

Description62/100

Inputs50/100

Annotations0/100

Output schema0/100

Title81/100

Description94/100

Inputs75/100

Annotations0/100

Output schema0/100

Title90/100

Description89/100

Inputs42/100

Annotations0/100

Output schema0/100

Title70/100

Description65/100

Inputs50/100

Annotations0/100

Output schema0/100

Title70/100

Description70/100

Inputs75/100

Annotations0/100

Output schema0/100

Title88/100

Description59/100

Inputs48/100

Annotations0/100

Output schema0/100

Title74/100

Description57/100

Inputs50/100

Annotations0/100

Output schema0/100

Title68/100

Description61/100

Inputs50/100

Annotations0/100

Output schema0/100

Title46/100

Description59/100

Inputs75/100

Annotations0/100

Output schema0/100

Title73/100

Description56/100

Tool documentation quality