This MCP server exposes a comprehensive integration with Google services, including Calendar, Docs, Sheets, Slides, Drive, Gmail, Contacts (People API), YouTube, Tasks (as a Keep-like alternative), Forms, Chat, and Meet. After starting the server, you authenticate with Google via the google_auth tool to grant access to your Google account. Once authenticated, you can enumerate and invoke a wide set of tools to manage calendars, emails, documents, and more directly through the MCP interface. The tools are organized by service (Calendar, Gmail, Drive, Docs, Sheets, Slides, YouTube, Forms, Chat, Meet) and include both read-only operations (e.g., list, get) and write capabilities (e.g., create, update, delete). The Google Tasks integration acts as a Keep-like substitute, enabling note-like task lists with descriptions.

Prerequisites:

• Node.js (recommended LTS) installed on your system
• PNPM or npm for dependency installation
• Access to a Google Cloud project with OAuth credentials (credentials.json)

Install and build:

1. Clone the repository: git clone https://github.com/your-org/google-mcp.git cd google-mcp

2. Install dependencies: pnpm install

   or: npm install

3. Build the project (if using TypeScript/tsx entry): pnpm build

   or: npm run build

4. Prepare credentials:

   • Go through Google Cloud setup to enable APIs and obtain credentials.json
   • Place credentials.json at the location expected by your environment (e.g., ~/.config/google-mcp/credentials.json or as configured in the mcp_config env)

5. Run the server (example using the provided Node setup): node dist/index.js

   or via your preferred runner configuration in the MCP settings

6. Alternatively, for development or testing, you can run directly with npx/tsx as shown in the README usage examples.

Tips and common considerations:

• Ensure all required Google APIs are enabled in your Cloud project before first use.
• Set the credentials.json path correctly and keep it secure; the server stores tokens locally per platform.
• Use the google_auth tool to initiate OAuth flow; tokens will be refreshed automatically when needed.
• If you modify the server code, re-run the build step to ensure dist/index.js is up to date.
• When configuring mcpServers in your MCP settings, choose a command runner that matches your deployment environment (node with built dist, or npx/tsx for on-the-fly TS execution).
• For production deployments, consider defining environment variables for credentials path and any API scopes you intend to restrict.