@fruggr/zendesk-mcp-server 3.0.2 → 3.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (9) hide show
  1. package/README.md +4 -3
  2. package/dist/THIRD-PARTY-NOTICES.md +5272 -0
  3. package/dist/http-CmtU-oNu.js +36570 -0
  4. package/dist/index.js +102832 -1498
  5. package/dist/sbom.cdx.json +2152 -0
  6. package/dist/token-persistence-BeetFqPF.js +147 -0
  7. package/dist/token-store-CLtwRaxI.js +972 -0
  8. package/package.json +18 -35
  9. package/dist/http-BXXDmcaZ.js +0 -1383
package/README.md CHANGED
@@ -213,9 +213,10 @@ Something not working? See [Troubleshooting](docs/troubleshooting.md).
213
213
  You can also deploy a private remote MCP server for **one** Zendesk account.
214
214
  It is its own OAuth authorization server: web clients such as claude.ai and
215
215
  ChatGPT add it by URL and register themselves, each user signs in to Zendesk
216
- through it, and no shared admin key or per-client Zendesk setup is involved. Its
217
- packages install on top of the server, so stdio users never download them. The
218
- full guide covers that install, the one redirect URL to add to your Zendesk OAuth client, the
216
+ through it, and no shared admin key or per-client Zendesk setup is involved. Each
217
+ release also ships a hardened, distroless container image for it
218
+ (`ghcr.io/fruggr/zendesk-mcp-server`), signed and attested. The full guide covers
219
+ the image, the one redirect URL to add to your Zendesk OAuth client, the
219
220
  master secret and grant store, `--public-url` behind a reverse proxy, trusted
220
221
  clients, MCP client wiring, CORS and what stays the operator's job:
221
222
  **[docs/http-deployment.md](docs/http-deployment.md)**.