developer-tools

Zapmail

dsouzaalan

by dsouzaalan

Zapmail enables domain purchasing, bulk mailbox creation, and automated email workflows for large-scale cold email campa

Integrates with Zapmail API to enable domain purchasing, bulk mailbox creation, email automation workflows, and platform exports for large-scale cold email operations through natural language commands with advanced workflow orchestration.

github stars

1

0 commentsdiscussion

Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.

46+ tools availableExports to Instantly, Smartlead, Reply.ioNatural language processing

best for

  • / Cold email marketers scaling outreach campaigns
  • / Agencies managing multiple client domains
  • / Sales teams automating email workflows
  • / Businesses setting up bulk email infrastructure

capabilities

  • / Purchase and manage domains
  • / Create bulk email mailboxes
  • / Set up email automation workflows
  • / Export data to cold email platforms
  • / Process natural language commands
  • / Manage multiple workspaces

what it does

Connects to the Zapmail API to manage domains, create bulk email accounts, and export data for cold email campaigns. Provides natural language access to 46+ Zapmail tools through AI assistants.

about

Zapmail is a community-built MCP server published by dsouzaalan that provides AI assistants with tools and capabilities via the Model Context Protocol. Zapmail enables domain purchasing, bulk mailbox creation, and automated email workflows for large-scale cold email campa It is categorized under developer tools.

how to install

You can install Zapmail in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.

license

NOASSERTION

Zapmail is released under the NOASSERTION license.

readme

Zapmail MCP Server

A Model Context Protocol (MCP) server for the Zapmail API that provides natural language access to domain management, mailbox operations, and exports. This package enables AI assistants like Claude to interact with Zapmail through natural language commands.

Features

  • Complete Zapmail API coverage (46+ tools)
  • Natural language command processing
  • Dynamic tool generation from API documentation
  • Export support for Reachinbox, Instantly, Smartlead, Reply.io, and CSV
  • Caching system with TTL
  • Rate limiting and error handling
  • Multi-workspace support
  • MCP integration with Claude Desktop and Cursor

Prerequisites

  • Node.js 18+
  • Zapmail API key
  • MCP-compatible client (Claude Desktop, Cursor, etc.)
  • Optional: OpenAI API key for enhanced natural language processing

Installation

Option 1: Using npx (Recommended)

No installation required - run directly with npx:

npx zapmail-mcp

Option 2: Global Installation

Install globally for persistent access:

npm install -g zapmail-mcp

MCP Configuration

For Claude Desktop

Create or update claude_desktop_config.json:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

Using npx (Recommended):

{
  "mcpServers": {
    "zapmail": {
      "command": "npx",
      "args": ["zapmail-mcp"],
      "env": {
        "ZAPMAIL_API_KEY": "your-zapmail-api-key"
      }
    }
  }
}

Using global installation:

{
  "mcpServers": {
    "zapmail": {
      "command": "zapmail-mcp",
      "args": [],
      "env": {
        "ZAPMAIL_API_KEY": "your-zapmail-api-key"
      }
    }
  }
}

For Cursor

Add to your Cursor MCP settings:

Using npx (Recommended):

{
  "mcpServers": {
    "zapmail": {
      "command": "npx",
      "args": ["zapmail-mcp"],
      "env": {
        "ZAPMAIL_API_KEY": "your-zapmail-api-key"
      }
    }
  }
}

Using global installation:

{
  "mcpServers": {
    "zapmail": {
      "command": "zapmail-mcp",
      "args": [],
      "env": {
        "ZAPMAIL_API_KEY": "your-zapmail-api-key"
      }
    }
  }
}

Quick Start

  1. Get your Zapmail API key:

    • Sign up at Zapmail
    • Navigate to your API settings
    • Generate a new API key
  2. Configure your MCP client:

    • Choose your preferred MCP client (Claude Desktop or Cursor)
    • Add the configuration JSON above to your MCP settings
    • Replace your-zapmail-api-key with your actual API key
  3. Test the connection:

    • Open your MCP client
    • Try natural language commands like:
      • "List all my Zapmail workspaces"
      • "Show me my domains"
      • "Check if example.com is available for purchase"

Available Tools

Core Management Tools

  • set_context - Set workspace and provider context
  • wallet_balance - Get wallet balance
  • list_workspaces - List all workspaces
  • list_domains - List domains in workspace
  • check_domain_availability - Check domain availability
  • purchase_domains - Purchase domains (wallet-first)
  • create_mailboxes_for_zero_domains - Create mailboxes on empty domains
  • add_third_party_account - Add third-party export account
  • call_endpoint - Call any Zapmail endpoint
  • generate_usernames - Generate mailbox usernames
  • generate_name_pairs - Generate name pairs
  • generate_domains - Generate AI-powered domain suggestions
  • check_domain_availability_batch - Batch domain availability check
  • plan_and_execute - Natural-language plan & execute
  • get_server_info - Get server information

System Management Tools

  • get_metrics - Get system metrics and performance data
  • clear_cache - Clear system cache
  • health_check - System health check

