Latido Wedding MCP MCP server

An official MCP server provided by Latido that allows AI assistants to interact with the Hungarian wedding marketplace. It enables agents to search for vendors and venues, check availability, estimate budgets based on guest count and region, and retrieve planning checklists without requiring user authentication, reading only public marketplace data.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Latido

MCP endpoint (Streamable HTTP)

https://latido.wedding/mcp

Vendor documentation

What you can do with it

Search wedding vendors and venues by category, location, or date
Check vendor availability for specific dates
Estimate wedding budget based on guest count and region
Retrieve a personalized wedding planning checklist

Tools advertised by the last live check:

search_vendors
get_vendor
list_categories_and_regions
check_availability
estimate_budget
wedding_checklist
search
fetch

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 a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http latido-wedding-mcp https://latido.wedding/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 latido-wedding-mcp --url https://latido.wedding/mcp

Cursor

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

Cursor configuration

{
  "mcpServers": {
    "latido-wedding-mcp": {
      "url": "https://latido.wedding/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "latido-wedding-mcp": {
      "type": "streamableHttp",
      "url": "https://latido.wedding/mcp",
      "disabled": false
    }
  }
}

VS Code

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

VS Code configuration

{
  "servers": {
    "latido-wedding-mcp": {
      "type": "http",
      "url": "https://latido.wedding/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 latido-wedding-mcp https://latido.wedding/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "latido-wedding-mcp": {
      "url": "https://latido.wedding/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": {
    "latido-wedding-mcp": {
      "serverUrl": "https://latido.wedding/mcp"
    }
  }
}

See all 1,687

Do you run Latido Wedding MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing