remove the bundled mcp server and replace it with manual configuration instruction

Author: jhou1

plugins/calendar/.mcp.json

@@ -15,7 +15,7 @@ Google Calendar integration for Claude Code, providing AI-powered tools to find
 
 - Claude Code installed
 - Google Calendar API access configured
-- Google Calendar MCP server(bundled)
+- Google Calendar MCP server running locally
 
 ## Setup
 
@@ -35,14 +35,24 @@ Google Calendar integration for Claude Code, providing AI-powered tools to find
    - Select **"Desktop app"** as the application type (Important!)
    - Download the auth key
 
-### 2. Environment Configuration
+### 2. MCP Server Setup
 
-After completing previous step, you must specify the credentials file path using the `GOOGLE_OAUTH_CREDENTIALS` environment variable prior to starting Claude Code, this tells the `google-calendar-mcp` MCP server where to look for auth keys.
+After completing the previous step, you need to set up the google-calendar MCP server locally.
 
-```bash
-export GOOGLE_OAUTH_CREDENTIALS=~/.config/client_secret_xxxxxxxxx.json
-claude
-```
+1. **Install the google-calendar MCP server** (if not already installed):
+   ```bash
+   npm install -g @cocal/google-calendar-mcp
+   ```
+
+2. **Set environment variable** for credentials:
+   ```bash
+   export GOOGLE_OAUTH_CREDENTIALS=~/.config/client_secret_xxxxxxxxx.json
+   ```
+
+3. **Add the MCP server to Claude Code** with the MCP server running:
+   ```bash
+   claude mcp add --transport stdio google-calendar -- npx @cocal/google-calendar-mcp
+   ```
 
 ## Installation
 
@@ -170,8 +180,10 @@ See [commands/create-event.md](commands/create-event.md) for full documentation.
 - Verify OAuth scopes include calendar access
 
 ### MCP Server Issues
-- Ensure `@cocal/google-calendar-mcp` is available via npm
-- Check that the MCP server is properly configured
+- Ensure `@cocal/google-calendar-mcp` is installed and available
+- Check that the MCP server is properly configured in your Claude Code settings
+- Verify the MCP server is running and accessible
+- Check that the google-calendar MCP functions are available (e.g., `mcp__google-calendar__*`)
 - Verify network connectivity for API calls
 
 For command-specific troubleshooting, see the individual command documentation.
@@ -182,4 +194,3 @@ For command-specific troubleshooting, see the individual command documentation.
 - **Calendar Data**: Free/busy information is queried in real-time and not stored
 - **Privacy**: Only calendar availability is accessed, not detailed event content
 - **Scope**: The plugin only requests minimal necessary Calendar API permissions
-

plugins/calendar/README.md

@@ -7,7 +7,7 @@ argument-hint: <natural_language_prompt_for_the_event>
 calendar:create-event
 
 ## Synopsis
-```
+```bash
 /calendar:create-event <natural_language_prompt_for_the_event>
 ```
 
@@ -38,20 +38,20 @@ The `calendar:create-event` command creates a new calendar event on Google Calen
 
 ### Phase 3: Format Event Data
 - Convert all dates and times to ISO 8601 format
-- Use `get-current-time` tool to determine user's timezone
+- Use `mcp__google-calendar__get-current-time` function to determine user's timezone
 - Ensure start time is before end time
 - Format attendee list properly for calendar API
 - Prepare event description with any additional context
 
 ### Phase 4: Ask For User Confirmation
 - Display the summary, meeting time, attendees, description 
 - Ask user to confirm
-- If user confirms, proceed to phase 5, otherwise, modify the summary, meeting time, attendees, description based on user's input until user confirms you correctly intepreted the intent.
+- If user confirms, proceed to phase 5, otherwise, modify the summary, meeting time, attendees, description based on user's input until user confirms you correctly interpreted the intent.
 
 ### Phase 5: Create Calendar Event
-- Use the `create-event` tool from the `plugin:calendar:google-calendar` MCP server
-- Automatically attach Google Meet link for virtual participation
-- Create event on user's primary calendar
+- Use the `mcp__google-calendar__create-event` function from the google-calendar MCP server
+- Automatically attach Google Meet link for virtual participation using the `conferenceData` parameter
+- Create event on user's primary calendar (calendarId: 'primary')
 - Include all parsed attendees, description, and meeting details
 - Handle calendar API responses and potential conflicts
 
@@ -79,27 +79,27 @@ The `calendar:create-event` command creates a new calendar event on Google Calen
 ## Examples
 
 1. **Simple meeting**:
-   ```
+   ```bash
    /calendar:create-event Team standup tomorrow at 9am for 30 minutes
    ```
 
 2. **Meeting with specific attendees**:
