get_license_status Leave feedback

get_license_status reports how this server is licensed and, under metered licensing, how much has been consumed. Worth calling before a large merge: evaluation mode trims the result to three pages. Example prompt: “Is the merger server licensed?”

Tool description (as the AI agent sees it):

Returns how this MCP server is licensed, and — under metered licensing — how much has been consumed. Call this when the user asks about licensing, evaluation limitations, metered usage, remaining credit, or which product engine version is running. Returns a JSON object with mode (“evaluation”, “licensed” or “metered”), licensed (true for both licensed and metered), consumption (null unless metered; otherwise quantity and credit, or error if the reading failed), and server / engine name and version. Takes no arguments and never modifies anything.

None.

{
  "name": "get_license_status",
  "arguments": {}
}

A JSON object describing the active licensing mode.

Evaluation mode — nothing configured:

{
  "mode": "evaluation",
  "licensed": false,
  "server": { "name": "GroupDocs.Merger.Mcp", "version": "26.9.0" },
  "engine": { "name": "GroupDocs.Merger", "version": "26.4.0" },
  "note": "No license configured — output may carry evaluation limitations. ..."
}

The full note text names the variables to set: GROUPDOCS_METERED_PUBLIC_KEY and GROUPDOCS_METERED_PRIVATE_KEY for metered licensing, or GROUPDOCS_LICENSE_PATH for a license file.

Metered mode — both keys accepted:

{
  "mode": "metered",
  "licensed": true,
  "source": "metered-keys",
  "consumption": { "quantity": 1234.5678, "credit": 9642.0 },
  "server": { "name": "GroupDocs.Merger.Mcp", "version": "26.9.0" },
  "engine": { "name": "GroupDocs.Merger", "version": "26.4.0" }
}

"mode": "evaluation" trims your output: the result is cut to the first three pages and every page carries a trial badge. A merge that looks successful can be missing most of its content.

A rejected key pair does not fail silently: the mode reverts to evaluation and note carries the reason. See Licensing.

• “Is the merger server licensed?”
• “How much metered credit have I used?”
• “Which GroupDocs.Merger engine version is running?”