Notice: This page requires JavaScript to function properly.
Please enable JavaScript in your browser settings or update your browser.
Leer Setting Up AI Google Calendar Automation | Smarter Communication & Time Control
Agentic AI for Automating Daily Office Tasks
course content

Cursusinhoud

Agentic AI for Automating Daily Office Tasks

Agentic AI for Automating Daily Office Tasks

1. Meet Your AI Coworker
2. Smarter Communication & Time Control
3. Document Drafting, Editing & Filing

book
Setting Up AI Google Calendar Automation

Google Cloud Console Configuration

The Google Calendar API requires a dedicated project configuration within Google Cloud Console. This process mirrors the Gmail setup but requires specific Calendar API permissions.

Project Creation Steps
expand arrow
  1. Access Google Cloud Console through browser;
  2. Create new project with descriptive name (e.g., "gcalendar agent");
  3. Switch to newly created project once initialization completes.
OAuth Consent Screen Configuration
expand arrow

Application Registration:

  1. Enter application name (e.g., "calendar mcp");
  2. Specify authorized email address;
  3. Select "External Audience" for user type restrictions;
  4. Provide contact information using the same email;
  5. Accept User Data Policy requirements.
Calendar API Activation
expand arrow
  1. Navigate to APIs and ServicesLibrary;
  2. Search for "Calendar API";
  3. Select first result and enable API access;
  4. Verify API status shows as "Enabled".
Credentials Generation
expand arrow
  1. Access Credentials section in the APIs and Services;
  2. Create OAuth client ID;
  3. Select "Desktop Application" as application type;
  4. Download generated JSON credentials file;
  5. Temporarily store file on Desktop for easy access (optional).

Option 1: Use with npx (Recommended)

Config Block Addition
expand arrow
  • Copy configuration block:
    "google-calendar": {
      "command": "npx",
      "args": ["@cocal/google-calendar-mcp"],
      "env": {
        "GOOGLE_OAUTH_CREDENTIALS": "/path/to/your/gcp-oauth.keys.json"
      }
    }
  • Access Claude config file via Command/Ctrl + , → "Developer" → "Edit Config";
  • Open config file claude_desktop_config.json with text editor;
  • Add new config as next block after existing configurations and before the two last closing curly brackets;
  • Ensure proper JSON syntax with correct bracket closure and commas after each config block except the last one.
Path Configuration
expand arrow
  • Since in the previous step we stored the file on Desktop, but this file contains sensitive and important information, move it to a newly created folder in the /Documents/projects folder (or wherever you save previous servers).

Manual Method:

Open the /projects folder in your file explorer, create a new folder and name it (e.g., "google_calendar_mcp"), then move the file from Desktop to your new folder.

Terminal/Command Line Method:

  • Navigate to the folder with previous MCPs using the cd command (e.g., cd Documents/projects);
  • Create a new folder with the mkdir command (e.g., mkdir google_calendar_mcp && cd google_calendar_mcp) and move to this folder;
  • Move the file with OAuth keys to this folder (cp ~/Desktop/gsp-oauth-keys.json .);
  • Run pwd, copy the absolute path, and paste it into the Google Calendar config block.
Service Activation
expand arrow
  1. Restart Claude Desktop completely;
  2. Verify new server appears in available tools.

Option 2: Local Environment Setup

Directory Structure Creation
expand arrow

In your Terminal (Mac) or Command Line (Windows), start from the root directory (by default) and navigate to the folder where you will store all future AI Agent directories.

  • To access a folder, use the command cd folder_name, for example:
cd Documents

To create a new folder, use the command mkdir new_folder_name, for example:

mkdir projects

And navigate to this new folder with the cd command:

cd projects
Repository Download
expand arrow

Use the git clone link command to clone the GitHub repo:

git clone https://github.com/nspady/google-calendar-mcp.git

Move to the newly created repository by using the cd command:

cd google-calendar-mcp
Note
Note

If Git is not installed, download from the official Git website.

