Wedtide wedding seating

Seat wedding guests at tables with keep-apart rules; returns an editable plan and seat finder.

¿Debería usar esto?

Calidad y seguridad

A
Calidad de la descripción
100%
Integridad del esquema
95%
Calidad de los nombres
90%
Riesgo de envenenamiento
100%
Coincidencia de permisos
100%
Cumplimiento del protocolo
100%

Basado en el análisis automatizado de las definiciones de herramientas y el cumplimiento del protocolo.

Costo de contexto

~748Tokens (definiciones de herramientas)
~2.3 KBTamaño de respuesta típico
Impacto moderado en la atención (0.58% del contexto de 128k)

Este es el número aproximado de tokens que se consumen cada vez que las herramientas del servidor se cargan en el contexto de un modelo. Los recuentos más altos reducen la atención disponible para otras tareas.

Instalar

Instalación con un clic

Agrega esto a tu archivo `claude_desktop_config.json`:

{
  "mcpServers": {
    "seating": {
      "url": "https://wedtide.com/api/mcp"
    }
  }
}

Puntos de conexión remotos

https://wedtide.com/api/mcpstreamable-http

Qué puede hacer

Inventario de herramientas

Herramientas (2)

🟢 Solo lectura🟡 Escritura🔴 Eliminación⚪ Desconocido
🟢create_seating_plan(guests, seats_per_table, rules, couple, setting)

Arrange a wedding guest list at tables and return a link that opens the plan in Wedtide. Use when the user shares a guest list (pasted names, a spreadsheet, CSV) and wants a seating chart or table assignments. Couples and families written on one line ("Ana & Luis", "The Smiths: John, Mary, Tim (kid)") are kept at the same table; rules keep named guests apart or together. Returns a short summary of who sits at each table and anything that could not be satisfied, plus two links: plan_url opens the full, editable plan in Wedtide (saved on the user's device; they can move people, view the room in 3D, print, export), and finder_url is a page guests open to type their name and see their seat. Nothing is stored on a server; the guest list is encoded in the link.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "guests": {
      "type": "string",
      "description": "The guest list as text. One party per line; \"&\", \"+\", \"and\" or commas join people who arrive together. A line ending in \":\" starts a group (\"Bride's family:\"). \"(kid)\" marks a child. A CSV or tab-separated sheet with a header row (name, party/household, group, age...) also works, e.g. exports from Zola, The Knot or Google Sheets."
    },
    "seats_per_table": {
      "type": "integer",
      "description": "Seats at each round table. Default 10.",
      "minimum": 2,
      "maximum": 30
    },
    "rules": {
      "type": "array",
      "description": "Requests about specific guests, by name as written in the list. \"apart\" keeps two guests at different tables (exes, feuding relatives); \"together\" seats them at the same table.",
      "items": {
        "type": "object",
        "properties": {
          "a": {
            "type": "string",
            "description": "A guest name."
          },
          "b": {
            "type": "string",
            "description": "Another guest name."
          },
          "kind": {
            "type": "string",
            "enum": [
              "apart",
              "together"
            ]
          }
        },
        "required": [
          "a",
          "b",
          "kind"
        ]
      }
    },
    "couple": {
      "type": "string",
      "description": "The couple's names, shown as the plan's title, e.g. \"Emma & James\"."
    },
    "setting": {
      "type": "string",
      "enum": [
        "ballroom",
        "vineyard",
        "garden",
        "beach"
      ],
      "description": "The look of the 3D room in Wedtide. Default ballroom."
    }
  },
  "required": [
    "guests"
  ]
}
🟢seating_tips(culture, guests)

Concise, practical wedding seating etiquette: head table or sweetheart table, where parents sit, divorced or feuding parents, kids tables, plus-ones, singles, and how many tables to plan. Use it when the user asks who should sit where or how to handle a delicate seating situation. Optional culture adds notes for some traditions; guests adds a table count.

Esquema de entrada

{
  "type": "object",
  "properties": {
    "culture": {
      "type": "string",
      "description": "Optional tradition or region, e.g. \"american\", \"jewish\", \"latin american\", \"indian\", \"chinese\". Unknown values get the general guidance."
    },
    "guests": {
      "type": "integer",
      "description": "Optional number of guests, for a table count.",
      "minimum": 1
    }
  }
}

Comunidad

Califica este servidor

Evidencia

Observaciones recientes

verificadoversión no registrada2 herramientas