iflow-mcp_mcp-gsuite 0.4.1__tar.gz

iflow_mcp_mcp_gsuite-0.4.1/.gitignore

@@ -0,0 +1,15 @@
+# Python-generated files
+__pycache__/
+*.py[oc]
+build/
+dist/
+wheels/
+*.egg-info
+
+# Virtual environments
+.venv
+.env
+.gauth.json
+oauth2creds.json
+.accounts.json
+.oauth2.*.json

iflow_mcp_mcp_gsuite-0.4.1/.python-version

@@ -0,0 +1 @@
+3.13

iflow_mcp_mcp_gsuite-0.4.1/Dockerfile

@@ -0,0 +1,38 @@
+# Generated by https://smithery.ai. See: https://smithery.ai/docs/config#dockerfile
+# Use a Python image with uv pre-installed
+FROM ghcr.io/astral-sh/uv:python3.13-bookworm-slim AS uv
+
+# Set the working directory
+WORKDIR /app
+
+# Copy necessary configuration files
+COPY . .
+
+# Enable bytecode compilation
+ENV UV_COMPILE_BYTECODE=1
+
+# Use the copy link mode for mount points
+ENV UV_LINK_MODE=copy
+
+# Sync dependencies and build the project
+RUN --mount=type=cache,target=/root/.cache/uv     --mount=type=bind,source=uv.lock,target=uv.lock     --mount=type=bind,source=pyproject.toml,target=pyproject.toml     uv sync --frozen --no-install-project --no-dev --no-editable
+
+# Install the project
+RUN --mount=type=cache,target=/root/.cache/uv     uv sync --frozen --no-dev --no-editable
+
+# Final stage: running the application
+FROM python:3.13-slim-bookworm
+
+WORKDIR /app
+
+COPY --from=uv /root/.local /root/.local
+COPY --from=uv --chown=app:app /app/.venv /app/.venv
+
+# Place executables in the environment at the front of the path
+ENV PATH="/app/.venv/bin:$PATH"
+
+# Expose necessary ports
+EXPOSE 4100
+
+# Specify the entrypoint command
+ENTRYPOINT ["uv", "run", "mcp-gsuite"]

iflow_mcp_mcp_gsuite-0.4.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Markus Pfundstein
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

iflow_mcp_mcp_gsuite-0.4.1/PKG-INFO