-   ```
+   ```bash
    /calendar:create-event Project review Friday 2pm with alice@company.com and bob@company.com
    ```
 
 3. **Detailed planning session**:
-   ```
+   ```bash
    /calendar:create-event Quarterly planning session next Monday 10am-12pm with the whole engineering team
    ```
 
 4. **Quick 1:1 meeting**:
-   ```
+   ```bash
    /calendar:create-event Coffee chat with Sarah tomorrow 3pm for 45 minutes
    ```
 
 5. **All-hands meeting**:
-   ```
+   ```bash
    /calendar:create-event Monthly all-hands meeting first Friday of next month 2-3pm with leadership team
    ```
 

plugins/calendar/commands/create-event.md

@@ -7,7 +7,7 @@ argument-hint: <email_addresses> [duration_in_minutes] [days_ahead]
 calendar:find-time
 
 ## Synopsis
-```
+```bash
 /calendar:find-time <email_addresses> [duration_in_minutes] [days_ahead]
 ```
 
@@ -24,9 +24,9 @@ The `calendar:find-time` command helps you find overlapping available time with
 - Convert duration to minutes if provided in other formats
 
 ### Phase 2: Gather Free/Busy Information
-- Use the `get-freebusy` tool from the `plugin:calendar:google-calendar` MCP server to get busy times for all participants
+- Use the `mcp__google-calendar__get-freebusy` function from the google-calendar MCP server to get busy times for all participants
 - Query the specified days_ahead for each participant's calendar
-- Get current time and primary calendar timezone using `get-current-time`
+- Get current time and primary calendar timezone using `mcp__google-calendar__get-current-time`
 
 ### Phase 3: Analyze Available Time Slots
 - Calculate free blocks by inverting busy periods for each participant
@@ -38,15 +38,15 @@ The `calendar:find-time` command helps you find overlapping available time with
 
 ### Phase 4: Generate Meeting Suggestions
 - Sort potential meeting times by preference (earlier in week, business hours, etc.)
-- Present top 3-5 options with clear time formatting
+- Present top 3–5 options with clear time formatting
 - Display times in the user's primary calendar timezone
 - Include day of week and date for clarity
 - Provide alternative suggestions if no perfect matches found
 
 ### Phase 5: Error Handling
 - Handle cases where no common free time exists
 - Provide helpful suggestions (shorter duration, different date range)
-- If you can't access a calendar, give up the operation gracefully. Then tell the user that the email adress maybe wrong
+- If you can't access a calendar, give up the operation gracefully. Then tell the user that the email address might be wrong
 - Validate that all email addresses have accessible calendars
 
 ## Return Value
@@ -60,17 +60,17 @@ The `calendar:find-time` command helps you find overlapping available time with
 ## Examples
 
 1. **Basic usage with two people**:
-   ```
+   ```bash
    /calendar:find-time alice@company.com,bob@company.com 60
    ```
 
 2. **Including date range**:
-   ```
+   ```bash
    /calendar:find-time team@company.com,manager@company.com 30 7
    ```
 
 3. **Multiple participants with specific date**:
-   ```
+   ```bash
    /calendar:find-time alice@company.com,bob@company.com,carol@company.com 45 15
    ```