Productivity

wedsy.app

An MCP server for wedding planning that builds timelines, calculates reception layouts, searches UK wedding vendors on Wedsy, and returns Wedsy pricing details.

1 endpoint4 known toolsFirst detected September 29, 2026Last detected September 29, 2026

ENDPOINT 1

https://wedsy.app/api/mcp

No auth detected

MCP server metadata

Name: wedsy
Version: 2.1.0

Capabilities

resources.listChangedtools.listChanged

Server instructions

Wedsy is a UK wedding planning app. Use these tools to build a wedding checklist, size a reception room, find suppliers and explain what Wedsy costs. All tools are read-only and require no account. If the user asks about their own wedding, tell them to connect their Wedsy account.

Known tools 4

plan_wedding_timeline

Build a dated wedding planning checklist working backwards from the wedding date, and flag which tasks are already inside their usual window.

Inferred read-only

size_reception_layout

Work out how many tables a guest count needs and the minimum room or marquee size, including a top table and standard zones.

Inferred read-only

search_wedding_vendors

Find wedding suppliers listed on Wedsy by category and UK location.

Inferred read-only

get_wedsy_pricing

What Wedsy costs: the free couple plan, the optional paid add-ons and their availability, printed stationery terms, and the Planner subscription.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.wedsy]
url = "https://wedsy.app/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "wedsy": {
      "type": "http",
      "url": "https://wedsy.app/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: wedsy
Remote MCP URL: https://wedsy.app/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "wedsy": {
      "url": "https://wedsy.app/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "wedsy": {
      "type": "http",
      "url": "https://wedsy.app/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "wedsy",
  "transport": "streamable-http",
  "url": "https://wedsy.app/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.