Toast

Toast — connector documentation

• MCP endpoint: https://toast.connectorbay.com/mcp
• REST API: POST https://toast.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://toast.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: none required. An optional Authorization: Bearer <key> raises rate limits.
• Health: https://toast.connectorbay.com/health · Tool schemas: https://toast.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/toast · agent@connectorbay.com

What Toast is for

The moment right before you have to stand up and say something at someone's wedding, funeral, retirement party, birthday, or graduation — and you're staring at a blank page not knowing where to start, how long to talk, what order things happen in, or what topics to avoid. Toast is a structure and etiquette companion for exactly that handful of life-event speeches, not a script generator: it hands you an original outline to fill in with your own true, specific details.

What it does

A section-by-section outline — an opening-hook approach, body prompts, and a closing move — for eleven life-event occasions: best man and maid of honor toasts, a father-of-the-bride/parent-of-the-couple speech, a general wedding guest toast, a eulogy, a retirement speech, a farewell/going-away speech, a birthday toast, an anniversary toast, a graduation speech, and a comedic roast (speech_outline); commonly cited length guidance for each occasion (speech_length_guide); a handful of original opening-line styles and approaches, not finished lines (opening_line_ideas); general etiquette norms — order, whether to stand, whether to raise a glass, tone by relationship, and what to avoid (toast_etiquette_guide); a dedicated, carefully written eulogy guide covering what to include, tone, and practical delivery tips like arranging a backup reader and printing large-font notes (eulogy_writing_guide); a comedic roast-tone calibrator across mild/medium/spicy, always landing on sincerity (roast_guide); a bank of original structural transition techniques between speech sections (speech_transition_phrases); a common-mistakes checklist per occasion (common_mistakes_guide); and a glossary of about a dozen ceremonial-speech terms (speech_glossary).

What it is not

Not a ghostwriter, and not a general public-speaking coach. Every outline, opening-line idea, and transition phrase is original placeholder-style scaffolding — bracketed prompts like "[Share a specific memory here]" meant to be filled in with your own true details — never a complete, verbatim script, and never a real named person's real speech, quote, poem, or song lyric. Toast is also deliberately narrower than a general speech-skills tool: it doesn't check filler words, calculate speaking pace, or plan a generic speech timer — it is specifically about the structure, etiquette, and templates for these particular life-event occasions.

Tools

Outline & timing

speech_outline — A structured outline for a life-event speech occasion — an opening-hook approach, body sections with original placeholder prompts, and a closing move. Original scaffolding to fill in with your own details, not a fill-in-the-blank script to recite verbatim. Use for "what's the structure for a best man speech", "outline a eulogy". Args: occasion.

speech_length_guide — Commonly recommended length/duration for a life-event speech occasion (e.g. a best man toast commonly runs 3-5 minutes, a eulogy commonly 3-7 minutes), phrased as general guidance rather than a fixed rule. Use for "how long should a wedding toast be", "how long is a typical eulogy". Args: occasion.

Delivery & etiquette

opening_line_ideas — A handful of original example opening-line styles and approaches (techniques, not full scripted lines) for a life-event speech occasion — e.g. "start with how you met the couple", "open with a one-line description of what made them special". Use for "give me an opening line idea for a best man speech". Args: occasion.

toast_etiquette_guide — General etiquette norms for a life-event speech occasion: when to give it in the event's order, whether to stand, whether to raise a glass, appropriate tone/length by relationship to the honoree, and what to avoid (inside jokes, exes, indelicate topics). Use for "wedding toast etiquette", "when do you give a best man speech". Args: occasion.

common_mistakes_guide — Common pitfalls for a life-event speech occasion — rambling, inside jokes, oversharing about an ex, reading the whole thing off a phone, forgetting to toast, going too long. Use for "common mistakes in a best man speech", "what not to do in a eulogy". Args: occasion.

speech_transition_phrases — A bank of original generic transition-phrase styles between sections of a speech — structural connective techniques (the callback, the direct address, the time jump, ...), not scripted content. Use for "what's a good transition between parts of my speech".

Occasion specialists

eulogy_writing_guide — Sensitive, thoughtful guidance for writing and delivering a eulogy specifically: what to include (a life overview, character, relationships, a specific memory or two), tone guidance, and practical delivery tips (a backup reader in case of emotion, large-font printed notes). Use for "how do I write a eulogy", "eulogy tips".

