Back to Browse

Calendarport MCP Server

Developer ToolsModerate5.7MCP RegistryLocal
Free

Server data from the Official MCP Registry

Google Calendar calendars, events and free-busy checks, as MCP tools.

About

Google Calendar calendars, events and free-busy checks, as MCP tools.

Security Report

5.7
Moderate5.7Moderate Risk

calendarport is a clean-room Google Calendar MCP server that requires a GOOGLE_ACCESS_TOKEN from the environment and sends it only as a Bearer header to the Google Calendar API. The code shows no exfiltration, shell execution, or hardcoded secrets, and its permissions (outbound HTTP and env var reads) match its stated purpose. The only notable items are low-severity: the CALENDAR_API_URL override could redirect the token if an attacker controls the environment, and upstream error text is returned to the client. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

8 files analyzed · 8 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

GOOGLE_ACCESS_TOKENRequired

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-cloudcorprecords-calendarport": {
      "env": {
        "GOOGLE_ACCESS_TOKEN": "your-google-access-token-here"
      },
      "args": [
        "-y",
        "@reneturcios/calendarport"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

calendarport

Google Calendar calendars and events as MCP tools, talking to the Google Calendar API. calendarport is a clean-room rebuild of the core surface of the Google Calendar reference MCP server, under a new name: fresh code written from the public Calendar API documentation, no copied branding.

Tools (core subset, 10)

list_calendars, get_calendar, create_calendar, list_events, get_event, create_event, update_event, delete_event, quick_add_event, check_free_busy.

Calendar ACL and rules, event move/import/instances/watch, attachments, conference data, settings and colors from the wider Calendar surface are not in this subset. calendar_id is optional on event tools and defaults to primary.

Setup

Set a Google OAuth access token:

export GOOGLE_ACCESS_TOKEN=ya29....

Optionally override the API base with CALENDAR_API_URL (default https://www.googleapis.com/calendar/v3). Without the token, every tool call fails with an error naming the missing variable.

CLI

npx @reneturcios/calendarport list_events '{"time_min":"2026-10-27T00:00:00Z"}'
npx @reneturcios/calendarport mcp        # stdio MCP server

Each tool name is a subcommand taking one JSON object argument.

MCP client config

{
  "mcpServers": {
    "calendarport": {
      "command": "npx",
      "args": ["-y", "@reneturcios/calendarport", "mcp"],
      "env": { "GOOGLE_ACCESS_TOKEN": "ya29...." }
    }
  }
}

Docker

docker run -i -e GOOGLE_ACCESS_TOKEN ghcr.io/cloudcorprecords/calendarport

Development

npm install
npm run build
npm test

License

MIT

Reviews

No reviews yet

Be the first to review this server!