local_research — MailerDot MCP Prompt
local_research
is one of 3 prompts on the
MailerDot
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke local_research from your client
- Claude Code MailerDot Prompt/local_research run in your project directory
- Claude Desktop MailerDot Prompt/local_research ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor MailerDot Prompt/local_research ~/.cursor/mcp.json
- VS Code MailerDot Prompt/local_research .vscode/mcp.json
- Zed MailerDot Prompt/local_research ~/.config/zed/settings.json
- Windsurf MailerDot Prompt/local_research ~/.codeium/windsurf/mcp_config.json
- Cline MailerDot Prompt/local_research ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI MailerDot Prompt/local_research ~/.gemini/settings.json
- Grok MailerDot Prompt/local_research .mcp.json (in your project root)
- ChatGPT MailerDot Prompt/local_research Settings → Connectors → Advanced → Developer mode
- Claude.ai MailerDot Prompt/local_research Settings → Connectors → Add custom connector
- LangChain MailerDot Prompt/local_research pip install langchain-mcp-adapters
Other prompts on this server
MailerDot also offers 6 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 10 November 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.