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