mcpField
C
calendarport

calendarport

Local
github.com/CloudCorpRecordsProductivity0Updated 2w ago
Repository

About calendarport

calendarport exposes Google Calendar calendars, events, and free-busy checks as tools for agents that need calendar operations. It covers core calendar and event actions through the Google Calendar API.

Key features

  1. 01List and retrieve calendars
  2. 02Create calendars and events
  3. 03Find, update, and delete events
  4. 04Quick-add an event
  5. 05Check free-busy availability

Use cases

  1. 01Look up events within a time range
  2. 02Create or modify calendar events
  3. 03Check participant availability

MCP support

The MCP server provides clients with 10 Google Calendar tools for managing calendars and events, quick-adding events, and checking free-busy status. Calls require a Google OAuth access token.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
  "mcpServers": {
    "cloudcorprecords-calendarport": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/calendarport"
      ]
    }
  }
}
Run commandnpx -y @reneturcios/calendarport

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@reneturcios/calendarport0.1.0
ocighcr.io/cloudcorprecords/calendarport:0.1.0

Tools

10

Saved tool list · updated 1w ago

This tool takes no parameters.

Details

From the project 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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.