@carrierllc/mcp 0.13.47 → 0.13.51
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/dist/{chunk-4XUAUQ3U.js → chunk-NPAD6AA7.js} +53 -24
- package/dist/chunk-NPAD6AA7.js.map +1 -0
- package/dist/cli.js +102 -11
- package/dist/cli.js.map +1 -1
- package/dist/index.js +69 -3
- package/dist/index.js.map +1 -1
- package/package.json +6 -3
- package/plugin/carrier/skills/storefront/SKILL.md +2 -2
- package/templates/storefront/CLERK.md +2 -0
- package/dist/chunk-4XUAUQ3U.js.map +0 -1
package/package.json
CHANGED
|
@@ -1,14 +1,17 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@carrierllc/mcp",
|
|
3
|
-
"version": "0.13.
|
|
4
|
-
"description": "Carrier MCP
|
|
3
|
+
"version": "0.13.51",
|
|
4
|
+
"description": "Carrier MCP — natural-language control of MVNO/eSIM fleets via eSIMVault OCS. Stdio mode for direct integration with Claude Desktop, Cursor, Windsurf, and MCP-compatible clients. Ships the `carrier` CLI (plugin install + white-label eSIM storefront scaffold).",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"author": "Carrier (Lifecycle Innovations Limited)",
|
|
7
7
|
"homepage": "https://mcp.carrier.llc",
|
|
8
8
|
"type": "module",
|
|
9
9
|
"carrierCompatibility": {
|
|
10
10
|
"claudeOAuthOwnerVersion": "2.1.277",
|
|
11
|
-
"claudeOAuthOwnerVersions": [
|
|
11
|
+
"claudeOAuthOwnerVersions": [
|
|
12
|
+
"2.1.277",
|
|
13
|
+
"2.1.296"
|
|
14
|
+
]
|
|
12
15
|
},
|
|
13
16
|
"main": "./dist/index.js",
|
|
14
17
|
"files": [
|
|
@@ -19,9 +19,9 @@ Works for **any developer** with Carrier MCP (`https://mcp.carrier.llc/mcp`) or
|
|
|
19
19
|
Shows which hosts are installed, logged in, and ready: Cloudflare, Vercel, Netlify, Fly. Names the one a deploy would pick.
|
|
20
20
|
- **deploy** → `carrier site deploy <dir>`
|
|
21
21
|
Picks a host automatically: one the project is already configured for, else Cloudflare (what the template is built for). Force with `--target cloudflare|vercel|netlify|fly`. Builds with the right script per host (`cf:build` for Cloudflare, `build` elsewhere), **stages runtime secrets before the code**, deploys, then **verifies the site actually serves** and repairs it once if it does not.
|
|
22
|
-
Flags: `--no-secrets`, `--no-verify`, `--clerk
|
|
22
|
+
Flags: `--no-secrets`, `--no-verify`, `--no-clerk` (skip Clerk; it is provisioned by default), `--domain`, `--autofix-agent`.
|
|
23
23
|
- **clerk** → `carrier site clerk <dir>`
|
|
24
|
-
Four tiers, best first: create via Platform API (`CLERK_PLATFORM_API_KEY`) → mint a **keyless** app with the Clerk CLI, no account needed
|
|
24
|
+
Four tiers, best first: reuse keys already in `.env.local` or the environment (a redeploy must never orphan existing buyer accounts) → create via Platform API (`CLERK_PLATFORM_API_KEY`) → mint a **keyless** app with the Clerk CLI, no account needed (**skipped on production deploys**: keyless apps are development instances) → print the dashboard steps. Writes keys to `.env.local` and sets allowed origins + redirect URLs. `--no-create` reuses only; `--production` pulls prod keys. To force a brand-new application, remove the old keys from `.env.local` first.
|
|
25
25
|
|
|
26
26
|
Secrets are staged **before** the deploy, not after. On Cloudflare they ride along in the same version via `--secrets-file`, so there is never a moment where the new code is live without them — that gap is what made a green deploy serve 500s.
|
|
27
27
|
|
|
@@ -1,5 +1,7 @@
|
|
|
1
1
|
# Clerk instance switch
|
|
2
2
|
|
|
3
|
+
> **Note on Carrier-Managed Provisioning**: `carrier site deploy` automatically provisions Clerk with the Carrier-managed default (discovered-tier: the Carrier production instance). `NEXT_PUBLIC_CLERK_INSTANCE=dev` remains the default for local development and scaffolding; the production-switch mechanism remains unchanged.
|
|
4
|
+
|
|
3
5
|
This template does not create or configure a Clerk application. Dev is the default. Production is a config switch for a later approval.
|
|
4
6
|
|
|
5
7
|
Set the switch with `NEXT_PUBLIC_CLERK_INSTANCE`.
|