Gmail MCP Agent

MCP办公协作

提供方 brandononchain

办公协作 stdio · 本地进程 Token 社区 / 第三方
查看接入方式

一个企业级的潜在客户培育系统,通过Gmail自动化外联活动,包括智能跟进、响应跟踪和24/7运行。

一句话选型结论

按资料字段整理

Gmail MCP Agent 属于办公协作类 MCP 服务器,stdio · 本地进程,Token,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类办公协作 传输方式stdio · 本地进程 鉴权Token 部署方式本地部署
GitHub 星标 0 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

办公协作
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

适用场景

邮件营销Python本地部署自动化潜在客户管理Gmail集成企业级

安装与配置

stdio · 本地进程 Token
客户端在本机拉起子进程,数据不出本机
pip install -r requirements.txt

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
日程与消息

查日程、发消息、约会议。

表单与审批

填表单、走审批流。

团队协作

同步任务、汇总进展。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好Token对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在办公协作场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Gmail MCP Agent当前 未标注 stdio · 本地进程 本地部署 有 2026-05-17
CowAgent 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Karakeep MCP 未标注 未标注 未标注 无 2026-05-17
agentscope 未标注 stdio · 本地进程 本地部署 有 2026-04-11
note-gen 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Everywhere 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

办公协作
字段来自项目仓库与公开索引,中文说明由本站标注
提供方brandononchain上游标注的维护方 brandononchain
分类办公协作本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式Token远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

8.0 KB
来自项目仓库与上游目录的原文,未做删改

🤖 Gmail MCP Agent - 24/7 Lead Nurturing System

A comprehensive, enterprise-grade lead nurturing system that automates Gmail outreach campaigns with intelligent follow-ups, response tracking, and 24/7 operation via MCP (Model Context Protocol) server.

🚀 Features

✅ Automated Lead Nurturing

  • 24/7 Operation - Runs continuously with Docker containerization
  • Intelligent Follow-ups - Automatic sequences at 3 days and 7 days
  • Response Tracking - Monitors Gmail for replies and categorizes them
  • Lead Scoring - Tracks engagement and interest levels
  • Smart Responses - Automatically responds to interested leads

📊 MCP Server Architecture

  • Remote Control - Control system via MCP protocol
  • Real-time Monitoring - Live status and performance tracking
  • Docker Deployment - Production-ready containerization
  • Health Checks - Automatic recovery and error handling
  • Scalable Design - Ready for enterprise use

🎯 Email Campaign Management

  • CSV-based Lead Lists - Easy contact management
  • Template System - Jinja2-powered email personalization
  • Rate Limiting - Respects Gmail API quotas
  • Resume Capability - Continue from where you left off
  • Comprehensive Logging - Complete audit trail

📁 Project Structure```

├── send_from_csv.py # Main Gmail sender script
├── lead_nurturer.py # Automated nurturing system
├── mcp_server.py # 24/7 MCP server
├── mcp_client.py # Control interface
├── lead_dashboard.py # Monitoring dashboard
├── run_nurturing.py # Automation runner
├── contacts.csv # Lead database (96 dental practices)
├── body.txt # Email template
├── credentials.json # Gmail API credentials
├── nurturing_config.json # System configuration
├── gmail_sync_state.json # Gmail incremental sync state (auto-created)
├── requirements.txt # Python dependencies
├── Dockerfile # Container configuration
├── docker-compose.yml # Deployment setup
├── deploy.sh # One-click deployment
└── DEPLOYMENT_GUIDE.md # Complete setup guide


## 🛠️ Quick Start

### 1. **Clone and Setup**```bash
git clone https://github.com/brandononchain/GMAIL-MCP-Agent.git
cd GMAIL-MCP-Agent
pip install -r requirements.txt

2. Configure Gmail API

  • Get OAuth2 credentials from Google Cloud Console
  • Save as credentials.json
  • Update sender email in nurturing_config.json

3. Deploy 24/7 System```bash

Docker deployment (recommended)

./deploy.sh

Or manual deployment

docker-compose up -d


### 4. **Start Nurturing**```bash
# Using MCP client
python mcp_client.py start 4

# Or direct execution
python run_nurturing.py

🎮 Control Commands

MCP Client Interface```bash

Start nurturing system (every 4 hours)

python mcp_client.py start 4

Check system status

python mcp_client.py status

Get lead report

python mcp_client.py report

Send test email

python mcp_client.py test your-email@example.com

View recent logs

python mcp_client.py logs 100

Stop the system

python mcp_client.py stop


### Direct Scripts```bash
# Run single nurturing cycle
python lead_nurturer.py

# View lead dashboard
python lead_dashboard.py

# Send emails from CSV
python send_from_csv.py contacts.csv --body_file body.txt

📊 Current Campaign

