Gmail AutoAuth MCP Server
by MCP-Mirror
A Model Context Protocol (MCP) server for Gmail integration in Claude Desktop with auto authentication support. This server enables AI assistants to manage Gmail through natural language interactions.
Last updated: N/A
What is Gmail AutoAuth MCP Server?
This is a Model Context Protocol (MCP) server designed to integrate Gmail with Claude Desktop, providing auto-authentication capabilities. It allows AI assistants to interact with and manage Gmail accounts using natural language.
How to use Gmail AutoAuth MCP Server?
To use this server, you need to create a Google Cloud Project, enable the Gmail API, and obtain OAuth 2.0 credentials. You can install it via Smithery or manually. After installation, authenticate using the provided commands, configure it in Claude Desktop, and then use the provided JSON examples to interact with Gmail.
Key features of Gmail AutoAuth MCP Server
Send emails with attachments
Read email messages by ID
Search emails with various criteria
List emails in inbox, sent, or custom labels
Mark emails as read/unread
Move emails to different labels/folders
Delete emails
Simple OAuth2 authentication flow with auto browser launch
Support for both Desktop and Web application credentials
Global credential storage for convenience
Use cases of Gmail AutoAuth MCP Server
Automated email sending from AI assistants
Intelligent email searching and filtering
Managing email labels and folders through natural language
Integrating Gmail functionality into Claude Desktop workflows
FAQ from Gmail AutoAuth MCP Server
Where are OAuth credentials stored?
Where are OAuth credentials stored?
OAuth credentials are stored securely in your local environment at ~/.gmail-mcp/.
What if the OAuth keys are not found?
What if the OAuth keys are not found?
Make sure gcp-oauth.keys.json is in either your current directory or ~/.gmail-mcp/ and check file permissions.
What if I get an invalid credentials format error?
What if I get an invalid credentials format error?
Ensure your OAuth keys file contains either web or installed credentials. For web applications, verify the redirect URI is correctly configured.
What if port 3000 is already in use?
What if port 3000 is already in use?
If port 3000 is already in use, please free it up before running authentication. You can find and stop the process using that port.
How do I contribute to this project?
How do I contribute to this project?
Contributions are welcome! Please feel free to submit a Pull Request.