email-clean-up

This Project will focus on cleaning up my Gmail account.

This MCP server was generated using the Template Orchestrator and includes the following integrations:

Available Tools

This MCP server provides 25 tools across 1 integrations:

GoogleGmail Tools

• google-gmail_get_draft: Get a specific draft by ID
• google-gmail_get_label: Get label details by ID
• google-gmail_get_thread: Get a specific thread by ID
• google-gmail_send_draft: Send an existing draft
• google-gmail_get_message: Get a specific message by ID
• google-gmail_get_profile: Get user's Gmail profile information
• google-gmail_list_drafts: List draft messages in user's mailbox
• google-gmail_list_labels: List all labels in the user's mailbox
• google-gmail_create_draft: Create a new draft message. IMPORTANT: Message must be an object with 'raw' field containing base64url-encoded RFC 2822 formatted message.
• google-gmail_create_label: Create a new custom label
• google-gmail_delete_draft: Delete a draft. Returns 204 No Content with empty body on success.
• google-gmail_delete_label: Delete a custom label. Returns 204 No Content with empty body on success.
• google-gmail_list_threads: List email threads in user's mailbox
• google-gmail_send_message: Send an email message. Requires message in RFC 2822 format encoded as base64url string
• google-gmail_trash_thread: Move an entire email thread/conversation to trash (RECOMMENDED for deleting conversations). This is the standard way users delete email threads - remains recoverable for 30 days.
• google-gmail_update_draft: Update an existing draft. IMPORTANT: Message must be an object with 'raw' field containing base64url-encoded RFC 2822 formatted message.
• google-gmail_update_label: Update an existing label
• google-gmail_delete_thread: PERMANENTLY delete an entire thread - IMMEDIATE and IRREVERSIBLE. WARNING: Use trash_thread instead for normal conversation deletion. Only use this for sensitive data that must be immediately destroyed. Bypasses trash completely. REQUIRES https://mail.google.com/ scope. Returns 204 No Content with empty body on success.
• google-gmail_list_messages: List messages in user's mailbox with optional filtering
• google-gmail_modify_thread: Modify labels on all messages in a thread
• google-gmail_trash_message: Move a message to trash (RECOMMENDED for deleting emails). This is the standard way users delete emails - messages remain recoverable for 30 days.
• google-gmail_delete_message: PERMANENTLY delete a message - IMMEDIATE and IRREVERSIBLE. WARNING: Use trash_message instead for normal email deletion. Only use this for sensitive data that must be immediately destroyed. Bypasses trash completely. REQUIRES https://mail.google.com/ scope. Returns 204 No Content with empty body on success.
• google-gmail_modify_message: Modify labels on a message (add/remove labels, mark read/unread)
• google-gmail_untrash_thread: Remove a thread from trash
• google-gmail_untrash_message: Remove a message from trash

Installation

npm install @coretext-ai-public/email-clean-up-cb8a5661-e56d-43cb-9e14-f0d70effd443

Environment Setup

Create a .env file with the following variables:

GOOGLE_OAUTH_CREDENTIALS=your_google_oauth_credentials_here

Usage

Running the server

# Development mode
npm run dev

# Production mode
npm run build && npm start

Using with Claude Desktop

Add this to your Claude Desktop configuration:

{
  "mcpServers": {
    "email-clean-up": {
      "command": "npx",
      "args": ["@coretext-ai-public/email-clean-up-cb8a5661-e56d-43cb-9e14-f0d70effd443"],
      "env": {
        "GOOGLE_OAUTH_CREDENTIALS": "your_google_oauth_credentials_here"
      }
    }
  }
}

Instructions for Fetching API Keys/Tokens

• COMING SOON

Advanced Features

Request Cancellation

This MCP server supports request cancellation according to the MCP cancellation specification. Clients can cancel in-progress requests by sending a notifications/cancelled message with the request ID.

When a request is cancelled:

• The server immediately stops processing the request
• Any ongoing API calls are aborted
• Resources are cleaned up
• No response is sent for the cancelled request

Progress Notifications

The server supports progress notifications for long-running operations according to the MCP progress specification.

To receive progress updates:

1. Include a progressToken in your request metadata
2. The server will send notifications/progress messages with:
   • Current progress value
   • Total value (when known)
   • Human-readable status messages

Progress is reported for:

• Multi-step operations
• Batch processing
• Long-running API calls
• File uploads/downloads

Example progress notification:

{
  "method": "notifications/progress",
  "params": {
    "progressToken": "operation-123",
    "progress": 45,
    "total": 100,
    "message": "Processing item 45 of 100..."
  }
}

Generated Information

• Generated at: Tue Nov 11 2025 20:48:46 GMT+0000 (Coordinated Universal Time)
• Orchestrator version: 0.0.2
• Template repository: Coretext-AI-Dev/server-template-v2
• Total endpoints: 25