.codex-plugin/plugin.json

{
  "author": {
    "name": "PPJ Venture Labs UG (haftungsbeschr\u00e4nkt)"
  },
  "description": "Check availability, manage events and sync connected calendars. With separate permission, publish public subscribe calendars and get a website subscribe button.",
  "interface": {
    "capabilities": [],
    "category": "Productivity",
    "defaultPrompt": [
      "When am I free for two hours this week?",
      "Preview a one-way sync from my work calendar to my personal calendar, showing availability only.",
      "Here is my schedule for the month. Enter it all and flag anything that clashes."
    ],
    "developerName": "PPJ Venture Labs UG (haftungsbeschr\u00e4nkt)",
    "displayName": "Kalender Sync",
    "longDescription": "Kalender Sync connects Google Calendar, Microsoft Outlook, Apple iCloud and supported CalDAV calendars to ChatGPT and Codex. Check your schedule, find available times, search appointments, create and manage events, and answer supported invitations. You can also connect read-only iCal feeds where your plan supports them.\n\nCreate one-way or two-way syncs between your own connected calendars. Preview a sync before confirming its source, target and detail level. Check its status, diagnose issues, and pause or resume it. Sync targets require write access and explicit sync-management permission. Deleting a sync requires a preview and confirmation: its copies are removed, while source events remain. Syncs keep running after assistant access is revoked until paused or deleted.\n\nFor connected calendars, you choose which calendars the assistant can access: availability only, titles and times, or full details. Creating events needs write permission; managing existing events needs management permission and full details. Updates, deletions and invitation replies can notify participants. Provider restrictions apply: CalDAV invitation replies depend on the provider; iCloud supports replies to iCloud invitations, not Google or Outlook. iCal feeds are read-only.\n\nWith separate permission, create public subscribe calendars for a website, publish and update their events, check aggregate subscriber statistics, and get a subscribe button. This access covers the subscribe calendars owned by your account. Sandbox calendars are public too, with a test label. Confirm the intended public content before publishing; do not use private calendar data without explicit approval.\n\nUse the included skills to plan your day or week, import a schedule, timebox tasks, plan time off and make room for recurring goals. The assistant proposes a plan before creating appointments and reports conflicts and incomplete reads. Calendar reads can be cached for up to 60 seconds.\n\nTry asking: \u201cWhen do I have a free two-hour block next week?\u201d or \u201cPreview a one-way sync from work to personal, showing availability only.\u201d\n\nA Kalender Sync account is required; personal planning and syncs also need connected calendars. Providers, calendar counts and usage limits depend on your account permissions and entitlements. Hosted in Germany.",
    "privacyPolicyURL": "https://kalender-sync.de/en/privacy-policy/",
    "shortDescription": "Check and book your calendars",
    "supportURL": "https://kalender-sync.de/en/contact/",
    "termsOfServiceURL": "https://kalender-sync.de/en/terms/",
    "websiteURL": "https://kalender-sync.de/en/?ref=chatgpt_directory",
    "logo": "./assets/logo.png",
    "composerIcon": "./assets/logo.png"
  },
  "name": "app-6a789d2ee20c8191a7abd7c3736a7c2c",
  "skills": "./skills",
  "version": "3.1.0",
  "extensions": {
    "com.openai": {
      "publication": {
        "release_notes": "Kalender Sync 3.1.0 review candidate, based on the approved 3.0.1 package.\n\nThe short description, publisher identity, original logo, legal/support URLs and MCP endpoint are retained from 3.0.1. The About text keeps the calendar-first structure and adds syncs, public subscribe calendars, Codex and current provider/permission limits. One example prompt requests a sync preview.\n\nThe same eight skills and frontmatter descriptions are retained. Shared guidance covers the 15 calendar/event/sync tools and seven opt-in Publisher tools (up to 22 total). It explains persistent syncs, preview/confirmation, public sandbox data, account-wide Publisher access, partial writes and permission boundaries. No new tool definition or OAuth grant is embedded in this ZIP. Users must separately opt into publisher.manage; existing grants are not broadened. Reminder instructions apply only when the client exposes the corresponding schema.\n\nThe remote server supplies MCP definitions separately. Prepared server version: MCP 1.11.1. Its Publisher annotations mark public creation, metadata overwrites and event writes as readOnlyHint:false, destructiveHint:true, openWorldHint:true. The four Publisher read tools use true/false/false. Calendar creation is not idempotent; the other Publisher operations are. No new handler or scope is introduced by this correction.\n\nLocal validation: approved-source ZIP integrity, JSON/asset paths, eight skill frontmatter checks, unchanged endpoint/logo and an allowlisted package diff. Server preflight: typechecks, lint and unit tests passed; 22 Publisher/discovery/feed/plan integration tests passed against disposable Postgres, including 22-tool discovery with full consent, cross-account isolation, partial results and update/delete behavior. These are local checks, not a claim of an OpenAI scan or reviewer OAuth test.\n\nBefore submission: deploy the reviewed server correction, explicitly extend the reviewer connection with publisher.manage, scan all 22 tools, inspect findings and perform consented live tests using synthetic public data only. Keep existing calendar grants limited to the two review calendars. The metadata review does not replace tool review. No support case is requested.\n"
      }
    }
  },
  "mcpServers": "./.mcp.json",
  "apps": "./.app.json"
}