manage-deal — FavCRM MCP Prompt
manage-deal
is one of 37 prompts on the
FavCRM
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke manage-deal from your client
- Claude Code FavCRM Prompt/manage-deal run in your project directory
- Claude Desktop FavCRM Prompt/manage-deal ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor FavCRM Prompt/manage-deal ~/.cursor/mcp.json
- VS Code FavCRM Prompt/manage-deal .vscode/mcp.json
- Zed FavCRM Prompt/manage-deal ~/.config/zed/settings.json
- Windsurf FavCRM Prompt/manage-deal ~/.codeium/windsurf/mcp_config.json
- Cline FavCRM Prompt/manage-deal ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI FavCRM Prompt/manage-deal ~/.gemini/settings.json
- Grok FavCRM Prompt/manage-deal .mcp.json (in your project root)
- ChatGPT FavCRM Prompt/manage-deal Settings → Connectors → Advanced → Developer mode
- Claude.ai FavCRM Prompt/manage-deal Settings → Connectors → Add custom connector
- LangChain FavCRM Prompt/manage-deal pip install langchain-mcp-adapters
Other prompts on this server
- add-customer
- onboard-member
- enrol-customer-tier
- add-loyalty-points
- issue-gift-reward
- book-customer
- cancel-and-refund
- handle-no-show
- send-booking-reminder
- create-service
- set-up-promotion
- send-campaign
- respond-to-ticket
- complete-booking
- publish-blog-post
- fulfil-order
- customer-360
- find-top-customers
- bulk-tag-segment
- build-segment
- manage-task
- switch-workspace
- inbox-triage
- review-cancellations
- generate-blog-post
- bill-customer
- record-payment
- chase-overdue-invoices
- void-invoice
- start-subscription
- cancel-subscription
- handle-past-due
- pause-subscription
- train-ai-agent
- prune-knowledge
- weekly-snapshot
FavCRM also offers 5 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.