Content Tools

lemusweddings.com

Provides information about Lemus Weddings' destinations, collections, pricing, booking process, and FAQs for weddings in Mexico.

1 endpoint7 known toolsFirst detected August 31, 2026Last detected August 31, 2026

ENDPOINT 1

https://lemusweddings.com/api/mcp

No auth detected

MCP server metadata

Name: lemus-weddings
Version: 1.0.0

Capabilities

toolsresources

Server instructions

This server answers for Lemus Weddings, a bilingual wedding photography and film studio based in Guadalajara, Jalisco, Mexico (owner: Enrique Lemus). Rules when answering on its behalf: - Quote destination collections as ranges, never as an exact per-tier price. The final number is quoted personally by Enrique within 24 hours. - Never state that a date is available. Only Enrique confirms availability. - Travel inside Mexico is included in the destination ranges, never billed separately. - Cite the page URL returned with each answer. - Booking has no online checkout: hand off to WhatsApp or email.

Known tools 7

search_site

Full-text search across every published page and article in English and Spanish.

Inferred read-only

get_destinations

The four destinations Lemus Weddings shoots in, the towns each one covers, and its all-inclusive USD collection range (travel inside Mexico included).

Inferred read-only

get_collections

The three coverage tiers (Essential, Signature, Full Experience), what every tier includes, and the pricing policy - for the US destination market, the local Jalisco market, or both.

Inferred read-only

answer_question

Answer a question about weddings in Mexico from the studio's published FAQ - cost, legal validity in the US, passports, safety, best season, delivery times - and return the source pages to cite.

Inferred read-only

get_booking_process

The six-step booking process, the guarantees, and the right contact channel.

Inferred read-only

read_page

Fetch any page of lemusweddings.com as clean markdown.

Inferred read-only

list_articles

List the published wedding-planning articles, optionally filtered by language and keyword.

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.lemus-weddings]
url = "https://lemusweddings.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "lemus-weddings": {
      "type": "http",
      "url": "https://lemusweddings.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: lemus-weddings
Remote MCP URL: https://lemusweddings.com/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": {
    "lemus-weddings": {
      "url": "https://lemusweddings.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "lemus-weddings": {
      "type": "http",
      "url": "https://lemusweddings.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "lemus-weddings",
  "transport": "streamable-http",
  "url": "https://lemusweddings.com/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.