Altessa Wedding Planner

studio.altessaPublished by altessa.studioOfficial publisherv1.0.0Updated Oct 26, 2026

Reception layouts to scale, seating charts, wedding day timelines, and budgets. No login needed.

VerifiedStreamable HTTPWeb executableLocation & LifestyleProductivity & Workflow

Overview

AI-generated overview

Remote MCP server for wedding planning: reception floor plans, guest seating charts, a minute-by-minute wedding day timeline, and budget estimates.

What you can do
  • Plan a reception layout: check whether a room fits a guest count with tables, dance floor, bar, buffet and head table
  • Assign named guests to tables with keep-together and keep-apart rules and get a shareable chart
  • Build a minute-by-minute wedding day schedule from a ceremony start time
  • Split a total budget or guest count into categories with per-guest math and a contingency line
  • Return a view-only link for each result so the user can keep editing
When to use it
Useful when someone is planning a wedding and wants quick, structured help with venue fit, seating arrangements, the day-of schedule, or a category budget split. It is not for long-range planning checklists, vendor payment tracking, or actual spending records.
Requirements
A remote streamable HTTP endpoint; no login, API key, or environment variables are declared. Inputs use feet and US dollars.
Before you install
Results are planning estimates, not quotes or bookings, and the server explicitly does not cover pricing or purchases. Each result produces a view-only link, so plan details are shared with the service. Budget output is a suggested split, not a record of real spending.

Installation

In SourceWeft

  1. Open Altessa Wedding Planner in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/studio.altessa%2Faltessa/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "altessa-wedding-planner": {
      "type": "http",
      "url": "https://mcp.altessa.studio/mcp"
    }
  }
}

Tools

4

plan_reception_layout

Reception layout planner

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, returns the space required instead of a fit check). Do not use for ceremony seating, seating assignments by name (use generate_seating_chart), or venue search.

Parametersbarscake_tablehead_tabledance_floorguest_countrequiredtable_shapefood_serviceentertainmentroom_width_ftroom_length_ftseats_per_table

generate_seating_chart

Seating chart generator

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 floor plans without names (use plan_reception_layout) or for RSVP tracking.

Parametersguestsrequiredkeep_aparttable_countfill_strategykeep_togetherseats_per_tablehead_table_names

build_wedding_timeline

Wedding day timeline builder

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.

Parameterslocationsend_offfirst_looksame_venuewedding_dateceremony_timerequiredtravel_minutesreception_hoursceremony_minutesphoto_prioritiescocktail_hour_minuteshair_and_makeup_people

estimate_wedding_budget

Wedding budget breakdown

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.

Parametersstyleregionprioritiesguest_counttotal_budget_usd

Version history

1
  1. v1.0.0LatestOct 26, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.