Dental Practice Outreach

  • Target: 96 dental practices in Chicago
  • Message: AI lead follow-up system for dental practices
  • Follow-up Schedule: 3 days and 7 days after initial contact
  • Expected Results: 20-30% response rate, 10-15% conversion

Email Template```

Hi {{first_name}},

Did you know many dental practices lose 20–30% of new patient inquiries because follow-ups slip through the cracks?

We've built an AI agent that automatically follows up with every lead via SMS/email and books them straight into your calendar.

Clients typically see 5–9 extra appointments in the first 30 days.

Have time for 10-min demo call this week?

Thank you,
Brandon
Quantra Labs


## 🔧 Configuration

### Environment Variables```env
# Gmail API Configuration
CREDENTIALS_FILE=credentials.json
TOKEN_FILE=token.json

# Nurturing Settings
PER_MINUTE=12
RESUME=false
LOG_FILE=send_log.csv

# MCP Server Settings
MCP_SERVER_PORT=8000
LOG_LEVEL=INFO

Nurturing Configuration```json

{
"sender_email": "your-email@domain.com",
"follow_up_schedule": {
"followup_1_days": 3,
"followup_2_days": 7
},
"automation": {
"check_responses_interval_hours": 4,
"auto_respond_to_interest": true
}
}


## 📈 Performance Metrics

### Expected Results
- **Response Rate**: 20-30% from initial outreach
- **Follow-up Response**: 40-60% from follow-ups
- **Conversion Rate**: 10-15% to interested leads
- **Automation Coverage**: 80% of responses handled automatically
- **Uptime**: 99.9% with Docker restart policies

### Monitoring
- Real-time lead scoring and status tracking
- Response rate analytics and conversion metrics
- System health monitoring and error reporting
- Complete audit trail of all interactions

## 🚀 Deployment Options

### Docker (Recommended)```bash
# One-click deployment
./deploy.sh

# Manual deployment
docker-compose up -d

Local Development```bash

Install dependencies

pip install -r requirements.txt

Run nurturing system

python run_nurturing.py


### Production Server```bash
# Systemd service
sudo cp lead-nurturing.service /etc/systemd/system/
sudo systemctl enable lead-nurturing
sudo systemctl start lead-nurturing

🔒 Security & Privacy

  • Local Data Storage - All data remains on your server
  • OAuth2 Authentication - Secure Gmail API access
  • No External Services - No data sent to third parties
  • Encrypted Credentials - Secure credential management
  • Audit Logging - Complete activity tracking

📞 Support & Documentation

  • Deployment Guide: DEPLOYMENT_GUIDE.md
  • Nurturing Guide: NURTURING_README.md
  • Debug Report: DEBUG_REPORT.md
  • Docker Setup: docker-compose.yml

🎯 Use Cases

Sales Outreach

  • B2B lead generation and nurturing
  • Automated follow-up sequences
  • Response tracking and lead scoring

Marketing Campaigns

  • Email marketing automation
  • A/B testing and optimization
  • Performance analytics

Customer Success

  • Onboarding email sequences
  • Renewal and upsell campaigns
  • Customer feedback collection

📊 System Architecture```

┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
│ MCP Client │◄──►│ MCP Server │◄──►│ Lead Nurturer │
│ (Control) │ │ (24/7 Service) │ │ (Automation) │
└─────────────────┘ └──────────────────┘ └─────────────────┘
│
▼
┌──────────────────┐
│ Gmail API │
│ (Email System) │
└──────────────────┘
```

🏆 Enterprise Features

  • 24/7 Operation - Continuous automation
  • Scalable Architecture - Handle thousands of leads
  • Professional Monitoring - Real-time dashboards
  • Error Recovery - Automatic failure handling
  • Audit Compliance - Complete activity logging
  • Docker Deployment - Production-ready containerization

Ready to automate your lead nurturing? 🚀

This system is production-ready and can handle enterprise-scale email campaigns with full automation, monitoring, and 24/7 operation.

📄 License

This project is licensed under the MIT License - see the LICENSE file for details.

🤝 Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

📧 Contact

  • Author: Brandon
  • Company: Quantra Labs
  • Repository: GMAIL-MCP-Agent

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Gmail MCP Agent 怎么安装?

在客户端按下面的安装命令接入:pip install -r requirements.txt。装完在客户端配置里引用同一个包或端点。

Gmail MCP Agent 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Gmail MCP Agent 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Gmail MCP Agent 需要 API Key 吗?

资料标注需要Token认证,使用前准备好对应凭据,并按最小权限配置。

Gmail MCP Agent 能提供哪些能力?

资料显示能力标签包括 Python、Gmail集成、团队协作。具体工具清单以官方文档为准。

Gmail MCP Agent 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

Gmail MCP Agent 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。