channel_health — Obriym CRM MCP Prompt

channel_health is one of 7 prompts on the Obriym CRM MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke channel_health from your client

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

Other prompts on this server

• triage_stale_leads
• pipeline_review
• daily_briefing
• qualify_lead
• add_product
• stock_check

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.