portkey-admin-mcp 0.14.0 → 0.14.1
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.
- package/COMPATIBILITY.md +67 -0
- package/README.md +63 -15
- package/docs/DISTRIBUTION.md +22 -3
- package/docs/VERCEL_DEPLOYMENT.md +6 -0
- package/package.json +6 -4
package/COMPATIBILITY.md
ADDED
|
@@ -0,0 +1,67 @@
|
|
|
1
|
+
# Compatibility and deprecations
|
|
2
|
+
|
|
3
|
+
Last reviewed: 2026-10-24. Package versions, SDK versions, and negotiated MCP
|
|
4
|
+
protocol revisions are separate compatibility boundaries.
|
|
5
|
+
|
|
6
|
+
## Release lines
|
|
7
|
+
|
|
8
|
+
| Package release | MCP SDK | MCP protocol | Support and behavior |
|
|
9
|
+
| --- | --- | --- | --- |
|
|
10
|
+
| 0.14.1 | v1; dependency floor 1.32.1 | Latest supported revision: `2025-11-25` | Current published minor, 194 tools across 22 domains, Node.js 24+. Stateful HTTP sessions and optional replay stores remain active. |
|
|
11
|
+
| 0.13.0 | v1; dependency floor 1.31.0 | Latest supported revision: `2025-11-25` | Historical release, 184 tools across 20 domains. Upgrade to the latest published minor for security fixes. |
|
|
12
|
+
| Planned migration, minor release number unassigned | v2, exact version to be selected and tested | Native `2026-07-28` plus older clients on the same endpoint | Not shipped. Planned to retire HTTP session and replay stores and change configuration behavior. |
|
|
13
|
+
|
|
14
|
+
The current SDK supports `2025-11-25`, `2025-06-18`, `2025-03-26`,
|
|
15
|
+
`2024-11-05`, and `2024-10-07`. A newer client that negotiates an older
|
|
16
|
+
revision can use this server; that fallback does not mean the server natively
|
|
17
|
+
supports `2026-07-28`. The migration must verify both modern and older clients
|
|
18
|
+
over HTTP and stdio before release.
|
|
19
|
+
|
|
20
|
+
[SECURITY.md](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/SECURITY.md) owns the security-support policy: fixes ship on the
|
|
21
|
+
latest published minor line; older minor lines do not receive backports.
|
|
22
|
+
See [CHANGELOG.md](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/CHANGELOG.md) for changes in each published release.
|
|
23
|
+
|
|
24
|
+
## Configuration lifecycle
|
|
25
|
+
|
|
26
|
+
No deprecation warnings or removals for the settings below ship in 0.14.x.
|
|
27
|
+
The planned migration has no assigned package release number. Its release
|
|
28
|
+
notes must identify the first warning, ignored-setting, and removal versions
|
|
29
|
+
before operators are asked to upgrade.
|
|
30
|
+
|
|
31
|
+
| Setting or behavior | 0.14.x | Planned migration | First warning / ignored / removal release |
|
|
32
|
+
| --- | --- | --- | --- |
|
|
33
|
+
| `MCP_SESSION_MODE`, `MCP_SESSION_TIMEOUT` | Active; stateful mode is the default | Retire session storage; serve older clients without persistent sessions | Unassigned / unassigned / unassigned |
|
|
34
|
+
| `MCP_EVENT_STORE`, `MCP_EVENT_TTL_SECONDS`, `MCP_EVENT_STORE_MAX_EVENTS`, `MCP_EVENT_STORE_MAX_BYTES`, `MCP_EVENT_STORE_COMMAND_TIMEOUT_MS` | Active replay configuration | Retire replay storage and warn about obsolete settings | Unassigned / unassigned / unassigned |
|
|
35
|
+
| `MCP_EVENT_ENCRYPTION_KEY`, `MCP_REDIS_KEY_PREFIX` | Active Redis replay configuration | Retire with the replay store | Unassigned / unassigned / unassigned |
|
|
36
|
+
| HTTP GET stream, `Last-Event-ID` recovery, session identifiers | Active under the configured HTTP mode | Retire legacy sessions and replay; document the resulting recovery changes | Unassigned / unassigned / unassigned |
|
|
37
|
+
| `RATE_LIMIT_*` | Active rate-limit configuration | Retained, including shared Redis limiting | No removal planned |
|
|
38
|
+
| `RATE_LIMIT_REDIS_URL`, `MCP_REDIS_URL`, `REDIS_URL` | Rate limiter uses these URL sources in that order; replay uses the latter two | Preserve a documented Redis connection path for rate limiting when replay is retired | No removal assigned |
|
|
39
|
+
| `MCP_MAX_SESSIONS` | Bounds stateful sessions or active stateless request handlers | Retain the stateless concurrency bound | No removal planned |
|
|
40
|
+
| `MCP_TOOL_DOMAINS`, `CORS_ORIGIN` | Supported fallbacks for `PORTKEY_TOOL_DOMAINS`, `ALLOWED_ORIGINS` | No change assigned | No removal planned |
|
|
41
|
+
|
|
42
|
+
Redis rate limiting and Redis replay are separate features. Retiring the replay
|
|
43
|
+
store does not remove the need for a shared rate limiter in multi-instance or
|
|
44
|
+
serverless deployments. Do not remove working settings from a 0.14.x deployment
|
|
45
|
+
based on the migration plan.
|
|
46
|
+
|
|
47
|
+
## Migration preparation
|
|
48
|
+
|
|
49
|
+
Work starts by 2026-12-01, or earlier if the v1 SDK stops receiving a needed
|
|
50
|
+
security fix or announces end of life, a targeted client drops the older
|
|
51
|
+
handshake or fails when pinned to `2026-07-28`, or 30 days pass without a v2
|
|
52
|
+
server release carrying upgrade notes. Target completion is before 2027-01-27.
|
|
53
|
+
These are project planning dates, not announced configuration-removal dates or
|
|
54
|
+
an SDK end-of-life guarantee. [ROADMAP.md](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/ROADMAP.md) tracks the work.
|
|
55
|
+
|
|
56
|
+
Before that release, operators need a versioned upgrade guide covering:
|
|
57
|
+
|
|
58
|
+
- warning and removal behavior for every retired setting;
|
|
59
|
+
- loss of session affinity, the GET stream, and `Last-Event-ID` recovery;
|
|
60
|
+
- how to inspect Portkey state after an interrupted mutation before retrying,
|
|
61
|
+
since an automatic retry can repeat a successful write;
|
|
62
|
+
- retained Redis rate-limit configuration and concurrency bounds; and
|
|
63
|
+
- client, reverse-proxy, Vercel, and marketplace compatibility checks.
|
|
64
|
+
|
|
65
|
+
The release must update this table, the README configuration reference,
|
|
66
|
+
[architecture](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/docs/ARCHITECTURE.md), [Vercel guide](docs/VERCEL_DEPLOYMENT.md),
|
|
67
|
+
[security assurance case](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/SECURITY-ASSURANCE.md), and changelog together.
|
package/README.md
CHANGED
|
@@ -36,27 +36,52 @@
|
|
|
36
36
|
|
|
37
37
|
<h2 align="center">Contents</h2>
|
|
38
38
|
|
|
39
|
+
- [Documentation](#documentation)
|
|
39
40
|
- [Quick Start](#quick-start)
|
|
40
41
|
- [What You Can Do](#what-you-can-do)
|
|
41
42
|
- [API Key Scopes](#api-key-scopes)
|
|
42
43
|
- [HTTP Server (Experimental)](#http-server)
|
|
43
|
-
- [Architecture](
|
|
44
|
+
- [Architecture](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/docs/ARCHITECTURE.md)
|
|
44
45
|
- [Distribution and directories](./docs/DISTRIBUTION.md)
|
|
45
46
|
- [Prisma AIRS interoperability](./docs/PRISMA_AIRS_INTEROPERABILITY.md)
|
|
46
|
-
- [Verify a release](
|
|
47
|
+
- [Verify a release](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/docs/VERIFY_RELEASE.md)
|
|
47
48
|
- [Development](#development)
|
|
49
|
+
- [Roadmap](#roadmap)
|
|
48
50
|
- [Community](#community)
|
|
49
|
-
- [
|
|
50
|
-
- [
|
|
51
|
-
- [
|
|
51
|
+
- [Built With](#built-with)
|
|
52
|
+
- [Contributing](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/CONTRIBUTING.md)
|
|
53
|
+
- [Governance](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/GOVERNANCE.md)
|
|
54
|
+
- [Security assurance](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/SECURITY-ASSURANCE.md)
|
|
52
55
|
- [Full tool list — ENDPOINTS.md](./ENDPOINTS.md)
|
|
53
56
|
|
|
54
57
|
<hr>
|
|
55
58
|
|
|
59
|
+
<h2 align="center" id="documentation">Documentation</h2>
|
|
60
|
+
|
|
61
|
+
| Resource | Link |
|
|
62
|
+
| --- | --- |
|
|
63
|
+
| Tool reference | [ENDPOINTS.md](./ENDPOINTS.md) |
|
|
64
|
+
| Compatibility and deprecations | [COMPATIBILITY.md](./COMPATIBILITY.md) |
|
|
65
|
+
| Changelog | [CHANGELOG.md](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/CHANGELOG.md) |
|
|
66
|
+
| Roadmap | [ROADMAP.md](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/ROADMAP.md) |
|
|
67
|
+
| Architecture | [Architecture](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/docs/ARCHITECTURE.md) |
|
|
68
|
+
| Deployment | [HTTP configuration](#http-server), [Vercel guide](./docs/VERCEL_DEPLOYMENT.md) |
|
|
69
|
+
| Distribution | [Directories and release records](./docs/DISTRIBUTION.md), [verify a release](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/docs/VERIFY_RELEASE.md) |
|
|
70
|
+
| Prisma AIRS | [Interoperability guide](./docs/PRISMA_AIRS_INTEROPERABILITY.md) |
|
|
71
|
+
| Contributing and governance | [CONTRIBUTING.md](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/CONTRIBUTING.md), [GOVERNANCE.md](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/GOVERNANCE.md), [Code of Conduct](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/CODE_OF_CONDUCT.md) |
|
|
72
|
+
| Security | [Reporting policy](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/SECURITY.md), [assurance case](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/SECURITY-ASSURANCE.md) |
|
|
73
|
+
|
|
74
|
+
<hr>
|
|
75
|
+
|
|
56
76
|
<h2 align="center" id="quick-start">Quick Start</h2>
|
|
57
77
|
|
|
58
78
|
You need a **Portkey API key** with appropriate scopes. Get one from your [Portkey dashboard](https://app.portkey.ai/) under API Keys.
|
|
59
79
|
|
|
80
|
+
Version 0.14.0 uses MCP SDK v1 and supports protocol revisions through
|
|
81
|
+
`2025-11-25`. Session and replay settings remain active. See
|
|
82
|
+
[compatibility and deprecations](./COMPATIBILITY.md) before upgrading; the
|
|
83
|
+
planned MCP v2 migration has no assigned release number or removal date.
|
|
84
|
+
|
|
60
85
|
### Claude Code
|
|
61
86
|
|
|
62
87
|
```bash
|
|
@@ -317,10 +342,14 @@ docker run \
|
|
|
317
342
|
-e MCP_PORT=3000 \
|
|
318
343
|
-e MCP_AUTH_MODE=bearer \
|
|
319
344
|
-e MCP_AUTH_TOKEN=your_secret \
|
|
345
|
+
-e RATE_LIMIT_SINGLE_PROCESS=true \
|
|
320
346
|
-p 3000:3000 \
|
|
321
347
|
portkey-admin-mcp
|
|
322
348
|
```
|
|
323
349
|
|
|
350
|
+
This example runs one long-lived container with in-memory rate limiting. Use
|
|
351
|
+
`RATE_LIMIT_STORE=redis` and a TLS Redis URL for multiple instances.
|
|
352
|
+
|
|
324
353
|
</details>
|
|
325
354
|
|
|
326
355
|
### Health Endpoints
|
|
@@ -357,16 +386,33 @@ The required CI and release gates measure every TypeScript source file and fail
|
|
|
357
386
|
below 80% line coverage. The CI and Coverage workflow reports show the current
|
|
358
387
|
line, branch, and function coverage.
|
|
359
388
|
|
|
389
|
+
The [CI workflow](https://github.com/CodesWhat/portkey-admin-mcp/actions/workflows/ci.yml)
|
|
390
|
+
also runs the standalone Qlty CLI and publishes `quality-reports` artifacts for
|
|
391
|
+
each analyzed commit, including lint/security results, duplication, complexity,
|
|
392
|
+
and metrics. The existing Qlty maintainability and coverage badges remain
|
|
393
|
+
Cloud-generated; local analysis does not update those badges. Coverage uploads
|
|
394
|
+
and Cloud analysis still consume Qlty analysis minutes.
|
|
395
|
+
|
|
360
396
|
`npm run dev:http` now requires `MCP_AUTH_MODE=bearer` or `MCP_AUTH_MODE=clerk` by default. For deliberate local-only unauthenticated testing, set `MCP_ALLOW_UNAUTHENTICATED_HTTP=true`.
|
|
361
397
|
|
|
362
398
|
Contributions use pull requests and the checks documented in
|
|
363
|
-
[`CONTRIBUTING.md`](CONTRIBUTING.md). Project decisions and maintainer roles are
|
|
364
|
-
documented in [`GOVERNANCE.md`](GOVERNANCE.md). Report vulnerabilities through
|
|
365
|
-
[`SECURITY.md`](SECURITY.md), and see [`SECURITY-ASSURANCE.md`](SECURITY-ASSURANCE.md)
|
|
399
|
+
[`CONTRIBUTING.md`](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/CONTRIBUTING.md). Project decisions and maintainer roles are
|
|
400
|
+
documented in [`GOVERNANCE.md`](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/GOVERNANCE.md). Report vulnerabilities through
|
|
401
|
+
[`SECURITY.md`](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/SECURITY.md), and see [`SECURITY-ASSURANCE.md`](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/SECURITY-ASSURANCE.md)
|
|
366
402
|
for the public threat model and assurance case.
|
|
367
403
|
|
|
368
404
|
<hr>
|
|
369
405
|
|
|
406
|
+
<h2 align="center" id="roadmap">Roadmap</h2>
|
|
407
|
+
|
|
408
|
+
Release 0.14.0 adds access policies, egress allowlists, and security maintenance.
|
|
409
|
+
The [roadmap](https://github.com/CodesWhat/portkey-admin-mcp/blob/main/ROADMAP.md) separates completed work from upstream contract and
|
|
410
|
+
tenant-verification gates. The planned MCP v2 migration keeps older clients on
|
|
411
|
+
the same endpoint; its package version and configuration-removal releases are
|
|
412
|
+
still unassigned. See [compatibility and deprecations](./COMPATIBILITY.md).
|
|
413
|
+
|
|
414
|
+
<hr>
|
|
415
|
+
|
|
370
416
|
<h2 align="center" id="community">Community</h2>
|
|
371
417
|
|
|
372
418
|
Questions and bug reports belong in [Issues](https://github.com/CodesWhat/portkey-admin-mcp/issues); broader discussion, ideas, and help using the server belong in [Discussions](https://github.com/CodesWhat/portkey-admin-mcp/discussions).
|
|
@@ -379,7 +425,7 @@ tool catalog in this repository as authoritative when a third-party index lags.
|
|
|
379
425
|
|
|
380
426
|
<div align="center">
|
|
381
427
|
|
|
382
|
-
|
|
428
|
+
<h2 align="center" id="built-with">Built With</h2>
|
|
383
429
|
|
|
384
430
|
[](https://www.typescriptlang.org/)
|
|
385
431
|
[](https://github.com/modelcontextprotocol/typescript-sdk)
|
|
@@ -392,6 +438,14 @@ tool catalog in this repository as authoritative when a third-party index lags.
|
|
|
392
438
|
[](https://www.conventionalcommits.org/)
|
|
393
439
|
[](https://keepachangelog.com/)
|
|
394
440
|
|
|
441
|
+
Marketplace listings on [LobeHub](https://lobehub.com/mcp/codeswhat-portkey-admin-mcp) and [Glama](https://glama.ai/mcp/servers/CodesWhat/portkey-admin-mcp):
|
|
442
|
+
|
|
443
|
+
[](https://lobehub.com/mcp/codeswhat-portkey-admin-mcp)
|
|
444
|
+
|
|
445
|
+
<a href="https://glama.ai/mcp/servers/CodesWhat/portkey-admin-mcp"><img src="https://glama.ai/mcp/servers/CodesWhat/portkey-admin-mcp/badges/card.svg" alt="portkey-admin-mcp MCP server"></a>
|
|
446
|
+
|
|
447
|
+
---
|
|
448
|
+
|
|
395
449
|
**[MIT License](LICENSE)** · Inspired by [r-huijts/portkey-admin-mcp-server](https://github.com/r-huijts/portkey-admin-mcp-server)
|
|
396
450
|
|
|
397
451
|
<a href="https://github.com/CodesWhat">
|
|
@@ -402,12 +456,6 @@ tool catalog in this repository as authoritative when a third-party index lags.
|
|
|
402
456
|
</picture>
|
|
403
457
|
</a>
|
|
404
458
|
|
|
405
|
-
Marketplace listings on [LobeHub](https://lobehub.com/mcp/codeswhat-portkey-admin-mcp) and [Glama](https://glama.ai/mcp/servers/CodesWhat/portkey-admin-mcp):
|
|
406
|
-
|
|
407
|
-
[](https://lobehub.com/mcp/codeswhat-portkey-admin-mcp)
|
|
408
|
-
|
|
409
|
-
<a href="https://glama.ai/mcp/servers/CodesWhat/portkey-admin-mcp"><img src="https://glama.ai/mcp/servers/CodesWhat/portkey-admin-mcp/badges/card.svg" alt="portkey-admin-mcp MCP server"></a>
|
|
410
|
-
|
|
411
459
|
<a href="#portkey-admin-mcp-server">Back to top</a>
|
|
412
460
|
|
|
413
461
|
</div>
|
package/docs/DISTRIBUTION.md
CHANGED
|
@@ -16,7 +16,7 @@ legacy repository owner, so they should not be used to validate the runtime.
|
|
|
16
16
|
| [npm](https://www.npmjs.com/package/portkey-admin-mcp) | Canonical package distribution | Automated from a protected release tag using `package.json` |
|
|
17
17
|
| [Official MCP Registry](https://registry.modelcontextprotocol.io/v0/servers?search=io.github.CodesWhat/portkey-admin-mcp) | Canonical MCP metadata under `io.github.CodesWhat/portkey-admin-mcp` | Automated after npm publication using `server.json` |
|
|
18
18
|
| [LobeHub](https://lobehub.com/mcp/codeswhat-portkey-admin-mcp) | Claimed marketplace listing | Run `npm run update:lobehub` after release; `lhm.plugin.json` is owner-declared metadata |
|
|
19
|
-
| [Glama](https://glama.ai/mcp/servers/CodesWhat/portkey-admin-mcp) | Claimed directory and quality listing
|
|
19
|
+
| [Glama](https://glama.ai/mcp/servers/CodesWhat/portkey-admin-mcp) | Claimed directory and quality listing; the 2026-10-16 post-release build serves package 0.14.0 with 194 tools | Indexes GitHub; after each release, use **Repository > Sync Server**, then **Dockerfile > Build & Release**, and verify the version and tool count it shows. The generated description and FAQ text are Glama's and refresh on their own schedule |
|
|
20
20
|
| [Awesome MCP Servers](https://github.com/punkpeye/awesome-mcp-servers/pull/13074) | Community list entry; the CodesWhat correction (PR #13074) merged on 2026-09-13 | Update the entry through a new PR when the repository owner, Glama badge, or released catalog count changes |
|
|
21
21
|
|
|
22
22
|
The canonical description for owner-controlled records is:
|
|
@@ -28,11 +28,30 @@ Counts belong only in generated or release-specific records. `README.md`,
|
|
|
28
28
|
`ENDPOINTS.md`, and `lhm.plugin.json` are regenerated or verified from the
|
|
29
29
|
runtime catalog before release.
|
|
30
30
|
|
|
31
|
+
### 0.14.0 publication checks, 2026-10-16
|
|
32
|
+
|
|
33
|
+
- GitHub [v0.14.0](https://github.com/CodesWhat/portkey-admin-mcp/releases/tag/v0.14.0),
|
|
34
|
+
npm, and the official MCP Registry report 0.14.0. The release workflow passed.
|
|
35
|
+
- The authenticated LobeHub owner CLI reports `codeswhat-portkey-admin-mcp`
|
|
36
|
+
published at 0.14.0 across 15 locales, with the English summary updated to
|
|
37
|
+
194 tools. Its public page still showed cached 0.13.0 during the post-publish
|
|
38
|
+
check; owner publication and public-page cache refresh are separate states.
|
|
39
|
+
- Glama synced release commit
|
|
40
|
+
[`ccaaaf5593d6ab923a6538a15b018845c91560b0`](https://github.com/CodesWhat/portkey-admin-mcp/commit/ccaaaf5593d6ab923a6538a15b018845c91560b0)
|
|
41
|
+
and completed a successful build. Its server version is 0.14.0 and indexed
|
|
42
|
+
inventory is 194 tools. Glama's separate hosted release number is 1.0.8.
|
|
43
|
+
Before that sync, the same day's check showed 0.13.0 and 184 tools; generated
|
|
44
|
+
description/FAQ text still said 150/151, and the public inventory API returned
|
|
45
|
+
401. Those observations describe the earlier scan, not the released server.
|
|
46
|
+
- Docker submission [#5026](https://github.com/docker/mcp-registry/pull/5026)
|
|
47
|
+
was refreshed to that release commit with successful validation and
|
|
48
|
+
194-tool discovery. Upstream maintainer review remains outstanding.
|
|
49
|
+
|
|
31
50
|
## Observed downstream listings
|
|
32
51
|
|
|
33
|
-
| Surface |
|
|
52
|
+
| Surface | Last verified state | Maintenance decision |
|
|
34
53
|
|---|---|---|
|
|
35
|
-
| [LobeHub legacy listing](https://lobehub.com/mcp/scttbnsn-portkey-admin-mcp) | Unpublished on 2026-09-08.
|
|
54
|
+
| [LobeHub legacy listing](https://lobehub.com/mcp/scttbnsn-portkey-admin-mcp) | Unpublished on 2026-09-08. The 2026-10-16 pre-release owner check still showed it unpublished at 0.3.5 while the canonical listing was published at 0.13.0; the canonical listing advanced to 0.14.0 in the post-release check above | Nothing to do; only the canonical listing is published |
|
|
36
55
|
| [PulseMCP](https://www.pulsemcp.com/servers) | A legacy record uses `io.github.s-b-e-n-s-o-n/portkey-admin-mcp` and an old count; listing changes are paused | Recheck when its submission and correction flow reopens; prefer MCP Registry ingestion |
|
|
37
56
|
| [mcp.so](https://mcp.so/servers/portkey-admin-mcp) | Live but stale under the previous owner, with a visible claim control and conflicting counts | Claim and refresh only through its owner workflow; do not automate an undocumented interface |
|
|
38
57
|
| [mcpservers.org](https://mcpservers.org/servers/s-b-e-n-s-o-n/portkey-admin-mcp) | Scrapes the current README but retains the previous owner slug and a 151-tool headline | Use its **Request update** flow, then treat the result as downstream indexing rather than a release gate |
|
|
@@ -4,6 +4,12 @@
|
|
|
4
4
|
|
|
5
5
|
This guide describes how to self-deploy this MCP server on Vercel.
|
|
6
6
|
|
|
7
|
+
These session and Redis replay settings remain active in 0.14.0. The planned
|
|
8
|
+
MCP migration has no assigned warning or removal release. Keep this deployment
|
|
9
|
+
configuration until a versioned upgrade guide replaces it; Redis rate limiting
|
|
10
|
+
remains a separate requirement. See [compatibility and
|
|
11
|
+
deprecations](../COMPATIBILITY.md).
|
|
12
|
+
|
|
7
13
|
## Recommended Architecture
|
|
8
14
|
|
|
9
15
|
- Runtime: Vercel Node.js Function (`api/index.ts`)
|
package/package.json
CHANGED
|
@@ -9,6 +9,7 @@
|
|
|
9
9
|
"typecheck": "tsc --noEmit",
|
|
10
10
|
"typecheck:tests": "tsc --project tsconfig.tests.json --noEmit",
|
|
11
11
|
"lint": "biome lint .",
|
|
12
|
+
"quality": "qlty check --all --no-fix --no-progress --fail-level fmt --no-upgrade-check",
|
|
12
13
|
"format": "biome format --write .",
|
|
13
14
|
"check": "biome check --write .",
|
|
14
15
|
"test": "tsx --test tests/config.test.ts tests/security-worker-layout.test.ts tests/security-edge-runtime.test.ts tests/contract.test.ts tests/contract-extended.test.ts tests/unit.test.ts tests/services.test.ts tests/base-services.test.ts tests/fetch.test.ts tests/http-server.test.ts tests/http-edge-runtime.test.ts tests/http-edge-runtime-final.test.ts tests/tools-observability.test.ts tests/tools-catalog.test.ts tests/tools-prompts-configs.test.ts tests/tools-remaining.test.ts tests/tools-edge-workflows.test.ts tests/tools-platform.test.ts tests/tools-keys.test.ts tests/tools-users.test.ts tests/tools-analytics.test.ts tests/current-api.test.ts tests/tools-governance.test.ts tests/release-readiness.test.ts tests/lobehub-generator.test.ts tests/auth-clerk.test.ts tests/lib-event-store.test.ts tests/lib-session-mcp.test.ts tests/smoke-outcomes.test.ts tests/request-path.test.ts",
|
|
@@ -27,11 +28,11 @@
|
|
|
27
28
|
"verify:readme-tools": "node scripts/verify-readme-tools.mjs",
|
|
28
29
|
"verify:generated": "node scripts/verify-generated.mjs",
|
|
29
30
|
"knip": "knip",
|
|
30
|
-
"ci": "npm run lint && npm run knip && npm run typecheck && npm run typecheck:tests && npm run test:coverage && npm run build && npm run verify:tool-quality && npm run test:e2e && npm run verify:readme-tools && npm run verify:generated",
|
|
31
|
+
"ci": "npm run quality && npm run lint && npm run knip && npm run typecheck && npm run typecheck:tests && npm run test:coverage && npm run build && npm run verify:tool-quality && npm run test:e2e && npm run verify:readme-tools && npm run verify:generated",
|
|
31
32
|
"start:http": "node build/server.js",
|
|
32
33
|
"generate:lobehub-tools": "npm run build && node scripts/generate-lobehub-tools.mjs && biome format --write lhm.plugin.json",
|
|
33
34
|
"generate:endpoints": "node scripts/generate-endpoints.mjs",
|
|
34
|
-
"update:lobehub": "npm run generate:lobehub-tools && npx -y @lobehub/market-cli plugin update --dir \"$PWD\"",
|
|
35
|
+
"update:lobehub": "npm run generate:lobehub-tools && npx -y @lobehub/market-cli@0.0.41 plugin update --dir \"$PWD\"",
|
|
35
36
|
"publish:lobehub": "npm run update:lobehub",
|
|
36
37
|
"prepare": "[ -n \"$CI\" ] || [ -f /.dockerenv ] || [ ! -d .git ] || lefthook install",
|
|
37
38
|
"prepublishOnly": "npm run ci"
|
|
@@ -39,10 +40,11 @@
|
|
|
39
40
|
"engines": {
|
|
40
41
|
"node": ">=24"
|
|
41
42
|
},
|
|
42
|
-
"packageManager": "npm@12.2.
|
|
43
|
+
"packageManager": "npm@12.2.1",
|
|
43
44
|
"files": [
|
|
44
45
|
"build",
|
|
45
46
|
"ENDPOINTS.md",
|
|
47
|
+
"COMPATIBILITY.md",
|
|
46
48
|
"docs/DISTRIBUTION.md",
|
|
47
49
|
"docs/PRISMA_AIRS_INTEROPERABILITY.md",
|
|
48
50
|
"docs/VERCEL_DEPLOYMENT.md"
|
|
@@ -59,7 +61,7 @@
|
|
|
59
61
|
},
|
|
60
62
|
"name": "portkey-admin-mcp",
|
|
61
63
|
"mcpName": "io.github.CodesWhat/portkey-admin-mcp",
|
|
62
|
-
"version": "0.14.
|
|
64
|
+
"version": "0.14.1",
|
|
63
65
|
"main": "build/index.js",
|
|
64
66
|
"keywords": [
|
|
65
67
|
"mcp",
|