mcpField
I
invitas

invitas

Remote
invitas.coOther0Updated today

About invitas

invitas is an MCP connector for managing digital invitations and event details through conversational clients. Hosts can work with events, guests, RSVPs, seating, and related communications using its hosted service.

Key features

  1. 01Create and manage events
  2. 02Customize invitations and event sections
  3. 03Manage guest lists and RSVPs
  4. 04Assign guests to tables
  5. 05Moderate messages and prepare reminders

Use cases

  1. 01Organize a wedding guest list
  2. 02Update event details and invitations
  3. 03Track RSVPs and seating arrangements

MCP support

The hosted MCP server exposes 31 tools for events, guests, seating, and communications over Streamable HTTP. It supports OAuth 2.1 with PKCE or personal access tokens.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://invitas.co/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

invitas MCP connector

Español

invitas MCP Connector Protocol

Official Model Context Protocol (MCP) server for invitas.co. Create, customize, and manage your invitations, guest rosters, RSVPs, and table seating through conversation with Claude, ChatGPT, Cursor, and any MCP-compliant client.

Connector Endpoint: https://invitas.co/mcp (Streamable HTTP / JSON-RPC 2.0)


Architecture & Interaction Flow

The connector exposes 31 native tools via Streamable HTTP and JSON-RPC 2.0, authenticating requests via OAuth 2.1 (PKCE) or Personal Access Tokens (PAT).

sequenceDiagram
    autonumber
    actor User as Host / Developer
    participant Client as MCP Client (Claude / ChatGPT / Cursor)
    participant Connector as invitas MCP Server (https://invitas.co/mcp)
    participant App as invitas.co Core API

    User->>Client: "How many guests confirmed for my event?"
    Client->>Connector: POST /mcp (tools/call: list_guests)
    Connector->>App: GET /api/v1/events/{id}/guests (Bearer Token)
    App-->>Connector: 200 OK (guests & RSVPs payload)
    Connector-->>Client: 200 OK (JSON-RPC tool result)
    Client-->>User: "You have 26 confirmed guests out of 41 invited."

Tool Categories (31 Tools)

All tools are automatically catalogued from the core API specification. See Full Tool Catalogue for schemas and parameter details.

CategoryAvailable ToolsRequired Scopes
Discovery & Guidanceguide, search, fetchevents:read
Events & Templateslist_templates, list_events, get_event, create_event, update_event, publish_event, unpublish_event, duplicate_event, export_eventevents:read, events:write
Media & Sectionsadd_event_image, upsert_custom_section, set_custom_fieldsevents:read, events:write
Guests & RSVPslist_guests, get_guest, add_guest, update_guest, remove_guest, import_guests, export_guestsguests:read, guests:write
Seating & Tablesget_seating_chart, update_seating_chart, assign_guest_table, unassign_guest_tableseating:read, seating:write
Comms & Walllist_wall_messages, moderate_wall_message, prepare_reminder, get_event_statisticsevents:read, guests:read

Client Configuration Examples

Claude Desktop (claude_desktop_config.json)
{
  "mcpServers": {
    "invitas": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-sse",
        "https://invitas.co/mcp"
      ]
    }
  }
}
Cursor (.cursor/mcp.json)
{
  "mcpServers": {
    "invitas": {
      "url": "https://invitas.co/mcp"
    }
  }
}
Direct HTTP Request Example
# Discover available tools
curl -X POST https://invitas.co/mcp \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_PERSONAL_ACCESS_TOKEN" \
  -d '{"jsonrpc": "2.0", "id": 1, "method": "tools/list"}'

Supported Assistants

Step-by-step connection guides for every major client:


Sign-in and Permissions

The connector uses Streamable HTTP and OAuth 2.1 with PKCE and dynamic client registration. Sign in to invitas when prompted, then review the consent screen before authorising your assistant.

PermissionAccess
events:readRead events.
events:writeCreate and update events.
guests:readRead guest information.
guests:writeAdd and update guests.
seating:readRead table arrangements.
seating:writeUpdate table arrangements.

Terminal clients that support OAuth can use browser sign-in through the guides above. For clients that support bearer headers instead, create a personal access token in Mi cuenta, choose its permissions and send it in the Authorization: Bearer <token> header. See Other MCP clients and terminal for connection details.


What the Assistant Sees, and How to Disconnect

Within the permissions you authorise, your assistant can access the event information you see in your dashboard, including guest contact details, invitation links, wall messages, tables and prepared reminders. When you connect and authorise access, that information can be shared with your assistant provider, such as Anthropic for Claude or OpenAI for ChatGPT. To end access immediately, open Mi cuenta, select Apps conectadas, then Desconectar; changes already made are kept. See Data and permissions for details.


Examples

See example conversations for requests you can make, the tools involved and the results to expect.


Links


Repository Development

This repository contains documentation and a generated tool catalogue; the hosted connector runs in the invitas application. With Node.js 22 installed, run npm run check to verify that generated catalogue files match their source. Run npm run catalog after editing docs/catalog.source.json to regenerate them. See CONTRIBUTING.md.

The docs/ directory contains the catalogue and client guides, examples/ contains conversations, and scripts/ contains the catalogue generator. Changes to this repository publish documentation through the repository; deploying the hosted connector is handled by the application repository.


License

Documentation: CC BY 4.0.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.