mcp-gee-sweet 0.7.0.dev67__tar.gz → 0.7.0.dev69__tar.gz

mcp_gee_sweet-0.7.0.dev69/.github/workflows/docs.yml

@@ -0,0 +1,45 @@
+name: Docs
+
+on:
+  push:
+    branches: ["main", "develop"]
+
+permissions:
+  contents: write  # needed for mike to push to gh-pages branch
+
+jobs:
+  deploy:
+    name: Build and publish docs
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v7
+        with:
+          fetch-depth: 0  # full history so mike can see existing gh-pages versions
+
+      - name: Install uv
+        uses: astral-sh/setup-uv@v8.2.0
+
+      - name: Set up Python 3.12
+        run: uv python install 3.12
+
+      - name: Install dependencies
+        run: uv sync --frozen --all-extras --dev --python 3.12
+
+      - name: Configure git identity
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+
+      - name: Fetch existing gh-pages
+        run: git fetch origin gh-pages --depth=1 || true
+
+      - name: Deploy docs (main -> latest)
+        if: github.ref == 'refs/heads/main'
+        run: |
+          uv run mike deploy --push --update-aliases main latest
+          uv run mike set-default --push latest
+
+      - name: Deploy docs (develop)
+        if: github.ref == 'refs/heads/develop'
+        run: uv run mike deploy --push develop

{mcp_gee_sweet-0.7.0.dev67 → mcp_gee_sweet-0.7.0.dev69}/CONTRIBUTING.md

@@ -29,9 +29,9 @@ Two ways to supply configuration — pick whichever fits how you're running the
   ```bash
   cp src/mcp_gee_sweet/.env.template src/mcp_gee_sweet/.env
   ```