Advanced Mailbox Tools

  • bulk_update_mailboxes - Bulk update mailboxes
  • search_mailboxes - Search mailboxes with advanced filters

Export System Tools

  • get_export_info - Get export system information
  • get_export_scenario - Get export scenario instructions
  • validate_export_request - Validate export request parameters
  • export_guidance - Get export guidance and best practices

API Documentation Tools

  • get_api_info - Get comprehensive API endpoint information
  • search_api_endpoints - Search API endpoints by keyword
  • get_api_scenarios - Get common API usage scenarios
  • get_api_best_practices - Get API best practices and recommendations
  • generate_api_examples - Generate API usage examples

Dynamic API Tools

All documented API endpoints with automatic tool generation

Natural Language Commands

Once connected to your MCP client, you can use natural language to control Zapmail:

Workspace & Domain Management

  • "List all my workspaces"
  • "Show domains in current workspace containing 'lead'"
  • "Check if leadconnectlab.com is available for 2 years"
  • "Buy leadconnectlab.com and outreachprohub.com for 1 year using wallet if possible"

Mailbox Management

  • "Create 3 mailboxes per domain where there are zero mailboxes"
  • "Setup 100 mailboxes and connect to Instantly.ai for me"
  • "Update all mailboxes with new names"

Export Operations

  • "Export all mailboxes to reachinbox"
  • "Export mailboxes to instantly"
  • "Export mailboxes as CSV"
  • "Export specific mailboxes"
  • "Export mailboxes from leadconnectio.com domain"

Third-Party Integration

  • "Connect reachinbox account"
  • "Add instantly credentials"
  • "Link smartlead account"
  • "Setup reply.io integration"

Configuration

Environment Variables

VariableDescriptionDefaultRequired
ZAPMAIL_API_KEYYour Zapmail API key-Yes
ZAPMAIL_WORKSPACE_KEYDefault workspace ID-No
ZAPMAIL_SERVICE_PROVIDEREmail provider (GOOGLE/MICROSOFT)GOOGLENo
ZAPMAIL_LOG_LEVELLogging level (DEBUG/INFO/WARN/ERROR)INFONo
ZAPMAIL_MAX_RETRIESMaximum retry attempts3No
ZAPMAIL_TIMEOUT_MSRequest timeout in milliseconds30000No
ZAPMAIL_ENABLE_CACHEEnable response cachingtrueNo
ZAPMAIL_ENABLE_METRICSEnable performance metricstrueNo
ZAPMAIL_RATE_LIMIT_DELAYRate limiting delay in ms1000No
OPENAI_API_KEYOpenAI API key for enhanced NLP-No

Usage Examples

Domain Operations

Check Domain Availability

In Claude Desktop or Cursor:

"Check if example.com is available for 1 year"

Purchase Domains

In Claude Desktop or Cursor:

"Buy example.com and test.com for 1 year using wallet if possible"

Mailbox Management

Create Mailboxes on Empty Domains

In Claude Desktop or Cursor:

"Create 5 mailboxes on domains that have zero mailboxes"

Bulk Update Mailboxes

In Claude Desktop or Cursor:

"Update all mailboxes with new names and details"

Export Operations

Export to Reachinbox

In Claude Desktop or Cursor:

"Connect my Reachinbox account and export all mailboxes"

Get Export Guidance

In Claude Desktop or Cursor:

"Help me export 100 mailboxes to Reachinbox"

Complex Workflows

Multi-Step Operations

In Claude Desktop or Cursor:

"Buy example.com and test.com, create 5 mailboxes on each, and export to reachinbox"

Workspace Management

In Claude Desktop or Cursor:

"Show me all my workspaces and switch to the one with the most domains"

System Monitoring

Health Check

In Claude Desktop or Cursor:

"Check the health of my Zapmail connection"

Get Metrics

In Claude Desktop or Cursor:

"Show me performance metrics for my Zapmail operations"

Troubleshooting

MCP Connection Issues

1. MCP Server Not Found

Problem: "zapmail-mcp command not found" or "npx zapmail-mcp not found" Solutions:

For npx usage:

# Test npx directly
npx zapmail-mcp --version

# If npx fails, try with explicit package version
npx zapmail-mcp@latest --version

# Get help information
npx zapmail-mcp --help

For global installation:

# Install the package globally
npm install -g zapmail-mcp

# Verify installation
zapmail-mcp --version

2. MCP Client Not Detecting Server

Problem: Zapmail tools not appearing in Claude Desktop/Cursor Solutions:

  • Restart your MCP client (Claude Desktop/Cursor)
  • Check your MCP configuration file syntax
  • Verify the command path in your config

3. API Key Issues

Problem: "ZAPMAIL_API_KEY not configured" Solutions:

  • Set environment variable in your MCP config:
{
  "mcpServers": {
    "zapmail": {
      "command": "npx",
      "args": ["zapmail-mcp"],
      "env": {
        "ZAPMAIL_API_KEY": "your-api-key"
      }
    }
  }
}
  • Or set globally:
export ZAPMAIL_API_KEY="your-api-key"

4. Workspace Context Issues