@@ -0,0 +1,272 @@
+Metadata-Version: 2.4
+Name: iflow-mcp_mcp-gsuite
+Version: 0.4.1
+Summary: MCP Server to connect to Google G-Suite
+Author-email: Markus Pfundstein <markus@life-electronic.nl>
+License-File: LICENSE
+Requires-Python: >=3.13
+Requires-Dist: beautifulsoup4>=4.12.3
+Requires-Dist: google-api-python-client>=2.154.0
+Requires-Dist: httplib2>=0.22.0
+Requires-Dist: mcp>=1.3.0
+Requires-Dist: oauth2client==4.1.3
+Requires-Dist: python-dotenv>=1.0.1
+Requires-Dist: pytz>=2024.2
+Requires-Dist: requests>=2.32.3
+Description-Content-Type: text/markdown
+
+# mcp-gsuite MCP server
+
+[![smithery badge](https://smithery.ai/badge/mcp-gsuite)](https://smithery.ai/server/mcp-gsuite)
+MCP server to interact with Google products.
+
+## Example prompts
+
+Right now, this MCP server supports Gmail and Calendar integration with the following capabilities:
+
+1. General
+* Multiple google accounts
+
+2. Gmail
+* Get your Gmail user information
+* Query emails with flexible search (e.g., unread, from specific senders, date ranges, with attachments)
+* Retrieve complete email content by ID
+* Create new draft emails with recipients, subject, body and CC options
+* Delete draft emails
+* Reply to existing emails (can either send immediately or save as draft)
+* Retrieve multiple emails at once by their IDs.
+* Save multiple attachments from emails to your local system.
+
+3. Calendar
+* Manage multiple calendars
+* Get calendar events within specified time ranges
+* Create calendar events with:
+  + Title, start/end times
+  + Optional location and description
+  + Optional attendees
+  + Custom timezone support
+  + Notification preferences
+* Delete calendar events
+
+Example prompts you can try:
+
+* Retrieve my latest unread messages
+* Search my emails from the Scrum Master
+* Retrieve all emails from accounting
+* Take the email about ABC and summarize it
+* Write a nice response to Alice's last email and upload a draft.
+* Reply to Bob's email with a Thank you note. Store it as draft
+
+* What do I have on my agenda tomorrow?
+* Check my private account's Family agenda for next week
+* I need to plan an event with Tim for 2hrs next week. Suggest some time slots.
+
+## Quickstart
+
+### Install
+
+### Installing via Smithery
+
+To install mcp-gsuite for Claude Desktop automatically via [Smithery](https://smithery.ai/server/mcp-gsuite):
+
+```bash
+npx -y @smithery/cli install mcp-gsuite --client claude
+```
+
+#### Oauth 2
+
+Google Workspace (G Suite) APIs require OAuth2 authorization. Follow these steps to set up authentication:
+
+1. Create OAuth2 Credentials:
+   - Go to the [Google Cloud Console](https://console.cloud.google.com/)
+   - Create a new project or select an existing one
+   - Enable the Gmail API and Google Calendar API for your project
+   - Go to "Credentials" → "Create Credentials" → "OAuth client ID"
+   - Select "Desktop app" or "Web application" as the application type
+   - Configure the OAuth consent screen with required information
+   - Add authorized redirect URIs (include `http://localhost:4100/code` for local development)
+
+2. Required OAuth2 Scopes:
+   
+
+```json
+   [
+     "openid",
+     "https://mail.google.com/",
+     "https://www.googleapis.com/auth/calendar",
+     "https://www.googleapis.com/auth/userinfo.email"
+   ]
+```
+
+3. Then create a `.gauth.json` in your working directory with client
+
+```json
+{
+    "web": {
+        "client_id": "$your_client_id",
+        "client_secret": "$your_client_secret",
+        "redirect_uris": ["http://localhost:4100/code"],
+        "auth_uri": "https://accounts.google.com/o/oauth2/auth",
+        "token_uri": "https://oauth2.googleapis.com/token"
+    }
+}
+```
+
+4. Create a `.accounts.json` file with account information
+
+```json
+{
+    "accounts": [
+        {
+            "email": "alice@bob.com",
+            "account_type": "personal",
+            "extra_info": "Additional info that you want to tell Claude: E.g. 'Contains Family Calendar'"
+        }
+    ]
+}
+```
+
+You can specifiy multiple accounts. Make sure they have access in your Google Auth app. The `extra_info` field is especially interesting as you can add info here that you want to tell the AI about the account (e.g. whether it has a specific agenda)
+
+Note: When you first execute one of the tools for a specific account, a browser will open, redirect you to Google and ask for your credentials, scope, etc. After a successful login, it stores the credentials in a local file called `.oauth.{email}.json` . Once you are authorized, the refresh token will be used.
+
+#### Claude Desktop
+
+On MacOS: `~/Library/Application\ Support/Claude/claude_desktop_config.json`
+
+On Windows: `%APPDATA%/Claude/claude_desktop_config.json`
+
+<details>
+  <summary>Development/Unpublished Servers Configuration</summary>
+  
+
+```json
+{
+  "mcpServers": {
+    "mcp-gsuite": {
+      "command": "uv",
+      "args": [
+        "--directory",
+        "<dir_to>/mcp-gsuite",
+        "run",
+        "mcp-gsuite"
+      ]
+    }
+  }
+}
+```
+
+
+Note: You can also use the `uv run mcp-gsuite --accounts-file /path/to/custom/.accounts.json` to specify a different accounts file or `--credentials-dir /path/to/custom/credentials` to specify a different credentials directory.
+
+```json
+{
+  "mcpServers": {
+    "mcp-gsuite": {
+      "command": "uv",
+      "args": [
+        "--directory",
+        "<dir_to>/mcp-gsuite",
+        "run",
+        "mcp-gsuite",
+        "--accounts-file",
+        "/path/to/custom/.accounts.json",
+        "--credentials-dir",
+        "/path/to/custom/credentials"
+      ]
+    }
+  }
+}
+```
+
+</details>
+
+<details>
+  <summary>Published Servers Configuration</summary>
+  
+
+```json
+{
+  "mcpServers": {
+    "mcp-gsuite": {
+      "command": "uvx",
+      "args": [
+        "mcp-gsuite",
+        "--accounts-file",
+        "/path/to/custom/.accounts.json",
+        "--credentials-dir",
+        "/path/to/custom/credentials"
+      ]
+    }
+  }
+}
+```
+
+</details>
+
+### Configuration Options
+
+The MCP server can be configured with several command-line options to specify custom paths for authentication and account information:
+
+* `--gauth-file`: Specifies the path to the `.gauth.json` file containing OAuth2 client configuration. Default is `./.gauth.json`.
+* `--accounts-file`: Specifies the path to the `.accounts.json` file containing information about the Google accounts. Default is `./.accounts.json`.
+* `--credentials-dir`: Specifies the directory where OAuth credentials are stored after successful authentication. Default is the current working directory with a subdirectory for each account as `.oauth.{email}.json`.
+
+These options allow for flexibility in managing different environments or multiple sets of credentials and accounts, especially useful in development and testing scenarios.
+
+Example usage:
+
+```bash
+uv run mcp-gsuite --gauth-file /path/to/custom/.gauth.json --accounts-file /path/to/custom/.accounts.json --credentials-dir /path/to/custom/credentials
+```
+
+This configuration is particularly useful when you have multiple instances of the server running with different configurations or when deploying to environments where the default paths are not suitable.
+
+## Development
+
+### Building and Publishing
+
+To prepare the package for distribution:
+
+1. Sync dependencies and update lockfile:
+
+```bash
+uv sync
+```
+
+2. Build package distributions:
+
+```bash
+uv build
+```
+
+This will create source and wheel distributions in the `dist/` directory.
+
+3. Publish to PyPI:
+
+```bash
+uv publish
+```
+
+Note: You'll need to set PyPI credentials via environment variables or command flags:
+* Token: `--token` or `UV_PUBLISH_TOKEN`
+* Or username/password: `--username`/`UV_PUBLISH_USERNAME` and `--password`/`UV_PUBLISH_PASSWORD`
+
+### Debugging
+
+Since MCP servers run over stdio, debugging can be challenging. For the best debugging
+experience, we strongly recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector).
+
+You can launch the MCP Inspector via [ `npm` ](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm) with this command:
+
+```bash
+npx @modelcontextprotocol/inspector uv --directory /path/to/mcp-gsuite run mcp-gsuite
+```
+
+Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.
+
+You can also watch the server logs with this command:
+
+```bash
+tail -n 20 -f ~/Library/Logs/Claude/mcp-server-mcp-gsuite.log
+```

iflow_mcp_mcp_gsuite-0.4.1/README.md

@@ -0,0 +1,255 @@
+# mcp-gsuite MCP server
+
+[![smithery badge](https://smithery.ai/badge/mcp-gsuite)](https://smithery.ai/server/mcp-gsuite)
+MCP server to interact with Google products.
+
+## Example prompts
+
+Right now, this MCP server supports Gmail and Calendar integration with the following capabilities:
+
+1. General
+* Multiple google accounts
+
+2. Gmail
+* Get your Gmail user information
+* Query emails with flexible search (e.g., unread, from specific senders, date ranges, with attachments)
+* Retrieve complete email content by ID
+* Create new draft emails with recipients, subject, body and CC options
+* Delete draft emails
+* Reply to existing emails (can either send immediately or save as draft)
+* Retrieve multiple emails at once by their IDs.
+* Save multiple attachments from emails to your local system.
+
+3. Calendar
+* Manage multiple calendars
+* Get calendar events within specified time ranges
+* Create calendar events with:
+  + Title, start/end times
+  + Optional location and description
+  + Optional attendees
+  + Custom timezone support
+  + Notification preferences
+* Delete calendar events
+
+Example prompts you can try:
+
+* Retrieve my latest unread messages
+* Search my emails from the Scrum Master
+* Retrieve all emails from accounting
+* Take the email about ABC and summarize it
+* Write a nice response to Alice's last email and upload a draft.
+* Reply to Bob's email with a Thank you note. Store it as draft
+
+* What do I have on my agenda tomorrow?
+* Check my private account's Family agenda for next week
+* I need to plan an event with Tim for 2hrs next week. Suggest some time slots.
+
+## Quickstart
+
+### Install
+
+### Installing via Smithery
+
+To install mcp-gsuite for Claude Desktop automatically via [Smithery](https://smithery.ai/server/mcp-gsuite):
+
+```bash
+npx -y @smithery/cli install mcp-gsuite --client claude
+```
+
+#### Oauth 2
+
+Google Workspace (G Suite) APIs require OAuth2 authorization. Follow these steps to set up authentication:
+
+1. Create OAuth2 Credentials:
+   - Go to the [Google Cloud Console](https://console.cloud.google.com/)
+   - Create a new project or select an existing one
+   - Enable the Gmail API and Google Calendar API for your project
+   - Go to "Credentials" → "Create Credentials" → "OAuth client ID"
+   - Select "Desktop app" or "Web application" as the application type
+   - Configure the OAuth consent screen with required information
+   - Add authorized redirect URIs (include `http://localhost:4100/code` for local development)
+
+2. Required OAuth2 Scopes:
+   
+
+```json
+   [
+     "openid",
+     "https://mail.google.com/",
+     "https://www.googleapis.com/auth/calendar",
+     "https://www.googleapis.com/auth/userinfo.email"
+   ]
+```
+
+3. Then create a `.gauth.json` in your working directory with client
+
+```json
+{
+    "web": {
+        "client_id": "$your_client_id",
+        "client_secret": "$your_client_secret",
+        "redirect_uris": ["http://localhost:4100/code"],
+        "auth_uri": "https://accounts.google.com/o/oauth2/auth",
+        "token_uri": "https://oauth2.googleapis.com/token"
+    }
+}
+```
+
+4. Create a `.accounts.json` file with account information
+
+```json
+{
+    "accounts": [
+        {
+            "email": "alice@bob.com",
+            "account_type": "personal",
+            "extra_info": "Additional info that you want to tell Claude: E.g. 'Contains Family Calendar'"
+        }
+    ]
+}
+```
+
+You can specifiy multiple accounts. Make sure they have access in your Google Auth app. The `extra_info` field is especially interesting as you can add info here that you want to tell the AI about the account (e.g. whether it has a specific agenda)
+
+Note: When you first execute one of the tools for a specific account, a browser will open, redirect you to Google and ask for your credentials, scope, etc. After a successful login, it stores the credentials in a local file called `.oauth.{email}.json` . Once you are authorized, the refresh token will be used.
+
+#### Claude Desktop
+
+On MacOS: `~/Library/Application\ Support/Claude/claude_desktop_config.json`
+
+On Windows: `%APPDATA%/Claude/claude_desktop_config.json`
+
+<details>
+  <summary>Development/Unpublished Servers Configuration</summary>
+  
+
+```json
+{
+  "mcpServers": {
+    "mcp-gsuite": {
+      "command": "uv",
+      "args": [
+        "--directory",
+        "<dir_to>/mcp-gsuite",
+        "run",
+        "mcp-gsuite"
+      ]
+    }
+  }
+}
+```
+
+
+Note: You can also use the `uv run mcp-gsuite --accounts-file /path/to/custom/.accounts.json` to specify a different accounts file or `--credentials-dir /path/to/custom/credentials` to specify a different credentials directory.
+
+```json
+{
+  "mcpServers": {
+    "mcp-gsuite": {
+      "command": "uv",
+      "args": [
+        "--directory",
+        "<dir_to>/mcp-gsuite",
+        "run",
+        "mcp-gsuite",
+        "--accounts-file",
+        "/path/to/custom/.accounts.json",
+        "--credentials-dir",
+        "/path/to/custom/credentials"
+      ]
+    }
+  }
+}
+```
+
+</details>
+
+<details>
+  <summary>Published Servers Configuration</summary>
+  
+
+```json
+{
+  "mcpServers": {
+    "mcp-gsuite": {
+      "command": "uvx",
+      "args": [
+        "mcp-gsuite",
+        "--accounts-file",
+        "/path/to/custom/.accounts.json",
+        "--credentials-dir",
+        "/path/to/custom/credentials"
+      ]
+    }
+  }
+}
+```
+
+</details>
+
+### Configuration Options
+
+The MCP server can be configured with several command-line options to specify custom paths for authentication and account information:
+
+* `--gauth-file`: Specifies the path to the `.gauth.json` file containing OAuth2 client configuration. Default is `./.gauth.json`.
+* `--accounts-file`: Specifies the path to the `.accounts.json` file containing information about the Google accounts. Default is `./.accounts.json`.
+* `--credentials-dir`: Specifies the directory where OAuth credentials are stored after successful authentication. Default is the current working directory with a subdirectory for each account as `.oauth.{email}.json`.
+
+These options allow for flexibility in managing different environments or multiple sets of credentials and accounts, especially useful in development and testing scenarios.
+
+Example usage:
+
+```bash
+uv run mcp-gsuite --gauth-file /path/to/custom/.gauth.json --accounts-file /path/to/custom/.accounts.json --credentials-dir /path/to/custom/credentials
+```
+
+This configuration is particularly useful when you have multiple instances of the server running with different configurations or when deploying to environments where the default paths are not suitable.
+
+## Development
+
+### Building and Publishing
+
+To prepare the package for distribution:
+
+1. Sync dependencies and update lockfile:
+
+```bash
+uv sync
+```
+
+2. Build package distributions:
+
+```bash
+uv build
+```
+
+This will create source and wheel distributions in the `dist/` directory.
+
+3. Publish to PyPI:
+
+```bash
+uv publish
+```
+
+Note: You'll need to set PyPI credentials via environment variables or command flags:
+* Token: `--token` or `UV_PUBLISH_TOKEN`
+* Or username/password: `--username`/`UV_PUBLISH_USERNAME` and `--password`/`UV_PUBLISH_PASSWORD`
+
+### Debugging
+
+Since MCP servers run over stdio, debugging can be challenging. For the best debugging
+experience, we strongly recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector).
+
+You can launch the MCP Inspector via [ `npm` ](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm) with this command:
+
+```bash
+npx @modelcontextprotocol/inspector uv --directory /path/to/mcp-gsuite run mcp-gsuite
+```
+
+Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.
+
+You can also watch the server logs with this command:
+
+```bash
+tail -n 20 -f ~/Library/Logs/Claude/mcp-server-mcp-gsuite.log
+```