GMAIL -Agent

This MCP server provides a 24/7 Gmail outreach and lead-nurturing system. It orchestrates automated email campaigns, follow-up sequences at 3 and 7 days, response tracking, and lead scoring, all controllable via the MCP client. The server runs Python components that manage Gmail API interactions, lead nurturing logic, and a lightweight dashboard for monitoring. You can start, stop, query status, generate reports, and run test emails through the MCP client as well as execute individual scripts for nurturing, dashboard viewing, and CSV-based email sending. When combined with Docker deployment, the system becomes a production-ready, scalable automation platform for enterprise lead management.

{"Prerequisites:","- Python 3.9+ and pip installed on your system","- Git installed","- Optional: Docker and docker-compose for containerized deployment","","1) Clone the repository","git clone https://github.com/brandononchain/GMAIL-MCP-Agent.git","cd GMAIL-MCP-Agent","","2) Install Python dependencies","pip install -r requirements.txt","","3) Configure Gmail API credentials","- Obtain OAuth2 credentials from Google Cloud Console","- Save the credentials JSON as credentials.json in the project root","- Update sender email and nurturing settings in nurturing_config.json","","4) Run the MCP server (via UV SDK as configured)","- If using UVX (Python/uv):","uvx gmail-mcp-agent","Note: The exact command may vary based on your packaging; ensure the command matches the mcp_config entry used by your environment.","","5) Optional Docker deployment","- Build and start containers using Docker Compose","./deploy.sh # One-click deployment (recommended)","docker-compose up -d # Manual deployment"}

Tips and considerations:

• Ensure the Gmail API credentials (credentials.json) and OAuth tokens (token.json) are securely stored and not committed to version control.
• The MCP server port defaults to 8000; adjust MCP_SERVER_PORT in the environment if you run multiple MCP servers.
• The nurturing configuration (nurturing_config.json) controls sender_email, follow-up days (3 and 7), and automation settings. Customize to fit your workflow.
• For production, use Docker deployment to leverage containerization, health checks, and restart policies.
• Logs are written to send_log.csv by default; rotate or archive periodically to prevent growth from filling disk space.