@laylzj777/my-apple-apple-eventkit 1.1.0

package/scripts/event-Info.plist

@@ -0,0 +1,29 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+<dict>
+	<key>CFBundleIdentifier</key>
+	<string>io.github.lay777.calendar-event-cli</string>
+	<!-- TCC prompt display name ("... would like to access Calendar"). Overridable at build time via APP_EVENT_DISPLAY_NAME, see build-event.mjs. -->
+	<key>CFBundleName</key>
+	<string>Apple EventKit MCP</string>
+	<key>CFBundleDisplayName</key>
+	<string>Apple EventKit MCP</string>
+	<key>CFBundleInfoDictionaryVersion</key>
+	<string>6.0</string>
+	<key>CFBundleVersion</key>
+	<string>1</string>
+	<key>NSRemindersUsageDescription</key>
+	<string>This tool needs access to Reminders so it can query and manage your reminders.</string>
+	<key>NSRemindersFullAccessUsageDescription</key>
+	<string>This tool needs access to Reminders so it can query and manage your reminders.</string>
+	<key>NSRemindersWriteOnlyAccessUsageDescription</key>
+	<string>This tool needs access to Reminders so it can create reminders for you.</string>
+	<key>NSCalendarsUsageDescription</key>
+	<string>This tool needs access to Calendar so it can query and manage your events.</string>
+	<key>NSCalendarsFullAccessUsageDescription</key>
+	<string>This tool needs access to Calendar so it can query and manage your events.</string>
+	<key>NSCalendarsWriteOnlyAccessUsageDescription</key>
+	<string>This tool needs access to Calendar so it can create events for you.</string>
+</dict>
+</plist>

package/scripts/event.entitlements

@@ -0,0 +1,10 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+<dict>
+	<key>com.apple.security.personal-information.calendars</key>
+	<true/>
+	<key>com.apple.security.personal-information.reminders</key>
+	<true/>
+</dict>
+</plist>

package/scripts/postinstall.mjs

@@ -0,0 +1,91 @@
+#!/usr/bin/env node
+
+/**
+ * Postinstall script for mcp-server-apple-events
+ *
+ * When the package is installed via npm, the pre-built `event` binary is
+ * included in the package and this script exits immediately. No Xcode required.
+ *
+ * When the repository is cloned locally (no pre-built binary), this script
+ * attempts to build the vendored `event` CLI from source. It gracefully skips
+ * on non-macOS platforms or if Swift is not available.
+ */
+
+import { execFile } from 'node:child_process';
+import { promises as fs } from 'node:fs';
+import path from 'node:path';
+import { fileURLToPath } from 'node:url';
+import { promisify } from 'node:util';
+
+const execFileAsync = promisify(execFile);
+
+const __dirname = path.dirname(fileURLToPath(import.meta.url));
+const projectRoot = path.resolve(__dirname, '..');
+
+async function main() {
+  if (process.platform !== 'darwin') {
+    console.log('Skipping `event` CLI build on non-macOS platform');
+    process.exit(0);
+  }
+
+  // If the pre-built binaries are already present (npm install from published
+  // package), skip the source build entirely — the npm tarball does not
+  // include the vendor/event submodule sources, so there is nothing to
+  // build against anyway. Both `event` and the `event-disclaim` TCC shim
+  // must exist; a clone with a stale pre-shim build rebuilds to pick up the
+  // shim (issue #93).
+  const binPath = path.join(projectRoot, 'bin', 'event');
+  const disclaimPath = path.join(projectRoot, 'bin', 'event-disclaim');
+  try {
+    await fs.access(binPath, fs.constants.X_OK);
+    await fs.access(disclaimPath, fs.constants.X_OK);
+    console.log('Pre-built `event` binaries found, skipping source build.');
+    process.exit(0);
+  } catch {
+    // Binaries not present or not executable — proceed to build from source
+  }
+
+  await buildEvent();
+}
+
+// `execFile` (not `exec`) so the install path is passed as a discrete argv
+// entry instead of being interpolated into a shell command. This keeps the
+// build deterministic even when the project lives under a directory that
+// contains spaces, `$`, backticks, or other shell-significant characters.
+async function buildEvent() {
+  const buildScript = path.join(projectRoot, 'scripts', 'build-event.mjs');
+  const { stdout } = await execFileAsync(process.execPath, [buildScript], {
+    cwd: projectRoot,
+  });
+  if (stdout) {
+    console.log(stdout);
+  }
+}
+
+main()
+  .then(() => {
+    console.log('`event` CLI built successfully');
+    process.exit(0);
+  })
+  .catch((error) => {
+    console.error(`\n${'='.repeat(70)}`);
+    console.error('WARNING: `event` CLI build failed');
+    console.error('='.repeat(70));
+    console.error('\nError details:', error.message);
+    console.error(
+      '\nThe MCP server requires the bundled `event` binary to function.',
+    );
+    console.error('\nTo build manually:');
+    console.error('  1. Navigate to the package directory');
+    console.error(
+      '  2. Initialize the submodule: git submodule update --init --recursive',
+    );
+    console.error('  3. Run: pnpm install && pnpm run build');
+    console.error('\nOr use a local clone instead of npx:');
+    console.error(
+      '  git clone --recurse-submodules https://github.com/fradser/mcp-server-apple-events.git',
+    );
+    console.error('  cd mcp-server-apple-events && pnpm install && pnpm build');
+    console.error(`${'='.repeat(70)}\n`);
+    process.exit(0); // Exit gracefully to not block installation
+  });