WedKit

ca.wedkitPublished by wedkit.caOfficial publisherv1.0.0Updated Oct 26, 2026

Run your wedding from Claude or ChatGPT: guests, RSVPs, meals, seating and your wedding site.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

WedKit connects an AI assistant to a wedding planning account so it can work with guests, RSVPs, meals, seating and the wedding site.

What you can do
  • Manage the guest list and RSVP responses for a wedding.
  • Track meal choices and arrange seating.
  • Work on the wedding website from the assistant.
  • No individual tools are documented, so the exact actions available are not specified.
When to use it
Useful for couples or planners already using WedKit who want to update guest details, check RSVPs, or adjust meals and seating through an AI assistant instead of the web interface.
Requirements
A remote MCP endpoint at wedkit.ca reached over streamable HTTP, with OAuth sign-in required. No packages, environment variables or headers are declared.
Before you install
The server requires OAuth access to a wedding planning account holding guest and RSVP data, so review the scopes granted. Actions may change or delete guest, meal and seating records; the specific tools and permissions are not documented here.

Installation

In SourceWeft

  1. Open WedKit 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/ca.wedkit%2Fwedkit/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": {
    "wedkit": {
      "type": "http",
      "url": "https://wedkit.ca/api/mcp"
    }
  }
}

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 21, 2026

Score

56% 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

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.