edgegate-mcp 0.1.1

package/package.json

@@ -0,0 +1,49 @@
+{
+  "name": "edgegate-mcp",
+  "version": "0.1.1",
+  "description": "MCP server for EdgeGate — set up edge-AI regression gates from Claude Code, Cursor, or Claude Desktop.",
+  "license": "MIT",
+  "type": "module",
+  "engines": {
+    "node": ">=20"
+  },
+  "bin": {
+    "edgegate-mcp": "./bin/edgegate-mcp",
+    "edgegate-mcp-install": "./bin/edgegate-mcp-install"
+  },
+  "main": "./dist/server.js",
+  "files": [
+    "dist/",
+    "bin/",
+    "skills/",
+    "plugin.json",
+    "README.md",
+    "LICENSE"
+  ],
+  "scripts": {
+    "build": "tsc",
+    "dev": "tsx src/server.ts",
+    "test": "vitest run",
+    "test:watch": "vitest",
+    "lint": "eslint 'src/**/*.ts'",
+    "format": "prettier --write 'src/**/*.ts'",
+    "prepublishOnly": "npm run build && npm test && npm run lint"
+  },
+  "dependencies": {
+    "@modelcontextprotocol/sdk": "^1.29.0",
+    "undici": "^6.0.0",
+    "zod": "^3.23.0",
+    "zod-to-json-schema": "^3.23.0"
+  },
+  "devDependencies": {
+    "@types/node": "^20.0.0",
+    "@typescript-eslint/eslint-plugin": "^7.0.0",
+    "@typescript-eslint/parser": "^7.0.0",
+    "eslint": "^8.57.0",
+    "msw": "^2.3.0",
+    "prettier": "^3.0.0",
+    "tsx": "^4.7.0",
+    "typescript": "^5.4.0",
+    "vitest": "^1.6.0"
+  }
+}

package/plugin.json

@@ -0,0 +1,26 @@
+{
+  "name": "edgegate",
+  "version": "0.1.0",
+  "description": "Edge-AI regression gates from Claude Code — set up CI, run benchmarks, and fetch audit PDFs from any prompt.",
+  "author": "Frozo / EdgeGate",
+  "homepage": "https://edgegate.frozo.ai",
+  "repository": "https://github.com/frozo-ai/edgegate-mcp",
+  "license": "MIT",
+  "mcpServers": {
+    "edgegate": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["-y", "edgegate-mcp"],
+      "env": {
+        "EDGEGATE_API_KEY": "${EDGEGATE_API_KEY}",
+        "EDGEGATE_API_URL": "${EDGEGATE_API_URL:-https://edgegateapi.frozo.ai}"
+      }
+    }
+  },
+  "skills": [
+    "skills/edgegate-init.md",
+    "skills/edgegate-gate.md",
+    "skills/edgegate-status.md",
+    "skills/edgegate-audit.md"
+  ]
+}

package/skills/edgegate-audit.md

@@ -0,0 +1,17 @@
+---
+name: edgegate-audit
+description: Fetch the signed audit PDF for a completed EdgeGate run. Use for compliance records or to attach to a release.
+---
+
+# /edgegate-audit
+
+The user needs the audit PDF for a specific run (for SOC2, ISO, internal compliance, or to attach to a release).
+
+1. If they gave you a `run_id`, call `edgegate_get_audit_report` directly.
+2. If not, call `edgegate_get_report` and ask which run they want.
+3. Return the signed URL. Remind the user that:
+   - URLs are time-limited (~1h).
+   - The PDF contains the signed evidence bundle hash, device fingerprints, and gate decisions.
+   - Save it locally if they need a durable record.
+
+If the run is still in-flight or the report hasn't generated yet, you'll get a 404. Tell the user to wait 1-2 minutes and retry.

package/skills/edgegate-gate.md

