harden_email — Default Privacy MCP Prompt

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

by client

How to invoke harden_email from your client

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

Other prompts on this server

• find_private_alternative
• audit_domain_privacy

Default Privacy also offers 4 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.