Skip to main content
Book a demo

Connect Google Calendar to VS Code

Give VS Code governed access to Google Calendar’s 13 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo VS Code setup guide

Set up

Add Google Calendar to VS Code in four steps

Admins approve the server once. Everyone in VS Code then gets it through the same governed connection.

  1. 1

    Approve Google Calendar in Runlayer

    Add Google Calendar from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect VS Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Google Calendar’s 13 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).

    VS Code setup guide
  3. 3

    Sign in to Google Calendar

    Sign in the way Google Calendar requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Google Calendar from VS Code

    Google Calendar’s approved tools appear in VS Code. Every call is checked against policy and recorded.

Tools

13 Google Calendar tools in VS Code

Runlayer policy decides which of these VS Code users can call. 4 read data only and 2 can change or delete data.

  • Create Calendar

    Create a new calendar.

  • Create event

    Create a new event in your Google Calendar with detailed options including attendees, location, reminders, and recurrence rules.

  • Delete Calendar

    Delete a secondary calendar.

  • Delete event

    Delete an event from your calendar.

  • Get event

    Get detailed information about a specific calendar event including title, description, time, location, attendees, and recurrence rules.

  • Get free busy

    Check free/busy information for calendars within a time range.

  • List calendars

    List all calendars accessible to the authenticated user.

  • List events

    List events from your Google Calendar.

See all 13 Google Calendar tools

Control

What Runlayer can see and stop in VS Code

Some controls apply to every client at the gateway. Others depend on what VS Code exposes to Runlayer.

  • Gateway policy (available)

    Every Google Calendar call from VS Code passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, VS Code as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before VS Code runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before VS Code’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.

Frequently asked questions

Connect more

Find another combination