@@ -0,0 +1,15 @@
+---
+name: edgegate-gate
+description: Trigger an EdgeGate run on an existing pipeline. Use when the user says "run the gates" or "test this PR on devices".
+---
+
+# /edgegate-gate
+
+The user wants to trigger an EdgeGate run.
+
+1. If you don't know the `workspace_id`, call `edgegate_setup_workspace` first.
+2. If you don't know the `pipeline_id`, ask the user. (In v1.0 there is no `list_pipelines` tool; tell them to find it in the dashboard at `https://edgegate.frozo.ai/workspace/{id}/pipelines`.)
+3. Call `edgegate_run_gate` with the workspace_id + pipeline_id. Optionally accept a `model_artifact_id` override.
+4. Tell the user the run_id and that they can check status with `/edgegate-status`.
+
+If you get a 409, that means another run is already in flight (workspace_concurrency=1). Tell the user to wait for it to finish, or check status.

package/skills/edgegate-init.md

@@ -0,0 +1,35 @@
+---
+name: edgegate-init
+description: Walk a new EdgeGate user from zero to a running CI gate. Wire the workspace, generate a pipeline from a model, and (optionally) set up the GitHub Action.
+---
+
+# /edgegate-init
+
+You are an assistant onboarding the user to EdgeGate. EdgeGate is a SaaS that runs AI model regression tests on real Snapdragon devices and produces signed evidence bundles to gate CI/CD pipelines.
+
+Goal of this skill: take the user from "I have a model file" to "every PR is automatically gated by EdgeGate" in under 5 minutes.
+
+## Steps
+
+1. **Confirm workspace.** Call `edgegate_setup_workspace` with no args. Present the list. Ask the user which one to use; if they say "the first one", pick `result[0].id`. Confirm before continuing.
+
+2. **Define the pipeline.** Ask the user:
+   - "Which model file do you want to gate? (path or artifact_id)"
+   - "Which Snapdragon devices? (default: Samsung Galaxy S24, Galaxy S23)"
+   - "Which gates? Common defaults: inference_time_ms ≤ 10, peak_memory_mb ≤ 150"
+
+   If they hand you a file path (e.g. `./model.onnx`), tell them they need to upload it via the dashboard first to get an artifact_id (the MCP tool does not handle uploads in v1.0). Link: `https://edgegate.frozo.ai/workspace/{workspace_id}/models`.
+
+   If they hand you an artifact_id, proceed to `edgegate_create_pipeline`.
+
+3. **Trigger the first run.** Call `edgegate_run_gate` with the workspace_id + new pipeline_id. Tell the user the run_id. Note that runs take 3-5 min per device.
+
+4. **Wire CI.** Ask "Should I set up the GitHub Action so every PR runs this gate?" — if yes, call `edgegate_setup_github_action`. Present the YAML and `gh` commands; tell the user to commit the YAML and run the `gh` commands.
+
+5. **Confirm.** Tell the user what's now set up: workspace `<name>`, pipeline `<name>`, run `<id>` in flight, and (if applicable) GitHub Action wired.
+
+## Failure modes
+
+- **No workspaces.** The API key may have been revoked. Direct the user to `https://edgegate.frozo.ai/workspace/<id>/settings#api-keys` to generate a fresh key.
+- **Workspace is on Free tier.** Pipelines per month are capped. Direct them to `/pricing`.
+- **Cell count > 25.** Reduce models × devices.

package/skills/edgegate-status.md

@@ -0,0 +1,14 @@
+---
+name: edgegate-status
+description: Check on an in-flight or recent EdgeGate run. Shows status, per-device metrics, gate pass/fail.
+---
+
+# /edgegate-status
+
+The user wants to know how a run is doing.
+
+1. If they gave you a `run_id`, call `edgegate_check_status` directly.
+2. If they did NOT give you a run_id, call `edgegate_get_report` to show the last 10 runs, then ask which one they meant.
+3. Render the result. If the run is FAILED, lead with the violating gate and the actual value — don't bury it.
+
+For PASSED runs, briefly summarize the metrics so the user has the numbers handy for a PR comment.