Credentials Integration
expand arrow

Now you need to move the file with credentials to the folder with the AI agent (google_calendar_mcp). You can do that manually by moving the file icon to the opened folder in the file explorer. Or use Terminal/Command Line and copy the file with the command cp path/to/file_name ., for example:

cp ~/Desktop/gsp-oauth.keys.json .

The dot (.) at the end specifies current directory as destination.

You can check if the JSON file was successfully moved to the folder using the ls command in the Terminal and find the file name in the list.

After moving the file, delete it from its original location (e.g., Desktop).

Package Installation
expand arrow

In the Terminal/Command Line use

npm install

This command downloads all required packages and dependencies.

Server Startup
expand arrow

Continue work in Terminal/Command Line and run

npm start

This command runs the default start script defined in the project's package.json file, which typically launches the application or server, in our case, it launches authentication flow.

Authentication Flow
expand arrow
  1. Browser window opens automatically;
  2. Select appropriate Google account;
  3. Grant calendar access permissions;
  4. Confirm "Authentication successful" message;
  5. Close browser window.

Claude Desktop Integration

Config Block Addition
expand arrow
  • Copy configuration block:
    "google-calendar": {
      "command": "node",
      "args": [
        "/path/to/build/index.js"
      ]
    }
  • Access Claude config file via Command/Ctrl + , → "Developer" → "Edit Config";
  • Open config file claude_desktop_config.json with text editor;
  • Add new config as next block after existing configurations and before the two last closing curly brackets;
  • Ensure proper JSON syntax with correct bracket closure and commas after each config block except the last one.
Path Configuration
expand arrow

In the Terminal/Command Line run

pwd

Copy the full directory path and insert before "/build" in config file.

Save configuration file Command/Ctrl + S.

Service Activation
expand arrow
  1. Restart Claude Desktop completely;
  2. Verify new server appears in available tools.
Was alles duidelijk?

Hoe kunnen we het verbeteren?

Bedankt voor je feedback!

Sectie 2. Hoofdstuk 2

Vraag AI

expand

Vraag AI

ChatGPT

Vraag wat u wilt of probeer een van de voorgestelde vragen om onze chat te starten.

course content

Cursusinhoud

Agentic AI for Automating Daily Office Tasks

Agentic AI for Automating Daily Office Tasks

1. Meet Your AI Coworker
2. Smarter Communication & Time Control
3. Document Drafting, Editing & Filing

book
Setting Up AI Google Calendar Automation

Google Cloud Console Configuration

The Google Calendar API requires a dedicated project configuration within Google Cloud Console. This process mirrors the Gmail setup but requires specific Calendar API permissions.

Project Creation Steps
expand arrow
  1. Access Google Cloud Console through browser;
  2. Create new project with descriptive name (e.g., "gcalendar agent");
  3. Switch to newly created project once initialization completes.
OAuth Consent Screen Configuration
expand arrow

Application Registration:

  1. Enter application name (e.g., "calendar mcp");
  2. Specify authorized email address;
  3. Select "External Audience" for user type restrictions;
  4. Provide contact information using the same email;
  5. Accept User Data Policy requirements.
Calendar API Activation
expand arrow
  1. Navigate to APIs and ServicesLibrary;
  2. Search for "Calendar API";
  3. Select first result and enable API access;
  4. Verify API status shows as "Enabled".
Credentials Generation
expand arrow
  1. Access Credentials section in the APIs and Services;
  2. Create OAuth client ID;
  3. Select "Desktop Application" as application type;
  4. Download generated JSON credentials file;
  5. Temporarily store file on Desktop for easy access (optional).

Option 1: Use with npx (Recommended)

