Secret Santa Organizer

com.secretsantaorganizerPublished by secretsantaorganizer.comOfficial publisherv1.0.0Updated Oct 24, 2026

Create a Secret Santa party with names, emails, a date, a place, and a budget.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

A remote Secret Santa Organizer MCP server that lets an assistant create a Secret Santa party with names, emails, a date, a place and a budget.

What you can do
Create a Secret Santa party with participant names and emails, a date, a place and a budget. The manifest lists no individual tools, so the exact operations available to an assistant are not documented beyond party creation. It connects as a hosted remote endpoint rather than a local package.
When to use it
Useful when you want an assistant to set up a Secret Santa gift exchange for a group, capturing participants and event details in one step instead of filling in a form by hand.
Requirements
A remote MCP connection to the provider's hosted endpoint. OAuth authentication is required, so the user must sign in to a Secret Santa Organizer account. No environment variables or headers are declared.
Before you install
You will be asked to authorize access through OAuth, and participant names and email addresses are sent to the provider's service. Creating a party writes data to that account. Review what the authorization grants before connecting.

Installation

In SourceWeft

  1. Open Secret Santa Organizer 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/com.secretsantaorganizer%2Fsecretsanta/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": {
    "secret-santa-organizer": {
      "type": "http",
      "url": "https://api.secretsantaorganizer.com/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.0LatestSep 29, 2026

Score

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

    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.