-- **Your MCP client's config directly** — if you're pointing your client at `uv run --directory /path/to/mcp-gee-sweet mcp-gee-sweet` (the README's stdio quick-start), you can set env vars in the client's `env` block instead, the same way the [MCP client config](https://khuisman.github.io/mcp-gee-sweet/client-setup/) examples do. Many contributors find this a better day-to-day experience than maintaining a separate `.env` file — client config takes precedence over `.env` either way.
+- **Your MCP client's config directly** — if you're pointing your client at `uv run --directory /path/to/mcp-gee-sweet mcp-gee-sweet` (the README's stdio quick-start), you can set env vars in the client's `env` block instead, the same way the [MCP client config](https://khuisman.github.io/mcp-gee-sweet/latest/client-setup/) examples do. Many contributors find this a better day-to-day experience than maintaining a separate `.env` file — client config takes precedence over `.env` either way.
 
-At minimum you need one auth method and a Drive folder. Full details on all four methods (including GCP setup steps) are in [Authentication](https://khuisman.github.io/mcp-gee-sweet/auth/); the full environment variable reference is in [Configuration](https://khuisman.github.io/mcp-gee-sweet/configuration/).
+At minimum you need one auth method and a Drive folder. Full details on all four methods (including GCP setup steps) are in [Authentication](https://khuisman.github.io/mcp-gee-sweet/latest/auth/); the full environment variable reference is in [Configuration](https://khuisman.github.io/mcp-gee-sweet/latest/configuration/).
 
 #### Choosing an auth method
 
@@ -65,7 +65,7 @@ The assistant will:
 - Populate them with known fixture data
 - Write `TEST_*` IDs to your `.env`
 
-**If you are using service account auth:** the folder and both files must be shared with the service account email. Find it at `service_account.json` → `client_email`. The service account cannot access files in personal Drive unless explicitly shared — see [Authentication](https://khuisman.github.io/mcp-gee-sweet/auth/) for the sharing steps.
+**If you are using service account auth:** the folder and both files must be shared with the service account email. Find it at `service_account.json` → `client_email`. The service account cannot access files in personal Drive unless explicitly shared — see [Authentication](https://khuisman.github.io/mcp-gee-sweet/latest/auth/) for the sharing steps.
 
 ### 4. Enable observability
 
@@ -87,7 +87,7 @@ Every tool call emits one line to the access log:
 - `make logs` — tail Docker container logs directly (SSE; `DEBUG_LEVEL=DEBUG` is already the Docker Compose default, no `.env` change needed)
 - `make access-logs` — tail `ACCESS_LOG_FILE` only, if set
 
-Full details on log levels and file routing: [Configuration → Logging](https://khuisman.github.io/mcp-gee-sweet/configuration/).
+Full details on log levels and file routing: [Configuration → Logging](https://khuisman.github.io/mcp-gee-sweet/latest/configuration/).
 
 ### 5. Run the server
 
@@ -143,7 +143,7 @@ Every new tool must have at least:
 - The tool included in the `docs/qa-checklist.md` attestation
 - The tool's happy-path TC added to the smoke suite in `docs/qa/runs/README.md`
 
-See [Design Principles](https://khuisman.github.io/mcp-gee-sweet/design/) for the tool inclusion criteria and composite tool rules.
+See [Design Principles](https://khuisman.github.io/mcp-gee-sweet/latest/design/) for the tool inclusion criteria and composite tool rules.
 
 ---
 

{mcp_gee_sweet-0.7.0.dev67 → mcp_gee_sweet-0.7.0.dev69}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mcp-gee-sweet
-Version: 0.7.0.dev67
+Version: 0.7.0.dev69
 Summary: MCP server for Google Workspace — Sheets, Drive, Docs, and Calendar. 60+ tools for AI clients.
 Project-URL: Homepage, https://github.com/khuisman/mcp-gee-sweet
 Project-URL: Bug Tracker, https://github.com/khuisman/mcp-gee-sweet/issues
@@ -83,7 +83,7 @@ The server tries auth methods in a waterfall by default, OAuth first — it auth
 export CREDENTIALS_PATH="/path/to/credentials.json"
 ```
 
-Service accounts (recommended for headless server deployments — see Option B above), base64 credential injection, and Application Default Credentials are also supported. See [Authentication](https://khuisman.github.io/mcp-gee-sweet/auth/) for all options.
+Service accounts (recommended for headless server deployments — see Option B above), base64 credential injection, and Application Default Credentials are also supported. See [Authentication](https://khuisman.github.io/mcp-gee-sweet/latest/auth/) for all options.
 
 ---
 
@@ -116,18 +116,18 @@ Service accounts (recommended for headless server deployments — see Option B a
 }
 ```
 
-See [Client Setup](https://khuisman.github.io/mcp-gee-sweet/client-setup/) for more options including tool filtering.
+See [Client Setup](https://khuisman.github.io/mcp-gee-sweet/latest/client-setup/) for more options including tool filtering.
 
 ---
 
 ## Docs
 
-- [Tools](https://khuisman.github.io/mcp-gee-sweet/tools/) — full tool reference (84 tools)
-- [Authentication](https://khuisman.github.io/mcp-gee-sweet/auth/) — all four auth methods
-- [Configuration](https://khuisman.github.io/mcp-gee-sweet/configuration/) — env vars, caching, tool filtering
-- [Client Setup](https://khuisman.github.io/mcp-gee-sweet/client-setup/) — MCP client config examples
-- [Design Principles](https://khuisman.github.io/mcp-gee-sweet/design/) — tool inclusion policy, composite tool decisions
-- [Roadmap](https://khuisman.github.io/mcp-gee-sweet/roadmap/) — planned features and known gaps
+- [Tools](https://khuisman.github.io/mcp-gee-sweet/latest/tools/) — full tool reference (84 tools)
+- [Authentication](https://khuisman.github.io/mcp-gee-sweet/latest/auth/) — all four auth methods
+- [Configuration](https://khuisman.github.io/mcp-gee-sweet/latest/configuration/) — env vars, caching, tool filtering
+- [Client Setup](https://khuisman.github.io/mcp-gee-sweet/latest/client-setup/) — MCP client config examples
+- [Design Principles](https://khuisman.github.io/mcp-gee-sweet/latest/design/) — tool inclusion policy, composite tool decisions
+- [Roadmap](https://khuisman.github.io/mcp-gee-sweet/latest/roadmap/) — planned features and known gaps
 
 ---
 

{mcp_gee_sweet-0.7.0.dev67 → mcp_gee_sweet-0.7.0.dev69}/README.md

@@ -61,7 +61,7 @@ The server tries auth methods in a waterfall by default, OAuth first — it auth
 export CREDENTIALS_PATH="/path/to/credentials.json"
 ```
 
-Service accounts (recommended for headless server deployments — see Option B above), base64 credential injection, and Application Default Credentials are also supported. See [Authentication](https://khuisman.github.io/mcp-gee-sweet/auth/) for all options.
+Service accounts (recommended for headless server deployments — see Option B above), base64 credential injection, and Application Default Credentials are also supported. See [Authentication](https://khuisman.github.io/mcp-gee-sweet/latest/auth/) for all options.
 
 ---
 
@@ -94,18 +94,18 @@ Service accounts (recommended for headless server deployments — see Option B a
 }
 ```
 
-See [Client Setup](https://khuisman.github.io/mcp-gee-sweet/client-setup/) for more options including tool filtering.
+See [Client Setup](https://khuisman.github.io/mcp-gee-sweet/latest/client-setup/) for more options including tool filtering.
 
 ---
 
 ## Docs
 
-- [Tools](https://khuisman.github.io/mcp-gee-sweet/tools/) — full tool reference (84 tools)
-- [Authentication](https://khuisman.github.io/mcp-gee-sweet/auth/) — all four auth methods
-- [Configuration](https://khuisman.github.io/mcp-gee-sweet/configuration/) — env vars, caching, tool filtering
-- [Client Setup](https://khuisman.github.io/mcp-gee-sweet/client-setup/) — MCP client config examples
-- [Design Principles](https://khuisman.github.io/mcp-gee-sweet/design/) — tool inclusion policy, composite tool decisions
-- [Roadmap](https://khuisman.github.io/mcp-gee-sweet/roadmap/) — planned features and known gaps
+- [Tools](https://khuisman.github.io/mcp-gee-sweet/latest/tools/) — full tool reference (84 tools)
+- [Authentication](https://khuisman.github.io/mcp-gee-sweet/latest/auth/) — all four auth methods
+- [Configuration](https://khuisman.github.io/mcp-gee-sweet/latest/configuration/) — env vars, caching, tool filtering
+- [Client Setup](https://khuisman.github.io/mcp-gee-sweet/latest/client-setup/) — MCP client config examples
+- [Design Principles](https://khuisman.github.io/mcp-gee-sweet/latest/design/) — tool inclusion policy, composite tool decisions
+- [Roadmap](https://khuisman.github.io/mcp-gee-sweet/latest/roadmap/) — planned features and known gaps
 
 ---
 

{mcp_gee_sweet-0.7.0.dev67 → mcp_gee_sweet-0.7.0.dev69}/docs/configuration.md

@@ -69,7 +69,7 @@ Access logs are emitted at `INFO` level — they appear when `DEBUG_LEVEL` is `D
 
 <!-- Auto-generated by `scripts/gen_tool_docs.py` — do not edit by hand, your changes will be overwritten on the next commit. -->
 
-By default all 84 tools are registered. Use `ENABLED_TOOLS` (or `--include-tools` on the CLI) to restrict the server to exactly the tools you need. This reduces the AI's context window cost — each registered tool is a name the model must reason about on every call.
+By default all 87 tools are registered. Use `ENABLED_TOOLS` (or `--include-tools` on the CLI) to restrict the server to exactly the tools you need. This reduces the AI's context window cost — each registered tool is a name the model must reason about on every call.
 
 ```bash
 # Environment variable
@@ -100,7 +100,7 @@ create_doc,get_doc_content,get_doc_structure,write_doc_content,insert_doc_text,i
 
 **Calendar only:**
 ```
-list_calendars,get_calendar,list_events,get_event,create_event,update_event,delete_event,find_free_slots
+list_calendars,get_calendar,create_calendar,update_calendar,delete_calendar,list_events,get_event,create_event,update_event,delete_event,find_free_slots
 ```
 
 See [Tools](tools.md) for the full list of tool names.

{mcp_gee_sweet-0.7.0.dev67 → mcp_gee_sweet-0.7.0.dev69}/docs/qa/tests/calendar.md

@@ -105,6 +105,144 @@ Fixtures: see [`docs/qa/setup.md`](../setup.md). Substitute your `{CALENDAR_ID}`
 
 ---
 
+## `create_calendar`
+
+### TC-CAL44: Create a secondary calendar ⚠️ destructive
+
+**Prompt**
+> "Create a new calendar called 'mcp-gee-sweet-qa-lifecycle-test' with description 'QA scratch calendar' and timezone 'America/Los_Angeles'"
+
+**Checks**
+- Returns `id`, `summary`, `description`, `time_zone`
+- `summary` is `mcp-gee-sweet-qa-lifecycle-test`
+- `time_zone` is `America/Los_Angeles`
+- The new calendar appears in a follow-up `list_calendars` call (cache invalidated)
+
+**Result (2026-07-05) ✅** — Created via OAuth; response had `summary`, `description`, and `time_zone: "America/Los_Angeles"` exactly as requested. Confirmed present in a follow-up `list_calendars` call.
+
+---
+
+### TC-CAL45: Create with only summary
+
+**Prompt**
+> "Create a new calendar called 'mcp-gee-sweet-qa-minimal'"
+
+**Checks**
+- Succeeds with only `summary` provided
+- `description` is `null`/absent
+- `time_zone` reflects the account default
+
+**Result (2026-07-05) ✅** — Created with only `summary` provided. `description: null`. `time_zone: "UTC"` (account default rather than the creator's local timezone — noted for documentation purposes). Confirmed present in a follow-up `list_calendars` call.
+
+---
+
+## `update_calendar`
+
+### TC-CAL46: Rename and change timezone ⚠️ destructive
+
+**Setup:** use the calendar created in TC-CAL44
+
+**Prompt**
+> "Update calendar 'mcp-gee-sweet-qa-lifecycle-test' — rename it to 'mcp-gee-sweet-qa-renamed' and set its timezone to 'America/New_York'"
+
+**Checks**
+- `summary` is `mcp-gee-sweet-qa-renamed`
+- `time_zone` is `America/New_York`
+- `description` unchanged from TC-CAL44
+- `get_calendar` on the same ID reflects the new values
+
+**Result (2026-07-05) ✅** — Patched with `summary: "mcp-gee-sweet-qa-renamed"` and `timezone: "America/New_York"`. Response reflected both changes; `description` unchanged from TC-CAL44 (`"QA scratch calendar"`).
+
+---
+
+### TC-CAL47: Change color only ⚠️ destructive
+
+**Setup:** use the calendar from TC-CAL44/46
+
+**Prompt**
+> "Change the color of calendar 'mcp-gee-sweet-qa-renamed' to color ID '5'"
+
+**Checks**
+- `color_id` in the response is `5`
+- `summary`/`description`/`time_zone` unchanged (verify with `get_calendar`)
+- Confirms the color patch goes through `calendarList().patch()`, not `calendars().patch()`
+
+**Result (2026-07-05) ✅** — Patched `color_id="5"` only (no summary/description/timezone). Response had `color_id: "5"` with `summary`, `description`, `time_zone` all unchanged from TC-CAL46 — confirms the tool fell back to `calendars().get()` for the base fields and routed color through `calendarList().patch()`.
+
+---
+
+### TC-CAL48: No fields provided
+
+**Prompt**
+> "Update calendar {CALENDAR_ID} with no changes — just fetch its current state through update_calendar"
+
+**Checks**
+- Returns current calendar metadata unchanged
+- `color_id` is `null` (no color patch attempted)
+- No API error
+
+**Result (2026-07-05) ✅** — Called with `calendar_id="primary"` and no other fields. Returned the account's real primary calendar summary/timezone unchanged, `color_id: null`. Confirms the no-op path uses `calendars().get()` without issuing any patch.
+
+---
+
+### TC-CAL49: Non-existent calendar ID
+
+**Prompt**
+> "Update calendar 'totally-invalid-cal-id@example.com' — rename it to 'Nope'"
+
+**Checks**
+- Returns `{"error": "..."}` — not a top-level exception
+
+**Result (2026-07-05) ✅** — Returned `{"error": "<HttpError 404 ... 'reason': 'notFound' ...>"}`. No exception raised.
+
+---
+
+## `delete_calendar`
+
+### TC-CAL50: Delete a calendar ⚠️ destructive
+
+**Setup:** use the calendar created in TC-CAL44 (after TC-CAL46/47 updates)
+
+**Prompt**
+> "Delete the calendar 'mcp-gee-sweet-qa-renamed'"
+
+**Checks**
+- Returns `{"calendar_id": "...", "action": "deleted"}`
+- Calendar no longer appears in a follow-up `list_calendars` call
+- `get_calendar` on the deleted ID returns an error
+
+**Result (2026-07-05) ✅** — Returned `{"calendar_id": "...", "action": "deleted"}`. Confirmed absent from a follow-up `list_calendars` call. `get_calendar` on the deleted ID returned a 404 `notFound` error.
+
+---
+
+### TC-CAL51: Delete the minimal test calendar ⚠️ destructive
+
+**Setup:** use the calendar created in TC-CAL45
+
+**Prompt**
+> "Delete the calendar 'mcp-gee-sweet-qa-minimal'"
+
+**Checks**
+- Returns `{"calendar_id": "...", "action": "deleted"}`
+- Cleans up the fixture so it doesn't linger in the account's calendar list
+
+**Result (2026-07-05) ✅** — Returned `{"calendar_id": "...", "action": "deleted"}`. Confirmed removed from the account's `list_calendars` output alongside TC-CAL50's cleanup.
+
+---
+
+### TC-CAL52: Non-existent calendar ID
+
+**Prompt**
+> "Delete the calendar 'totally-invalid-cal-id@example.com'"
+
+**Checks**
+- Returns `{"error": "..."}` — not a top-level exception
+- No side effects
+
+**Result (2026-07-05) ✅** — Returned `{"error": "<HttpError 404 ... 'reason': 'notFound' ...>"}`. No side effects.
+
+---
+
 ## `list_events`
 
 ### TC-CAL09: No time filters — upcoming events

{mcp_gee_sweet-0.7.0.dev67 → mcp_gee_sweet-0.7.0.dev69}/docs/tools.md

@@ -2,7 +2,7 @@
 
 <!-- Auto-generated by `scripts/gen_tool_docs.py` — do not edit by hand, your changes will be overwritten on the next commit. -->
 
-84 tools. All tool names are lowercase with underscores — use these exact strings with `ENABLED_TOOLS` or `--include-tools`.
+87 tools. All tool names are lowercase with underscores — use these exact strings with `ENABLED_TOOLS` or `--include-tools`.
 
 ## Sheets — data
 
@@ -141,6 +141,9 @@ Requires the `drive.activity.readonly` scope; uses the Drive Activity API v2.
 |---|---|---|
 | `list_calendars` | List all calendars accessible to the authenticated user. | — |
 | `get_calendar` | Fetch metadata for a single calendar. | `calendar_id` |
+| `create_calendar` | Create a new secondary calendar owned by the authenticated user. | `summary`, `description?`, `timezone?` |
+| `update_calendar` | Update fields on an existing calendar using patch semantics. Only the fields you provide are changed; omitted fields are left as-is. | `calendar_id`, `summary?`, `description?`, `timezone?`, `color_id?` |
+| `delete_calendar` | Permanently delete a calendar. For calendars you own, this deletes the calendar entirely for all users it is shared with — use with caution. To only stop seeing a calendar in your own list, use remove_calendar_from_list instead. | `calendar_id` |
 | `list_events` | List events in a calendar. | `calendar_id`, `time_min?`, `time_max?`, `query?`, `max_results?`, `expand_recurring?` |
 | `get_event` | Fetch a single event by calendar ID and event ID. | `calendar_id`, `event_id` |
 | `create_event` | Create a new event in a calendar. | `calendar_id`, `summary`, `start`, `end`, `description?`, `location?`, `attendees?`, `timezone?`, `recurrence?` |

{mcp_gee_sweet-0.7.0.dev67 → mcp_gee_sweet-0.7.0.dev69}/mkdocs.yml

@@ -33,6 +33,10 @@ markdown_extensions:
       anchor_linenums: true
   - pymdownx.superfences
 
+extra:
+  version:
+    provider: mike
+
 nav:
   - Home: index.md
   - Reference:

{mcp_gee_sweet-0.7.0.dev67 → mcp_gee_sweet-0.7.0.dev69}/pyproject.toml

@@ -58,6 +58,7 @@ ignore = ["E501"]
 dev = [
     "mkdocs>=1.6.0",
     "mkdocs-material>=9.5.0",
+    "mike>=2.1.0",
     "pre-commit>=4.6.0",
     "pytest>=8.0.0",
     "pytest-cov>=6.0.0",

{mcp_gee_sweet-0.7.0.dev67 → mcp_gee_sweet-0.7.0.dev69}/scripts/gen_tool_docs.py

@@ -215,6 +215,9 @@ SUBSETS = [
         [
             "list_calendars",
             "get_calendar",
+            "create_calendar",
+            "update_calendar",
+            "delete_calendar",
             "list_events",
             "get_event",
             "create_event",

{mcp_gee_sweet-0.7.0.dev67 → mcp_gee_sweet-0.7.0.dev69}/src/mcp_gee_sweet/tools/calendar.py

@@ -73,6 +73,140 @@ def register(tool):
         cache.store(calendar_id, result)
         return result
 
+    @tool(annotations=ToolAnnotations(title="Create Calendar", destructiveHint=True))
+    def create_calendar(
+        summary: str,
+        description: str | None = None,
+        timezone: str | None = None,
+        ctx: Context = None,
+    ) -> dict[str, Any]:
+        """
+        Create a new secondary calendar owned by the authenticated user.
+
+        Args:
+            summary: Calendar title.
+            description: Optional calendar description.
+            timezone: IANA timezone name (e.g. 'America/Los_Angeles'). Defaults to
+                      the account's timezone if omitted.
+
+        Returns:
+            Created calendar: id, summary, description, time_zone.
+        """
+        lc = ctx.request_context.lifespan_context
+
+        body: dict[str, Any] = {"summary": summary}
+        if description:
+            body["description"] = description
+        if timezone:
+            body["timeZone"] = timezone
+
+        try:
+            c = lc.calendar_service.calendars().insert(body=body).execute()
+        except Exception as e:
+            return {"error": str(e)}
+
+        lc.calendar_cache.mark_dirty(c["id"])
+        logger.debug("Created calendar %s", c["id"])
+        return {
+            "id": c["id"],
+            "summary": c.get("summary", ""),
+            "description": c.get("description"),
+            "time_zone": c.get("timeZone"),
+        }
+
+    @tool(annotations=ToolAnnotations(title="Update Calendar", destructiveHint=True))
+    def update_calendar(
+        calendar_id: str,
+        summary: str | None = None,
+        description: str | None = None,
+        timezone: str | None = None,
+        color_id: str | None = None,
+        ctx: Context = None,
+    ) -> dict[str, Any]:
+        """
+        Update fields on an existing calendar using patch semantics. Only the
+        fields you provide are changed; omitted fields are left as-is.
+
+        Note: color_id is set via the authenticated user's calendar list entry
+        (calendarList().patch()), not the calendar resource itself — it is a
+        per-user setting, not a property of the calendar shared with others.
+
+        Args:
+            calendar_id: The calendar ID, or 'primary'.
+            summary: New calendar title.
+            description: New calendar description.
+            timezone: New IANA timezone name (e.g. 'America/Los_Angeles').
+            color_id: New color ID from the palette returned by the Calendar API's
+                      colors().get() endpoint (predefined IDs, typically '1'-'24').
+
+        Returns:
+            Updated calendar: id, summary, description, time_zone, color_id.
+        """
+        lc = ctx.request_context.lifespan_context
+
+        patch: dict[str, Any] = {}
+        if summary is not None:
+            patch["summary"] = summary
+        if description is not None:
+            patch["description"] = description
+        if timezone is not None:
+            patch["timeZone"] = timezone
+
+        try:
+            if patch:
+                c = (
+                    lc.calendar_service.calendars()
+                    .patch(calendarId=calendar_id, body=patch)
+                    .execute()
+                )
+            else:
+                c = lc.calendar_service.calendars().get(calendarId=calendar_id).execute()
+
+            result_color_id = None
+            if color_id is not None:
+                list_entry = (
+                    lc.calendar_service.calendarList()
+                    .patch(calendarId=calendar_id, body={"colorId": color_id})
+                    .execute()
+                )
+                result_color_id = list_entry.get("colorId")
+        except Exception as e:
+            return {"error": str(e)}
+
+        lc.calendar_cache.mark_dirty(calendar_id)
+        logger.debug("Updated calendar %s", calendar_id)
+        return {
+            "id": c.get("id", calendar_id),
+            "summary": c.get("summary", ""),
+            "description": c.get("description"),
+            "time_zone": c.get("timeZone"),
+            "color_id": result_color_id,
+        }
+
+    @tool(annotations=ToolAnnotations(title="Delete Calendar", destructiveHint=True))
+    def delete_calendar(calendar_id: str, ctx: Context = None) -> dict[str, Any]:
+        """
+        Permanently delete a calendar. For calendars you own, this deletes the
+        calendar entirely for all users it is shared with — use with caution.
+        To only stop seeing a calendar in your own list, use
+        remove_calendar_from_list instead.
+
+        Args:
+            calendar_id: The calendar ID to delete.
+
+        Returns:
+            Confirmation with calendar_id and action 'deleted'.
+        """
+        lc = ctx.request_context.lifespan_context
+        try:
+            lc.calendar_service.calendars().delete(calendarId=calendar_id).execute()
+        except Exception as e:
+            return {"error": str(e)}
+
+        lc.calendar_cache.mark_dirty(calendar_id)
+        logger.debug("Deleted calendar %s", calendar_id)
+        return {"calendar_id": calendar_id, "action": "deleted"}
+
     @tool(annotations=ToolAnnotations(title="List Events", readOnlyHint=True))
     def list_events(
         calendar_id: str,