Config Block Addition
expand arrow
  • Copy configuration block:
    "google-calendar": {
      "command": "npx",
      "args": ["@cocal/google-calendar-mcp"],
      "env": {
        "GOOGLE_OAUTH_CREDENTIALS": "/path/to/your/gcp-oauth.keys.json"
      }
    }
  • Access Claude config file via Command/Ctrl + , → "Developer" → "Edit Config";
  • Open config file claude_desktop_config.json with text editor;
  • Add new config as next block after existing configurations and before the two last closing curly brackets;
  • Ensure proper JSON syntax with correct bracket closure and commas after each config block except the last one.
Path Configuration
expand arrow
  • Since in the previous step we stored the file on Desktop, but this file contains sensitive and important information, move it to a newly created folder in the /Documents/projects folder (or wherever you save previous servers).

Manual Method:

Open the /projects folder in your file explorer, create a new folder and name it (e.g., "google_calendar_mcp"), then move the file from Desktop to your new folder.

Terminal/Command Line Method:

  • Navigate to the folder with previous MCPs using the cd command (e.g., cd Documents/projects);
  • Create a new folder with the mkdir command (e.g., mkdir google_calendar_mcp && cd google_calendar_mcp) and move to this folder;
  • Move the file with OAuth keys to this folder (cp ~/Desktop/gsp-oauth-keys.json .);
  • Run pwd, copy the absolute path, and paste it into the Google Calendar config block.
Service Activation
expand arrow
  1. Restart Claude Desktop completely;
  2. Verify new server appears in available tools.

Option 2: Local Environment Setup

Directory Structure Creation
expand arrow

In your Terminal (Mac) or Command Line (Windows), start from the root directory (by default) and navigate to the folder where you will store all future AI Agent directories.

  • To access a folder, use the command cd folder_name, for example:
cd Documents

To create a new folder, use the command mkdir new_folder_name, for example:

mkdir projects

And navigate to this new folder with the cd command:

cd projects
Repository Download
expand arrow

Use the git clone link command to clone the GitHub repo:

git clone https://github.com/nspady/google-calendar-mcp.git

Move to the newly created repository by using the cd command:

cd google-calendar-mcp
Note
Note

If Git is not installed, download from the official Git website.

Credentials Integration
expand arrow

Now you need to move the file with credentials to the folder with the AI agent (google_calendar_mcp). You can do that manually by moving the file icon to the opened folder in the file explorer. Or use Terminal/Command Line and copy the file with the command cp path/to/file_name ., for example:

cp ~/Desktop/gsp-oauth.keys.json .

The dot (.) at the end specifies current directory as destination.

You can check if the JSON file was successfully moved to the folder using the ls command in the Terminal and find the file name in the list.

After moving the file, delete it from its original location (e.g., Desktop).

Package Installation
expand arrow

In the Terminal/Command Line use

npm install

This command downloads all required packages and dependencies.

Server Startup
expand arrow

Continue work in Terminal/Command Line and run

npm start

This command runs the default start script defined in the project's package.json file, which typically launches the application or server, in our case, it launches authentication flow.

Authentication Flow
expand arrow
  1. Browser window opens automatically;
  2. Select appropriate Google account;
  3. Grant calendar access permissions;
  4. Confirm "Authentication successful" message;
  5. Close browser window.

Claude Desktop Integration

Config Block Addition
expand arrow
  • Copy configuration block:
    "google-calendar": {
      "command": "node",
      "args": [
        "/path/to/build/index.js"
      ]
    }
  • Access Claude config file via Command/Ctrl + , → "Developer" → "Edit Config";
  • Open config file claude_desktop_config.json with text editor;
  • Add new config as next block after existing configurations and before the two last closing curly brackets;
  • Ensure proper JSON syntax with correct bracket closure and commas after each config block except the last one.
Path Configuration
expand arrow

In the Terminal/Command Line run

pwd

Copy the full directory path and insert before "/build" in config file.

Save configuration file Command/Ctrl + S.

Service Activation
expand arrow
  1. Restart Claude Desktop completely;
  2. Verify new server appears in available tools.
Was alles duidelijk?

Hoe kunnen we het verbeteren?

Bedankt voor je feedback!

Sectie 2. Hoofdstuk 2
some-alt