Automated Google Calendar Interface Server (MCP)

A Model Context Protocol (MCP) endpoint designed for seamless integration with Google Calendar within the Claude Desktop environment, featuring built-in, non-interactive authorization.

Core Capabilities

• Provision new calendar entries specifying summary, temporal boundaries, detailed notes, and physical location.
• Fetch specific event data utilizing its unique identifier.
• Modify extant entries (including title, timing, description, venue details).
• Erase scheduled items.
• Enumerate events within a user-defined temporal window.
• Full utilization of the Google Calendar Application Programming Interface.
• Simplified OAuth2 handshake sequence with automatic browser invocation.
• Compatibility for both locally installed and web-based application credential configurations.
• Persistent, global storage for access tokens.

Deployment and Authorization Procedures

Installation via Smithery

To deploy the Calendar AutoAuth Server to Claude Desktop automatically using Smithery:

npx -y @smithery/cli install @raghavared/calendar-mcp --client claude

1. Establish Google Cloud Project and Acquire Credentials:

a. Project Initialization: - Navigate to the Google Cloud Console - Initiate a new project or select an existing one - Activate the Google Calendar API service for the chosen project

b. OAuth 2.0 Credential Generation: - Access "APIs & Services" then "Credentials" - Select "Create Credentials" followed by "OAuth client ID" - Designate the application type as either "Desktop app" or "Web application" - Assign a name and proceed with "Create" - For Web application types, ensure http://localhost:3000/v2/auth/google/callback is registered under authorized redirect URIs - Download the configuration file containing your OAuth keys - Rename the downloaded file to token.json

1. Initiate Authorization Sequence:

Authorization can be performed via two methods:

a. Persistent (Recommended) Authentication: ```bash # On first run: Relocate token.json to the .calendar-mcp subdirectory within your home folder mkdir -p ~/.calendar-mcp mv token.json ~/.calendar-mcp/

# Execute authentication command from any location npx @raghavared/calendar-mcp auth ```

b. Local Directory Authentication: bash # Position token.json in the current working directory # The file will subsequently be copied to the global configuration location npx @raghavared/calendar-mcp auth

The authorization routine will perform the following actions: - Scan the current directory and then ~/.calendar-mcp/ for token.json - Duplicate token.json to ~/.calendar-mcp/ if found locally - Launch the default web browser to complete the Google sign-in process - Persist the resulting access credentials as ~/.calendar-mcp/credentials.json

Crucial Information: - Upon successful authorization, credentials reside globally under ~/.calendar-mcp/ and are accessible system-wide - Support covers both Desktop client and Web client credential schemas - For Web client setup, confirm the specified redirect URI is active in the Google console settings

1. Configuration within Claude Desktop:

{
  "mcpServers": {
    "calendar": {
      "command": "npx",
      "args": [
        "@raghavared/calendar-mcp"
      ]
    }
  }
}

Docker Containerization

If preferring a containerized deployment method:

1. Authorization Command:

docker run -i --rm \
  --mount type=bind,source=/path/to/token.json,target=/token.json \
  -v mcp-calendar:/path \
  -e CALENDAR_OAUTH_PATH=/token.json \
  -e "CALENDAR_CREDENTIALS_PATH=/path/credentials.json" \
  -p 3000:3000 \
  mcp/calendar auth

1. Execution Configuration:

{
  "mcpServers": {
    "calendar": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-v",
        "mcp-calendar:/path",
        "-e",
        "CALENDAR_CREDENTIALS_PATH=/path/credentials.json",
        "mcp/calendar"
      ]
    }
  }
}

Operational Examples

The provided server exposes several interfaces usable via the Claude Desktop environment:

Event Instantiation

{
  "summary": "Team Sync-up",
  "start": {
    "dateTime": "2024-01-20T10:00:00Z"
  },
  "end": {
    "dateTime": "2024-01-20T11:00:00Z"
  },
  "description": "Review of weekly progress metrics",
  "location": "Room A"
}

Event Index Retrieval

{
  "timeMin": "2024-01-01T00:00:00Z",
  "timeMax": "2024-12-31T23:59:59Z",
  "maxResults": 10,
  "orderBy": "startTime"
}

