PartyPlan MCP

PartyPlan provides MCP tools for AI assistants to manage party planning tasks. It allocates budgets across categories like venue and food, estimates headcount and supplies, generates countdown timelines, and creates tailored checklists. It performs pure arithmetic and drafting without handling bookings or payments.

Visit MagicTeams

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Community listingStreamable HTTPNo sign-inEndpoint checked 2026-11-07Published by MagicTeams

MCP endpoint (Streamable HTTP)

https://party-plan.magicteams.ai/mcp

Vendor documentation

What its tools do

4 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

4 of 4 have a description · 4 of 4 declare behavior hints · 4 of 4 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 7, 2026, 12:54 AM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Allocate a total party budget across seven categories by spending style
Estimate expected attendance and food quantities from an invite list
Build a dated countdown plan with task lists leading up to the event
Generate a supplies and prep checklist grouped by area and extras

Source and maintenance

Community listingRegistry 1.0.0

mcp-registry: io.github.everyai-com/party-plan@1.0.0 Source repository

Maintenance checked: Nov 7, 2026, 12:20 AM UTC

Protocol and capabilities

Server: party-plan 1.0.0
MCP protocol negotiated in check: 2025-11-25
Tools: 4 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

PartyPlan allocates a party budget across categories, turns an invite list into expected attendance and shopping quantities, builds a dated countdown timeline, and prepares a venue-aware checklist for home or venue parties. All maths only; nothing stored.

Tools

4 advertised

party_budget — Party budget

Advertised by the server during the last successful anonymous check.

Advertised read-only

Allocate a total party budget (USD) across seven categories (venue, food and drink, cake, decorations, entertainment, favors, contingency) by spending style, with per-guest spend and saving tips. Use when deciding what to spend before booking. Do NOT use to estimate attendance or food quantities (use headcount_plan).

party_budget input schema

{
  "type": "object",
  "required": [
    "budget",
    "guests"
  ],
  "properties": {
    "style": {
      "enum": [
        "budget",
        "standard",
        "premium"
      ],
      "type": "string",
      "description": "Spending style that sets the category percentages: 'budget', 'standard' (default) or 'premium'"
    },
    "budget": {
      "type": "number",
      "description": "Total party budget in USD, positive, e.g. 600"
    },
    "guests": {
      "type": "integer",
      "maximum": 500,
      "minimum": 1,
      "description": "Number of guests, whole number 1-500, e.g. 30"
    }
  }
}

party_budget output schema

{
  "type": "object",
  "required": [
    "currency",
    "budget",
    "guests",
    "per_guest_budget",
    "allocation",
    "note"
  ],
  "properties": {
    "note": {
      "type": "string",
      "description": "Plain-language summary of the allocation"
    },
    "budget": {
      "type": "number",
      "description": "Total budget, rounded to cents"
    },
    "guests": {
      "type": "integer",
      "description": "Guest count used"
    },
    "currency": {
      "type": "string",
      "description": "Currency of all amounts, always USD"
    },
    "allocation": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "category",
          "percent",
          "amount",
          "tips"
        ],
        "properties": {
          "tips": {
            "type": "string",
            "description": "Saving tip for this category"
          },
          "amount": {
            "type": "number",
            "description": "USD allocated to this category"
          },
          "percent": {
            "type": "number",
            "description": "Percent of the budget for this category"
          },
          "category": {
            "enum": [
              "venue",
              "food_drink",
              "cake",
              "decorations",
              "entertainment",
              "favors",
              "contingency"
            ],
            "type": "string",
            "description": "Budget category key"
          }
        }
      },
      "description": "Budget split per category; amounts sum to the budget"
    },
    "per_guest_budget": {
      "type": "number",
      "description": "Total budget divided by guests, rounded to cents"
    }
  }
}

party_budget annotations

