studio.altessa/altessa · v1.0.0 · ai-and-media
Altessa Wedding Planner is healthy: it completed an MCP handshake in 1730 ms and exposes 4 tools.
Reception layouts to scale, seating charts, wedding day timelines, and budgets. No login needed.
Endpoint: https://mcp.altessa.studio/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 4 |
| Latency | 1730 ms |
| Last checked (UTC) | 2026-10-25T17:55:10.971Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-25T17:55:10.971Z | Healthy | 1730 |
plan_reception_layout | Use this when someone wants to plan a wedding reception floor plan, figure out how many tables fit in a room, or check whether a venue space can hold their guest count with a dance floor, bar, buffet, DJ or band, and head table. Needs guest count; room dimensions in feet are optional (if missing, re |
generate_seating_chart | Use this when someone has a list of wedding guests and wants them assigned to tables, keeping families, friend groups, or couples together and keeping specific people apart. Accepts names with optional group labels and keep-apart pairs. Returns table assignments and a shareable chart. Do not use for |
build_wedding_timeline | Use this when someone wants a minute-by-minute wedding day schedule: getting ready, first look, ceremony, cocktail hour, reception, send-off. Needs the ceremony start time; everything else has defaults. Do not use for the months-long planning checklist or vendor payment schedules. |
estimate_wedding_budget | Use this when someone gives a total wedding budget, a guest count, or both and wants a category-by-category split (venue, catering, photo and video, flowers, music, attire, stationery, and so on) with per-guest math and a contingency line. Do not use for tracking actual spending or vendor payments. |