mcp server
Wedding Seat
Anonymous, no-login wedding planning: create a project, add guests, auto-generate a seating plan.
Description as published by the maintainer. Source
- version 1.0.0
- archived
archived — The linked repository returns 404. It was deleted, renamed or made private.
What this server can do
6 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
add_guests(guests, projectKey)- Add guests to a project (deduped by name+email). Provide the projectKey from create_wedding_project and a list of guests. Required: projectKey, guests.
create_wedding_project(date, names, locale, culture)- Create a new anonymous Wedding Seat project (no login). Returns a projectKey (your secret handle for all later calls) plus the workspace URL the couple opens in a browser. The projectKey is the ONLY way to access the project again — keep it.
generate_seating(tables, projectKey, seatsPerTable)- Auto-generate a reception seating plan: creates round tables and seats every guest with the constraint-aware solver (keeps must-sit-together groups together). Returns how many were seated and a link to the visual editor. Required: projectKey.
get_project_summary(projectKey)- Read the current state of a project: guest counts by RSVP status, seating tables/capacity, and budget totals. Read-only. Required: projectKey.
list_culture_packs- List the available wedding culture packs (key, English name, cluster, sides). Use a pack key as the `culture` argument to create_wedding_project. Grounding/read-only.
list_tools- List Wedding Seat's free planning tools (seating chart, guest list, budget, checklist, invitation wording) with their public URLs. Grounding/read-only.
Last successful function declaration observed on . Source: https://mcp.wedding-seat.com/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://mcp.wedding-seat.com/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-16 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-16 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | not_found | GitHub returned 404 for the repository the maintainer listed. The project was deleted, renamed or made private, so the listing points at nothing. | as of fetch | GitHub | |
| mcp tools declared | 6 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | mcp.wedding-seat.com | |
| mcp endpoint status | ok | The server listed 6 functions when asked. | as of probe | mcp.wedding-seat.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json