triage_inbox — Getlead MCP Prompt

triage_inbox is one of 3 prompts on the Getlead 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 Getlead Prompt/triage_inbox run in your project directory
• Claude Desktop Getlead Prompt/triage_inbox ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor Getlead Prompt/triage_inbox ~/.cursor/mcp.json
• VS Code Getlead Prompt/triage_inbox .vscode/mcp.json
• Zed Getlead Prompt/triage_inbox ~/.config/zed/settings.json
• Windsurf Getlead Prompt/triage_inbox ~/.codeium/windsurf/mcp_config.json
• Cline Getlead Prompt/triage_inbox ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI Getlead Prompt/triage_inbox ~/.gemini/settings.json
• Grok Getlead Prompt/triage_inbox .mcp.json (in your project root)
• ChatGPT Getlead Prompt/triage_inbox Settings → Connectors → Advanced → Developer mode
• Claude.ai Getlead Prompt/triage_inbox Settings → Connectors → Add custom connector
• LangChain Getlead Prompt/triage_inbox pip install langchain-mcp-adapters

Other prompts on this server

• plan_outbound_campaign
• build_icp_list

Getlead also offers 2 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 26 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.