invitas

io.github.invitas-coPublished by GitHub account invitas-cov1.0.0Updated Oct 29, 2026

Manage digital invitations, guest lists, RSVPs and seating for weddings and events.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Official invitas.co connector that lets an assistant create and manage event invitations, guest lists, RSVPs and table seating through conversation.

What you can do
  • Browse templates, list, create, update, publish, unpublish, duplicate and export events
  • Add event images, custom sections and custom fields
  • List, read, add, update, remove, import and export guests and their RSVPs
  • Read and update seating charts, assign or unassign guests to tables
  • Read and moderate wall messages, prepare reminders and get event statistics
  • Search and fetch guidance content for the connector
When to use it
Useful when you plan a wedding or event on invitas.co and want to check RSVP counts, adjust guest lists, edit invitation details or rearrange tables from a chat client instead of the dashboard.
Requirements
A remote Streamable HTTP endpoint at invitas.co/mcp; no local package needed. An invitas.co account, with OAuth 2.1 (PKCE) sign-in and consent, or a personal access token sent as an Authorization Bearer header for clients that support bearer headers.
Before you install
The assistant can read guest contact details, invitation links, wall messages and reminders, and that data may be shared with the assistant provider. Write tools create, update, publish, remove guests and change seating, and wall messages can be moderated. Grant only the scopes you need and disconnect in Mi cuenta when done.

Installation

In SourceWeft

  1. Open invitas in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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/io.github.invitas-co%2Finvitas-mcp/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "invitas": {
      "type": "http",
      "url": "https://invitas.co/mcp"
    }
  }
}

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).

mermaid
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)

json
{  "mcpServers": {    "invitas": {      "command": "npx",      "args": [        "-y",        "@modelcontextprotocol/server-sse",        "https://invitas.co/mcp"      ]    }  }}

Cursor (.cursor/mcp.json)

json
{  "mcpServers": {    "invitas": {      "url": "https://invitas.co/mcp"    }  }}

Direct HTTP Request Example

sh
# Discover available toolscurl -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.

Source: README.md at commit f661bcc

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

85% 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 listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts