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