---
name: send-out-jobs
description: "Step-by-step job recipes for the Send Out MCP server: Draft email; Create calendar event; Create WhatsApp link. Use when the user asks things like \"Draft an email to alex@example.com with subject 'Project Milestone' saying 'Phase 1 is complete and ready for review.'.\" or \"Create a calendar event for 'Product Launch' on 2026-11-15T14:00 with duration 60 minutes in Europe/London.\""
license: MIT
---

# Send Out jobs

Each section below walks through one job with the tools of the `send-out` MCP server. The same recipes are MCP prompts (prompts/list) on `https://api.openkrill.app/gateway/mcp`.
Connect the server at `https://sendout.openkrill.app/mcp` in your MCP client settings (remote streamable HTTP, no key), then call its tools as normal tool calls. They are not command line programs: Bash, curl and scripts cannot reach them.

## Draft email

Job: Draft email, with the Send Out MCP server.

Use the `draft_email` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "Draft an email to alex@example.com with subject "Project Milestone" saying "Phase 1 is complete and ready for review."."

Steps:
1. Call `draft_email` as a normal MCP tool call, with the request's values in the fields of its inputSchema. It needs `body`.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"to":"alex@example.com","subject":"Project Milestone","body":"Phase 1 is complete and ready for review."}`
4. For the request "Draft an email to alex@example.com with subject "Project Milestone" saying "Phase 1 is complete and ready for review.".", a correct answer looks like this: Returns mailto_url with RFC 6068 parameters and eml_content containing valid MIME headers (To, Subject, Date, X-Unsent: 1).
5. Follow the server's own rules:
   - Use Send Out when the user wants to send or export generated content.
   - Each tool returns a link or file text the user opens and sends themselves.
   - Use draft_email for an email draft or .eml file.
   - Always show the returned link as a clickable markdown link and show the file content or a summary.
   - Tell the user that nothing is sent by the server and that they must review the draft before they send it.
   - Send Out does not support Instagram messages, LinkedIn messages, SMS, or bulk or automated email.
   - For those, say so plainly and offer an email draft or a copyable text instead.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `draft_email`).

## Create calendar event

Job: Create calendar event, with the Send Out MCP server.

Use the `create_calendar_event` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "Create a calendar event for "Product Launch" on 2026-11-15T14:00 with duration 60 minutes in Europe/London."

Steps:
1. Call `create_calendar_event` as a normal MCP tool call, with the request's values in the fields of its inputSchema. It needs `title`, `start`.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"title":"Product Launch","start":"2026-11-15T14:00","duration_minutes":60,"timezone":"Europe/London"}`
4. For the request "Create a calendar event for "Product Launch" on 2026-11-15T14:00 with duration 60 minutes in Europe/London.", a correct answer looks like this: Returns google_calendar_url pointing to calendar.google.com/calendar/render and ics_content starting with BEGIN:VCALENDAR.
5. Follow the server's own rules:
   - Use Send Out when the user wants to send or export generated content.
   - Each tool returns a link or file text the user opens and sends themselves.
   - Use create_calendar_event for a meeting, invite or .ics file.
   - Always show the returned link as a clickable markdown link and show the file content or a summary.
   - Tell the user that nothing is sent by the server and that they must review the draft before they send it.
   - Send Out does not support Instagram messages, LinkedIn messages, SMS, or bulk or automated email.
   - For those, say so plainly and offer an email draft or a copyable text instead.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `create_calendar_event`).

## Create WhatsApp link

Job: Create WhatsApp link, with the Send Out MCP server.

Use the `create_whatsapp_link` tool for this job.

Work on the user's request. If there is none yet, ask what they need. A request this job handles: "Create a WhatsApp link for phone "+1 (555) 234-5678" with message "Your appointment is confirmed for Tuesday at 3pm."."

Steps:
1. Call `create_whatsapp_link` as a normal MCP tool call, with the request's values in the fields of its inputSchema. It needs `text`.
2. If a value the tool needs is missing and you cannot tell it from the request, ask the user one short question first.
3. This input is known to work; copy its format, not its values: `{"phone":"+1 (555) 234-5678","text":"Your appointment is confirmed for Tuesday at 3pm."}`
4. For the request "Create a WhatsApp link for phone "+1 (555) 234-5678" with message "Your appointment is confirmed for Tuesday at 3pm.".", a correct answer looks like this: Returns wa_url equal to "https://wa.me/15552345678?text=Your%20appointment%20is%20confirmed%20for%20Tuesday%20at%203pm."
5. Follow the server's own rules:
   - Use Send Out when the user wants to send or export generated content.
   - Each tool returns a link or file text the user opens and sends themselves.
   - Use create_whatsapp_link for a WhatsApp message.
   - Always show the returned link as a clickable markdown link and show the file content or a summary.
   - Tell the user that nothing is sent by the server and that they must review the draft before they send it.
   - Send Out does not support Instagram messages, LinkedIn messages, SMS, or bulk or automated email.
   - For those, say so plainly and offer an email draft or a copyable text instead.
6. If the call fails or the answer looks wrong, tell the user, then report it with `submit_feedback` (kind bug, tool `create_whatsapp_link`).