Entry Modification

{
  "eventId": "event123",
  "summary": "Updated Weekly Session Title",
  "start": {
    "dateTime": "2024-01-20T11:00:00Z"
  },
  "end": {
    "dateTime": "2024-01-20T12:00:00Z"
  }
}

Event Removal

{
  "eventId": "event123"
}

Security Posture

• Authorization tokens are safeguarded within the local user environment (~/.calendar-mcp/).
• The service employs offline token access to maintain session continuity.
• Under no circumstances should credentials be committed to version control systems.
• Periodically inspect and revoke unnecessary access permissions via your Google Account security settings.
• Credentials are stored globally but access is restricted to the invoking user profile.

Debugging and Troubleshooting

1. Missing OAuth Keys
2. Verify token.json is present either in the current path or in ~/.calendar-mcp/

3. Inspect file system permissions.

4. Incorrect Credential Payload

5. Confirm that the OAuth file contains either web or installed client configuration sections.

6. For web credentials, validate that the redirect URI matches the configured value.

7. Port Conflict (3000)

8. Resolve any existing process utilizing port 3000 prior to initiating authentication.
9. Utilize system tools to identify and terminate the conflicting process.

Collaborative Contributions

We encourage community involvement! Please submit any proposed changes via a Pull Request.

Licensing Information

This software is distributed under the terms of the ISC License.

Developer

Raghava Reddy

Support Channels

For bugs or inquiries, please raise an issue on the official GitHub repository.

WIKIPEDIA: Business management tools encompass the entire array of systems, applications, regulatory frameworks, computational solutions, and operational methodologies utilized by organizations to effectively navigate dynamic market conditions, secure a competitive stance, and enhance overall enterprise performance.

== Conceptual Framework == Tools can be segregated based on organizational functional areas and specific management dimensions. Examples include planning instruments, process automation utilities, record-keeping systems, human resources utilities, analytical decision-support mechanisms, and oversight tools. A functional classification might encompass:

Tools employed for data ingress and verification across all departments. Utilities focused on oversight and refinement of organizational workflows. Mechanisms for data aggregation and strategic inference. Modern business management solutions have undergone radical transformation in the last decade, driven by rapid technological advancement. This pace makes selecting optimal tools for a given business context increasingly complex. This complexity arises from continuous pressures to reduce expenditures, boost revenue, deeply understand client requirements, and consistently deliver products meeting those precise specifications. Within this evolving landscape, executive leadership should prioritize a strategic framework for tool acquisition and implementation rather than simply adopting the newest available technology. Over-reliance on unmodified tools often results in systemic instability. Therefore, enterprise management utilities must be selected meticulously and subsequently customized to align precisely with the organization's specific operational mandates, reversing the common practice of adapting organizational needs to the tool.

== Prominent Selections == In a 2013 assessment by Bain & Company regarding global utilization patterns of business tools, the results reflected regional requirements and prevailing market conditions. The leading ten tools identified were:

Strategic planning frameworks Customer relationship management (CRM) systems Employee morale surveys Competitive benchmarking analysis Balanced scorecard implementation Core competency identification Outsourcing strategies Organizational change management programs Supply chain optimization Mission and vision statement articulation Market segmentation analysis Total Quality Management (TQM)

== Enterprise Software Applications == A software suite or set of computer programs deployed by business personnel to execute diverse operational mandates is termed business software or an enterprise application. These applications serve to augment productivity metrics, quantify performance outcomes, and execute various corporate functions with precision. This domain originated with Management Information Systems (MIS), progressing into Enterprise Resource Planning (ERP). Subsequently, Customer Relationship Management (CRM) capabilities were integrated, leading to the current paradigm of cloud-based business management suites. While a clear link exists between IT investment and organizational success, two factors are paramount for value realization: the efficacy of the deployment process and the judicious selection and tailoring of the requisite technological assets.

== Tools Tailored for Small and Medium Enterprises (SMEs) == Tools specifically engineered for SMEs are vital as they furnish cost-effective mechanisms to conserve resources and expand operational capacity.