{
  "title": "Party budget",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

headcount_plan — Headcount plan

Advertised by the server during the last successful anonymous check.

Advertised read-only

Estimate how many invited guests will attend (adults vs children) and the food, drink, cake, favor and plate quantities to buy, with standard buffers. Use when sizing the shopping list from an invite count. Do NOT use for spending (use party_budget) or a dated to-do plan (use party_timeline).

headcount_plan input schema

{
  "type": "object",
  "required": [
    "invited"
  ],
  "properties": {
    "invited": {
      "type": "integer",
      "maximum": 1000,
      "minimum": 1,
      "description": "People invited, whole number 1-1000, e.g. 40"
    },
    "children_pct": {
      "type": "number",
      "maximum": 100,
      "minimum": 0,
      "description": "Percent of attendees who are children, 0-100, default 0"
    },
    "expected_decline_pct": {
      "type": "number",
      "maximum": 100,
      "minimum": 0,
      "description": "Percent of invitees expected to decline, 0-100, default 15"
    }
  }
}

headcount_plan output schema

{
  "type": "object",
  "required": [
    "invited",
    "expected_attendees",
    "adults",
    "children",
    "quantities",
    "note"
  ],
  "properties": {
    "note": {
      "type": "string",
      "description": "Plain-language explanation of the estimate and buffers"
    },
    "adults": {
      "type": "integer",
      "description": "Expected adult attendees"
    },
    "invited": {
      "type": "integer",
      "description": "Number of people invited"
    },
    "children": {
      "type": "integer",
      "description": "Expected child attendees"
    },
    "quantities": {
      "type": "object",
      "required": [
        "mains_portions",
        "drinks",
        "cake_slices",
        "favors",
        "plates"
      ],
      "properties": {
        "drinks": {
          "type": "integer",
          "description": "Drinks (2.5 per adult, 1.5 per child)"
        },
        "favors": {
          "type": "integer",
          "description": "Party favors (10% extra)"
        },
        "plates": {
          "type": "integer",
          "description": "Plates (25% extra)"
        },
        "cake_slices": {
          "type": "integer",
          "description": "Cake slices (20% extra)"
        },
        "mains_portions": {
          "type": "integer",
          "description": "Main-course portions (15% extra per adult, 0.75 per child)"
        }
      },
      "description": "Shopping quantities including buffers"
    },
    "expected_attendees": {
      "type": "integer",
      "description": "Expected attendance after declines (rounded up)"
    }
  }
}

headcount_plan annotations

{
  "title": "Headcount plan",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

party_timeline — Party timeline

Advertised by the server during the last successful anonymous check.

Advertised read-only

Build a dated countdown plan for a party, with task lists at 6 weeks, 4, 3, 2 and 1 week, 3 days, the day before and the day itself. Use when the date is set and the host needs to know what to do when. Do NOT use for spending (use party_budget) or a categorized supplies list (use party_checklist).

party_timeline input schema

{
  "type": "object",
  "required": [
    "event_date"
  ],
  "properties": {
    "guests": {
      "type": "integer",
      "maximum": 1000,
      "minimum": 1,
      "description": "Optional guest count 1-1000; adds a cake-sizing task at T-14"
    },
    "event_date": {
      "type": "string",
      "description": "Party date YYYY-MM-DD, e.g. 2026-12-20"
    },
    "event_type": {
      "type": "string",
      "description": "Optional event label added to the T-21 tasks, e.g. 'birthday', 'bbq' or 'kids party'"
    }
  }
}

party_timeline output schema

{
  "type": "object",
  "required": [
    "event_date",
    "milestones",
    "note"
  ],
  "properties": {
    "note": {
      "type": "string",
      "description": "How to read the milestone dates"
    },
    "event_date": {
      "type": "string",
      "description": "Party date YYYY-MM-DD"
    },
    "milestones": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "when",
          "date",
          "tasks"
        ],
        "properties": {
          "date": {
            "type": "string",
            "description": "Calendar date YYYY-MM-DD to finish these tasks by"
          },
          "when": {
            "type": "string",
            "description": "Offset label, e.g. 'T-14 days'"
          },
          "tasks": {
            "type": "array",
            "items": {
              "type": "string"
            },
            "description": "Tasks for this milestone"
          }
        }
      },
      "description": "Countdown milestones from T-42 days to the day itself"
    }
  }
}

party_timeline annotations

{
  "title": "Party timeline",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

party_checklist — Party checklist

Advertised by the server during the last successful anonymous check.

Advertised read-only

Generate a supplies and prep checklist grouped by area (food and drink, decorations, music and activities, practical, safety) for a home or venue party, with extra items for keywords like pool, bbq, costume, outdoor, kids, alcohol or potluck. Use when preparing what to buy and set up. Do NOT use for a dated plan (use party_timeline).

party_checklist input schema

{
  "type": "object",
  "required": [
    "venue"
  ],
  "properties": {
    "venue": {
      "enum": [
        "home",
        "venue"
      ],
      "type": "string",
      "description": "'home' for a party at home, 'venue' for a hired venue or hall"
    },
    "extras": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional keywords that add themed items: pool, bbq, costume, outdoor, kids, alcohol, potluck, e.g. [\"bbq\",\"kids\"]"
    }
  }
}

party_checklist output schema

{
  "type": "object",
  "required": [
    "venue",
    "checklist",
    "note"
  ],
  "properties": {
    "note": {
      "type": "string",
      "description": "Summary of venue adjustments and extras applied"
    },
    "venue": {
      "enum": [
        "home",
        "venue"
      ],
      "type": "string",
      "description": "Venue type the checklist was built for"
    },
    "checklist": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "area",
          "items"
        ],
        "properties": {
          "area": {
            "enum": [
              "food_drink",
              "decorations",
              "music_activities",
              "practical",
              "safety"
            ],
            "type": "string",
            "description": "Checklist area"
          },
          "items": {
            "type": "array",
            "items": {
              "type": "string"
            },
            "description": "Items to buy or do for this area"
          }
        }
      },
      "description": "Checklist items grouped by area"
    }
  }
}

party_checklist annotations

{
  "title": "Party checklist",
  "readOnlyHint": true,
  "openWorldHint": false,
  "idempotentHint": true,
  "destructiveHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 201 ms
95th percentile latency: 201 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 7, 2026, 12:54 AM UTC · probe · passed · 201 ms · metadata changed · 4 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http partyplan-mcp https://party-plan.magicteams.ai/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add partyplan-mcp --url https://party-plan.magicteams.ai/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable partyplan-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "partyplan-mcp": {
      "url": "https://party-plan.magicteams.ai/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "partyplan-mcp": {
      "type": "streamableHttp",
      "url": "https://party-plan.magicteams.ai/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start partyplan-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "partyplan-mcp": {
      "type": "http",
      "url": "https://party-plan.magicteams.ai/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http partyplan-mcp https://party-plan.magicteams.ai/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.

Claude Desktop configuration

https://party-plan.magicteams.ai/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "partyplan-mcp": {
      "serverUrl": "https://party-plan.magicteams.ai/mcp"
    }
  }
}

Let your agent find its tools

Find servers like PartyPlan MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

See all 5,453

PartyPlan MCP

Endpoint and access

What its tools do

Read-only (4)

Checks and signals

What you can do with it

Source and maintenance

Protocol and capabilities

Server-provided instructions

Tools

Prompts

Resources

30-day availability

Maintenance history

Connect from your client

Claude Code

Codex

Cursor

Cline

VS Code

Gemini CLI

Claude Desktop

Windsurf

Let your agent find its tools

Other productivity and knowledge servers