roast_guide — Guidance on comedic "roast" speeches (typically for a retirement, birthday, or occasionally a wedding best-man context): how to keep it affectionate rather than cruel, calibrating tone_level (mild/medium/spicy) to the audience and relationship, always landing on a sincere note. Use for "how do I roast my friend without being mean", "roast ideas for a retirement party". Args: tone_level.

Reference

speech_glossary — A glossary of terms related to ceremonial/life-event speaking (toast, eulogy, roast, rehearsal dinner speech, emcee, receiving line, ...) — distinct from a general public-speaking glossary. Use for "what's a rehearsal dinner speech", "what does emcee mean". Args: term.

Conventions

• Read-only. Every tool reads public data or computes; nothing is written anywhere and nothing about the user is stored.
• Result envelope. ok: true with data, or ok: false with a structured error (bad_input, not_found, upstream_error). degraded lists optional sources that were unreachable.
• Rate limits. Free tier 60 tool calls/minute and 300/day per user (keyed on the user identifier supplied by the host agent, else client IP); Pro keys raise this. Over-limit calls return HTTP 429 with Retry-After. initialize and tools/list are never counted.

Support

agent@connectorbay.com · connectorbay.com/toast/support

Toast — Privacy Policy

Effective 24 September 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Toast is. Toast is a connector (an MCP server and REST API) that AI assistants and personal agents call on your behalf for a fully local life-event speech template and structure guide: outlines, length guidance, opening-line ideas, etiquette norms, a eulogy-writing guide, a roast-tone calibrator, transition phrases, common mistakes, and a glossary for weddings, eulogies, retirement/farewell speeches, birthdays, anniversaries, graduations, and roasts. You interact with your assistant; the assistant sends us only the arguments needed for that one lookup.

What we receive. The arguments of each tool call — an occasion name, a roast tone level, or a glossary term — the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant, and a Pro API key if you have one), and standard server logs.

Everything is answered from bundled, hand-curated reference content and nothing is stored. No request is forwarded to any third party — there is no upstream call at all, live or otherwise — and no query is logged in request bodies, recorded, or used to train anything. In particular, we do not receive or store the text of any speech, story, or memory you may be drafting elsewhere; Toast's tools take a short occasion name or term, never a transcript.

What we do not receive or store. We do not receive your conversation with the assistant or your name, and we do not build a profile from your queries: each request is answered independently and nothing carries over between requests. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting-provider access logs, which contain IP addresses and request paths but not request bodies, are retained for up to 30 days for security and abuse prevention.

Sub-processors. None — the entire dataset is bundled with the server and answered locally. Hosting: Vercel (United States regions).

Legal bases and your rights. Our processing is necessary to provide the service you request through your assistant. Because we store no personal data beyond short-lived logs, requests to access, correct or delete personal data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. We do not sell or share personal information and do not use your data to train models.

Children. Toast is a general-audience service operated by the adult using the assistant.

Changes. We will post changes here with a new effective date.

Toast — Terms of Service

Effective 24 September 2026. These terms govern use of the Toast connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Toast returns a fully local life-event speech template and structure guide — original outline scaffolding, length guidance, opening-line ideas, etiquette norms, a eulogy-writing guide, a roast-tone calibrator, transition phrases, common mistakes, and a glossary — from hand-curated reference content. It is accessed through an AI assistant or directly over MCP or HTTP.
2. Structure and etiquette guidance, not a ghostwriter. Every outline and example the Service returns is original placeholder-style scaffolding meant to be filled in with your own true, specific details — it is not a finished, ready-to-deliver script, and it does not reproduce any real person's real speech, quote, poem, or song lyric.
3. General guidance, not personal or professional advice. Length, etiquette, and tone guidance reflect commonly cited general practice, not universal rules, and vary by culture, faith, family, and venue. The eulogy-writing guide is general writing and delivery guidance, not grief counseling or a substitute for professional bereavement support.
4. Acceptable use. Automated use within the published rate limits is welcome.
5. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time.
6. Data. Our Privacy Policy describes what we process. In short: your query is answered from bundled reference content, and nothing is stored.
7. Pro keys. Optional Pro API keys are issued at our discretion, are personal to the holder and may be revoked for abuse.
8. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including for the content or reception of any speech prepared with its help. Our total liability is limited to US $100.
9. Governing law. California law; venue in San Mateo County, California.
10. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/toast

Toast support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://toast.connectorbay.com/mcp
• REST API: https://toast.connectorbay.com/openapi.json
• Live status: https://toast.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Toast never asks for them.