MCP server
by dsouzaalan
Zapmail enables domain purchasing, bulk mailbox creation, and automated email workflows for large-scale cold email campa
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.
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.
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.
NOASSERTION
Zapmail is released under the NOASSERTION license.
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
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
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
Share your MCP server with the developer community
According to our notes, Zapmail benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Zapmail reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We wired Zapmail into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Useful MCP listing: Zapmail is the kind of server we cite when onboarding engineers to host + tool permissions.
Zapmail is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Zapmail has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Zapmail is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
We evaluated Zapmail against two servers with overlapping tools; this profile had the clearer scope statement.
Zapmail has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Useful MCP listing: Zapmail is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 47
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.
No installation required - run directly with npx:
npx zapmail-mcp
Install globally for persistent access:
npm install -g zapmail-mcp
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"
}
}
}
}
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"
}
}
}
}
Get your Zapmail API key:
Configure your MCP client:
your-zapmail-api-key with your actual API keyTest the connection:
set_context - Set workspace and provider contextwallet_balance - Get wallet balancelist_workspaces - List all workspaceslist_domains - List domains in workspacecheck_domain_availability - Check domain availabilitypurchase_domains - Purchase domains (wallet-first)create_mailboxes_for_zero_domains - Create mailboxes on empty domainsadd_third_party_account - Add third-party export accountcall_endpoint - Call any Zapmail endpointgenerate_usernames - Generate mailbox usernamesgenerate_name_pairs - Generate name pairsgenerate_domains - Generate AI-powered domain suggestionscheck_domain_availability_batch - Batch domain availability checkplan_and_execute - Natural-language plan & executeget_server_info - Get server informationget_metrics - Get system metrics and performance dataclear_cache - Clear system cachehealth_check - System health checkbulk_update_mailboxes - Bulk update mailboxessearch_mailboxes - Search mailboxes with advanced filtersget_export_info - Get export system informationget_export_scenario - Get export scenario instructionsvalidate_export_request - Validate export request parametersexport_guidance - Get export guidance and best practicesget_api_info - Get comprehensive API endpoint informationsearch_api_endpoints - Search API endpoints by keywordget_api_scenarios - Get common API usage scenariosget_api_best_practices - Get API best practices and recommendationsgenerate_api_examples - Generate API usage examplesAll documented API endpoints with automatic tool generation
Once connected to your MCP client, you can use natural language to control Zapmail:
| Variable | Description | Default | Required |
|---|---|---|---|
ZAPMAIL_API_KEY | Your Zapmail API key | - | Yes |
ZAPMAIL_WORKSPACE_KEY | Default workspace ID | - | No |
ZAPMAIL_SERVICE_PROVIDER | Email provider (GOOGLE/MICROSOFT) | No | |
ZAPMAIL_LOG_LEVEL | Logging level (DEBUG/INFO/WARN/ERROR) | INFO | No |
ZAPMAIL_MAX_RETRIES | Maximum retry attempts | 3 | No |
ZAPMAIL_TIMEOUT_MS | Request timeout in milliseconds | 30000 | No |
ZAPMAIL_ENABLE_CACHE | Enable response caching | true | No |
ZAPMAIL_ENABLE_METRICS | Enable performance metrics | true | No |
ZAPMAIL_RATE_LIMIT_DELAY | Rate limiting delay in ms | 1000 | No |
OPENAI_API_KEY | OpenAI API key for enhanced NLP | - | No |
In Claude Desktop or Cursor:
"Check if example.com is available for 1 year"
In Claude Desktop or Cursor:
"Buy example.com and test.com for 1 year using wallet if possible"
In Claude Desktop or Cursor:
"Create 5 mailboxes on domains that have zero mailboxes"
In Claude Desktop or Cursor:
"Update all mailboxes with new names and details"
In Claude Desktop or Cursor:
"Connect my Reachinbox account and export all mailboxes"
In Claude Desktop or Cursor:
"Help me export 100 mailboxes to Reachinbox"
In Claude Desktop or Cursor:
"Buy example.com and test.com, create 5 mailboxes on each, and export to reachinbox"
In Claude Desktop or Cursor:
"Show me all my workspaces and switch to the one with the most domains"
In Claude Desktop or Cursor:
"Check the health of my Zapmail connection"
In Claude Desktop or Cursor:
"Show me performance metrics for my Zapmail operations"
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
Problem: Zapmail tools not appearing in Claude Desktop/Cursor Solutions:
Problem: "ZAPMAIL_API_KEY not configured" Solutions:
{
"mcpServers": {
"zapmail": {
"command": "npx",
"args": ["zapmail-mcp"],
"env": {
"ZAPMAIL_API_KEY": "your-api-key"
}
}
}
}
export ZAPMAIL_API_KEY="your-api-key"
Problem: Getting data from wrong workspace Solution: Set workspace in MCP config:
{
"env": {
"ZAPMAIL_WORKSPACE_KEY": "your-workspace-id"
}
}
Problem: MCP operations taking too long Solutions:
ZAPMAIL_ENABLE_CACHE="true"ZAPMAIL_RATE_LIMIT_DELAY="2000"Problem: "Too many requests" errors Solution: Increase rate limit delay in MCP config:
{
"env": {
"ZAPMAIL_RATE_LIMIT_DELAY": "2000"
}
}
Enable debug logging
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ 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.