From f28de46103bac7a860a645c4f1f9129c3377f390 Mon Sep 17 00:00:00 2001
From: Cursor Agent <cursoragent@cursor.com>
Date: Sun, 5 Apr 2026 22:26:35 +0000
Subject: [PATCH 1/2] docs: add Cursor Cloud specific instructions to AGENTS.md

---
 AGENTS.md | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)

diff --git a/AGENTS.md b/AGENTS.md
index b6a7ca3..fd56852 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -202,3 +202,31 @@ Add to your IDE's MCP config:
 - Pino for structured logging (no `console.log` in non-CLI code)
 - Zod for runtime validation
 - Async/await preferred, custom error types at boundaries
+
+## Cursor Cloud specific instructions
+
+### Services overview
+
+MCPflare has three components: the core MCP server (`src/`), a VSCode extension (`vscode-extension/`), and a docs site (`docs-site/`). The core server is the primary development target. All build/dev/test commands are documented in the "Build and Development Commands" section above.
+
+### Running the MCP server
+
+- `npm run dev` starts the MCP server over stdio (via `tsx`). It reads IDE MCP config from `~/.cursor/mcp.jsonc` in this environment. The process blocks on stdin; it exits cleanly on EOF/SIGTERM.
+- `npm run cli` starts the interactive CLI. Pipe commands via stdin for non-interactive use: `echo -e "status\nexit" | npx tsx src/cli/index.ts`.
+
+### Testing notes
+
+- `npm test` runs all Vitest suites (unit, integration, security, evals). Expect 490+ passing tests.
+- The `tests/evals/github-mcp-isolation.test.ts` test requires a `GITHUB_PERSONAL_ACCESS_TOKEN` in `.env` **and** a GitHub MCP entry in the IDE config; it will fail in CI/cloud environments without these. This is expected.
+- Security tests (`tests/security/mcp-isolation.test.ts`, `tests/security/network-allowlist.test.ts`) spawn real Wrangler/workerd processes and take ~50-75s each. They are the slowest tests in the suite.
+- Use `npm run test:unit` for fast iteration (~1s); use `npm run test:security` only when changing isolation/network code.
+
+### Lint
+
+- Pre-commit hook runs `npm run check` (Biome lint + format). Pre-push hook additionally runs full `npm test`.
+- In cloud environments, run `npm run check` before committing to match CI expectations.
+
+### VSCode extension
+
+- Has its own `package.json` and `package-lock.json` at `vscode-extension/`. Install deps separately with `cd vscode-extension && npm install`.
+- Extension tests run as part of the main `npm test` suite (vitest picks up `vscode-extension/tests/`).

From e625a5eeba4d156963422944ededc1da73258b60 Mon Sep 17 00:00:00 2001
From: Cursor Agent <cursoragent@cursor.com>
Date: Sun, 5 Apr 2026 22:29:50 +0000
Subject: [PATCH 2/2] chore: sync vscode-extension lockfile version to 1.3.7

---
 vscode-extension/package-lock.json | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/vscode-extension/package-lock.json b/vscode-extension/package-lock.json
index d609c45..a46ae75 100644
--- a/vscode-extension/package-lock.json
+++ b/vscode-extension/package-lock.json
@@ -1,12 +1,12 @@
 {
   "name": "mcpflare",
-  "version": "1.2.10",
+  "version": "1.3.7",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "mcpflare",
-      "version": "1.2.10",
+      "version": "1.3.7",
       "license": "MIT",
       "dependencies": {
         "@modelcontextprotocol/sdk": "^1.25.2",