batch_email_workflow — machfive MCP Prompt

batch_email_workflow is one of 3 prompts on the machfive MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke batch_email_workflow from your client

• Claude Code machfive Prompt/batch_email_workflow run in your project directory
• Claude Desktop machfive Prompt/batch_email_workflow ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor machfive Prompt/batch_email_workflow ~/.cursor/mcp.json
• VS Code machfive Prompt/batch_email_workflow .vscode/mcp.json
• Zed machfive Prompt/batch_email_workflow ~/.config/zed/settings.json
• Windsurf machfive Prompt/batch_email_workflow ~/.codeium/windsurf/mcp_config.json
• Cline machfive Prompt/batch_email_workflow ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI machfive Prompt/batch_email_workflow ~/.gemini/settings.json
• Grok machfive Prompt/batch_email_workflow .mcp.json (in your project root)
• ChatGPT machfive Prompt/batch_email_workflow Settings → Connectors → Advanced → Developer mode
• Claude.ai machfive Prompt/batch_email_workflow Settings → Connectors → Add custom connector
• LangChain machfive Prompt/batch_email_workflow pip install langchain-mcp-adapters

Other prompts on this server

• generate_cold_email
• check_batch_status

machfive also offers 3 resources — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.