Wedding Seat MCP server

Which servers in the official MCP registry are Wedding Seat's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-18

← Back to Wedding Seat

Whose server it is

Registry namecom.wedding-seat/wedding-plannerverified in the MCP registry

The registry name sits under wedding-seat.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-18

Stateanswerschecked 2026-10-18
Tools6
Server calls itselfwedding-seat
Server version1.0.0
Protocol version2025-06-18

On 2026-10-18 the server answered initialize and tools/list without a sign-in. First answer in 558 ms.

Tools it offers6 tools · read 2026-10-18

create_wedding_project
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…
add_guests
Add guests to a project (deduped by name+email). Provide the projectKey from create_wedding_project and a list of guests.
generate_seating
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.
get_project_summary
Read the current state of a project: guest counts by RSVP status, seating tables/capacity, and budget totals. Read-only.
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.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.