MCP recipes
Turn hot intent signal leads into drafted messages you approve
This recipe asks your assistant to pull the high intent leads your signals produced, check each one's history so it does not write to someone already in a conversation, and queue a draft message for the right ones. Drafts wait in the approval queue and nothing is sent until you approve.
Published by Sellinger AI. Numbers and settings checked on 19 October 2026 against the fact register. Report an error.
What this recipe does
Signals add the people to your CRM. This recipe takes the step after: decide who to write to now and prepare the message. compose_messages_to_queue stores one message for each lead you name as a pending item.
Connect the Sellinger connector first (claude.ai: Settings, Connectors, Add custom connector, paste https://app.sellinger.ai/api/v2/mcp). The steps are on the MCP page.
The prompt
Review my hot intent signal leads and prepare messages. 1. Call get_hot_leads. 2. For each of the first ten, call get_lead and get_lead_conversation and skip anyone who already has an open conversation. 3. Tell me why each remaining lead is hot, in one line. 4. Draft one short message for the group, written to read well without personalization, and call compose_messages_to_queue for channel linkedin with those lead ids. 5. Call list_approvals with status pending and show me the drafts. Do not approve anything.
The exact tools it calls
| Tool | What the recipe uses it for |
|---|---|
| `get_hot_leads` | High intent leads from intent signals |
| `get_lead` | The full lead record |
| `get_lead_conversation` | Tells you whether the lead is already in a conversation |
| `compose_messages_to_queue` | Queues one draft for each named lead as a pending approval. Nothing is sent |
| `list_approvals` | Reads the drafts back |
| `regenerate_approval_draft` | Rewrites a draft you do not like |
The connector has 43 tools in total.
What needs your approval
- Reads run freely.
- compose_messages_to_queue writes drafts only. A person still has to approve each one.
- approve_approval sends the message. Confirm each approval.
Sample output
No sample output is published for this recipe yet. It has not been run end to end in Claude or ChatGPT for this page, and we do not invent output. The tool names and what each returns are taken from the connector's tool descriptions in the product code (checked 19 October 2026). When a real run is captured it will be added here with its date.
Notes and limits
- The same text is stored for every lead, with no merge fields, so write copy that reads well unpersonalized or queue small batches.
- Leads that already have a pending draft on that channel, or cannot be reached on it, are skipped and reported back.
- Drafts expire after 14 days if nobody acts on them.
Common questions
Does it create new leads?
Will it send automatically?
Can it use email?
Sources and method
Tool names, parameters and warnings are from frontend/src/lib/mcp/hosted-tools.ts and the saved prompts in hosted-prompts.ts (43 registered tools, checked 19 October 2026). The recipe has not been run for this page.
Related: signal based outreach, approval queue triage, intent signals, all recipes, MCP connector.
