Google-Mail Universal MCP Server
This repository contains an implementation of an Google-Mail Universal MCP (Model Context Protocol) server. It provides a standardized interface for interacting with Google-Mail's tools and services through a unified API.
The server is built using the Universal MCP framework.
This implementation follows the MCP specification, ensuring compatibility with other MCP-compliant services and tools.
Usage
You can start using Google-Mail directly from agentr.dev. Visit agentr.dev/apps and enable Google-Mail.
If you have not used universal mcp before follow the setup instructions at agentr.dev/quickstart
Available Tools
The full list of available tools is at ./src/universal_mcp_google_mail/README.md
Local Development
📋 Prerequisites
Ensure you have the following before you begin:
- Python 3.11+ (recommended)
- uv (install globally with
pip install uv)
🛠️ Setup Instructions
Follow the steps below to set up your development environment:
-
Sync Project Dependencies
uv syncThis installs all dependencies from
pyproject.tomlinto a local virtual environment (.venv). -
Activate the Virtual Environment
For Linux/macOS:
source .venv/bin/activate
For Windows (PowerShell):
.venv\Scripts\Activate
-
Start the MCP Inspector
mcp dev src/universal_mcp_google_mail/server.py
This will start the MCP inspector. Make note of the address and port shown in the console output.
-
Install the Application
mcp install src/universal_mcp_google_mail/server.py
📁 Project Structure
.
├── src/
│ └── universal_mcp_google_mail/
│ ├── __init__.py # Package initializer
│ ├── server.py # Server entry point
│ ├── app.py # Application tools
│ └── README.md # List of application tools
├── tests/ # Test suite
├── .env # Environment variables for local development
├── pyproject.toml # Project configuration
└── README.md # This file
📄 License
This project is licensed under the MIT License.
Generated with MCP CLI — Happy coding! 🚀
1 maintainer
Metadata
1 maintainer
Release files for universal-mcp-google-mail 0.1.21
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| universal_mcp_google_mail-0.1.21.tar.gz | 142.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| universal_mcp_google_mail-0.1.21-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 155.0 kB
Release files / universal_mcp_google_mail-0.1.21.tar.gz
| Download URL | universal_mcp_google_mail-0.1.21.tar.gz |
|---|---|
| Size | 142.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
69c54bf2716c3361d7f1498d4f888cb932bcb69564ebe07804a99cfd3b3e6f1d
|
|
BLAKE2b-256 checksum How to use checksums |
b2148c7832b838b9f83fc084d52555f74f4d8e926e5c030b13b0c8cb2ca88275
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.19
|
Release files / universal_mcp_google_mail-0.1.21-py3-none-any.whl
| Download URL | universal_mcp_google_mail-0.1.21-py3-none-any.whl |
|---|---|
| Size | 12.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
084bf4101668ede23bcc44d29c0b23caab478871780b952d55af7e6da5676446
|
|
BLAKE2b-256 checksum How to use checksums |
a8e0b455667e7d3af0c041bef3d1f07fce7c7b59671fdf3f8fb5c074a6936946
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.7.19
|
Security for universal-mcp-google-mail 0.1.21
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