Problem: Getting data from wrong workspace Solution: Set workspace in MCP config:

{
  "env": {
    "ZAPMAIL_WORKSPACE_KEY": "your-workspace-id"
  }
}

Performance Issues

1. Slow Response Times

Problem: MCP operations taking too long Solutions:

  • Enable caching: ZAPMAIL_ENABLE_CACHE="true"
  • Increase rate limit delay: ZAPMAIL_RATE_LIMIT_DELAY="2000"
  • Check your internet connection

2. Rate Limiting

Problem: "Too many requests" errors Solution: Increase rate limit delay in MCP config:

{
  "env": {
    "ZAPMAIL_RATE_LIMIT_DELAY": "2000"
  }
}

Debug Mode

Enable debug logging


FAQ

What is the Zapmail MCP server?
Zapmail is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
How do MCP servers relate to agent skills?
Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
How are reviews shown for Zapmail?
This profile displays 47 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.

Use Cases

Extended AI Capabilities

Add new capabilities to Claude beyond text generation

Example

Access external data sources, execute code, interact with tools and services

Transform Claude from chatbot to action-taking agent

Context Enhancement

Provide Claude with access to relevant context and data

Example

Load project documentation, access knowledge bases, query databases

Get more accurate, context-aware responses

Workflow Automation

Automate multi-step workflows combining AI and external tools

Example

Research → Summarize → Create document → Send notification

Complete complex tasks end-to-end without manual steps

Implementation Guide

Prerequisites

  • Claude Desktop 0.7.0+ or Cursor IDE with MCP support
  • Basic understanding of MCP architecture and capabilities
  • Access credentials for integrated services (if required)
  • Willingness to experiment and iterate on configuration

Time Estimate

15-60 minutes depending on server complexity

Installation Steps

  1. 1.Install MCP server: npm install -g [package-name] or via GitHub
  2. 2.Add server configuration to ~/.claude/mcp.json
  3. 3.Provide required credentials and configuration
  4. 4.Restart Claude Desktop to load new server
  5. 5.Test basic functionality with simple prompts
  6. 6.Explore capabilities and experiment with use cases
  7. 7.Document successful patterns for reuse

Troubleshooting

  • MCP server not loading: Check config syntax, verify installation
  • Connection errors: Check network, firewall, credentials
  • Feature not working: Read server docs, check required parameters
  • Performance issues: Monitor resource usage, check for network latency
  • Conflicts with other servers: Check port assignments, namespace collisions

Best Practices

✓ Do

  • +Read server documentation thoroughly before setup
  • +Start with simple use cases to validate functionality
  • +Test in non-production environment first
  • +Monitor resource usage and performance
  • +Keep servers updated for bug fixes and new features
  • +Document configuration for team members
  • +Use environment variables for sensitive configuration

✗ Don't

  • Don't grant overly permissive access to MCP servers
  • Don't skip reading security considerations in docs
  • Don't expose sensitive data without proper controls
  • Don't run untrusted MCP servers without code review
  • Don't ignore error messages—investigate root cause

💡 Pro Tips

  • Combine multiple MCP servers for powerful workflows
  • Create custom MCP servers for your specific needs
  • Share successful configurations with team
  • Use MCP inspector for debugging
  • Join MCP community for tips and troubleshooting

Technical Details

Architecture

Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.

Protocols

  • Model Context Protocol (MCP)
  • JSON-RPC 2.0
  • stdio or HTTP transport

Compatibility

  • Claude Desktop
  • Cursor IDE
  • Custom MCP clients

When to Use This

✓ Use When

Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.

✗ Avoid When

Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.

Integration

  • Tool composition: Chain multiple MCP tools in workflows
  • Context augmentation: Provide AI with relevant external data
  • Action delegation: Let AI execute tasks on external systems
  • Bidirectional sync: Keep AI context and external systems in sync

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.

List & Promote Your MCP Server

Share your MCP server with the developer community

GET_STARTED →
MCP server reviews

Ratings

4.547 reviews
  • Liam Rao· Dec 24, 2024

    According to our notes, Zapmail benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.

  • Lucas Zhang· Dec 20, 2024

    Zapmail reduced integration guesswork — categories and install configs on the listing matched the upstream repo.

  • Liam Jackson· Dec 12, 2024

    We wired Zapmail into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.

  • Shikha Mishra· Dec 8, 2024

    Useful MCP listing: Zapmail is the kind of server we cite when onboarding engineers to host + tool permissions.

  • Mia Lopez· Nov 27, 2024

    Zapmail is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.

  • Liam Gill· Nov 15, 2024

    Zapmail has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Evelyn Diallo· Nov 11, 2024

    Zapmail is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.

  • Layla Ndlovu· Nov 3, 2024

    We evaluated Zapmail against two servers with overlapping tools; this profile had the clearer scope statement.

  • Omar Sanchez· Oct 22, 2024

    Zapmail has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.

  • Ama Wang· Oct 18, 2024

    Useful MCP listing: Zapmail is the kind of server we cite when onboarding engineers to host + tool permissions.

showing 1-10 of 47

1 / 5