add_campaign_step — Mailcannon MCP Tool Mutating
add_campaign_step
(add campaign step) is one of 34 tools on the
Mailcannon
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call add_campaign_step from your client
- Claude Code Mailcannon add_campaign_step run in your project directory
- Claude Desktop Mailcannon add_campaign_step ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Mailcannon add_campaign_step ~/.cursor/mcp.json
- VS Code Mailcannon add_campaign_step .vscode/mcp.json
- Zed Mailcannon add_campaign_step ~/.config/zed/settings.json
- Windsurf Mailcannon add_campaign_step ~/.codeium/windsurf/mcp_config.json
- Cline Mailcannon add_campaign_step ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Mailcannon add_campaign_step ~/.gemini/settings.json
- Grok Mailcannon add_campaign_step .mcp.json (in your project root)
- ChatGPT Mailcannon add_campaign_step Settings → Connectors → Advanced → Developer mode
- Claude.ai Mailcannon add_campaign_step Settings → Connectors → Add custom connector
- LangChain Mailcannon add_campaign_step pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mailcannon https://www.thinkandautomate.dev/api/mcpOther tools on this server
- add_contact
- add_contacts
- list_contacts
- remove_contact
- update_contact_tags
- list_tags
- create_campaign
- list_campaigns
- delete_campaign
- update_campaign
- delete_campaign_step
- update_campaign_step
- schedule_campaign
- list_schedules
- process_campaigns
- add_provider
- list_providers
- remove_provider
- get_deliverability
- create_task
- list_tasks
- update_task
- delete_task
- get_setting
- set_setting
- list_settings
- send_test_email
- check_domain_deliverability
- check_email_spam_score
- pause_campaign
- resume_campaign
- retry_failed
- check_step_spam_score
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.