MCP Server

WedStay provides a remote MCP (Model Context Protocol) server that gives AI assistants direct access to wedding venue search, real pricing, vendor discovery, and booking — all without requiring an API key for read operations.

MCP Endpoint:

https://www.thewedstay.com/api/ai/mcp

Connect your AI assistant

Claude Desktop

Add WedStay to your Claude Desktop configuration:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "wedstay": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://www.thewedstay.com/api/ai/mcp"]
    }
  }
}

Restart Claude Desktop after saving. You should see WedStay tools in the tools list.

Claude Code

Add to your project's .mcp.json:

{
  "mcpServers": {
    "wedstay": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://www.thewedstay.com/api/ai/mcp"]
    }
  }
}

Cursor

Add to your Cursor MCP settings (.cursor/mcp.json in your project or global settings):

{
  "mcpServers": {
    "wedstay": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://www.thewedstay.com/api/ai/mcp"]
    }
  }
}

Streamable HTTP (modern clients)

If your MCP client supports Streamable HTTP natively (no mcp-remote bridge needed):

{
  "mcpServers": {
    "wedstay": {
      "url": "https://www.thewedstay.com/api/ai/mcp"
    }
  }
}

Available tools

The MCP server exposes 12 tools to AI assistants:

Read tools (no authentication required)

Write tools (require valid guest contact info)

Write tools create real leads in WedStay's pipeline. The AI assistant must collect valid guest name, email, and event details before submitting.

Example conversations

Once connected, you can ask your AI assistant things like:

• "Find wedding venues in California that sleep at least 20 people"
• "How much would a 3-night wedding at an estate in Texas cost for 80 guests?"
• "Show me photographers in the Los Angeles area"
• "What's the starting price for Golden Hour Studios?"
• "Submit a booking request for Cedar Hill Farm for October 2026"

The AI will use WedStay tools automatically to answer with real, up-to-date data.

Tool reference

search_venues

Each result includes: slug, name, city, state, country, latitude, longitude, property_type, venue_type, capacity_min/max, bedrooms, beds, bathrooms, gathering_spaces, price_range, hero_image, amenities, and a bookable url.

get_venue

calculate_pricing

Returns typed structuredContent agents can render as comparison tables:

• estimated_total (number), per_night (number)
• price_range = { low, high, label }
• breakdown = { base_venue, cleaning_fee, event_guest_charge, overnight_guest_charge, additional_nights, season_adjustment, service_fee, tax }
• comparison_vs_traditional = { traditional_estimate, savings_dollars, savings_percent, note }
• parameters (echoed inputs, includes venue_type_label)
• summary (one-line for chat display), calculator_url (deep link into the live UI for further tweaking), attribution

search_vendors

Each result includes: slug, business_name, tagline, service_category, service_subcategories, primary_city/state, bio, starting_price, price_unit (per_person · per_event · per_hour · per_item), years_in_business, weddings_completed, specialties, featured_image_url, logo_url, is_affiliate_only, affiliate_link, and a profile url. get_vendor adds pricing_structure, website, instagram, facebook, tiktok, portfolio_description, vendor_policies (booking / payment / cancellation / timeline / insurance), average_rating, and review_count.

Affiliate-only vendors: when is_affiliate_only is true, submit_vendor_inquiry returns an affiliate_only_vendor error. Direct the user to affiliate_link instead.

get_vendor

submit_venue_inquiry

submit_vendor_inquiry

search_blog_posts

Each result includes: slug, title, excerpt, feature_image, published_at, reading_time, tags[], primary_author, and url.

get_blog_post

Returns plaintext body for token-efficient agent consumption: slug, title, feature_image, excerpt, published_at, reading_time, word_count, tags[], primary_author, content_plaintext, url.

list_blog_tags

No parameters. Returns an array of { slug, name, post_count } sorted by post count descending. Use to discover valid tag filters for search_blog_posts.

How it works

The WedStay MCP server uses the Streamable HTTP transport (MCP protocol revision 2025-06-18). When an AI assistant connects:

1. The client sends an initialize request to establish a session
2. The server responds with available tools and capabilities
3. The client calls tools as needed — each tool call is a separate HTTP POST
4. Read tools query WedStay's database directly and return structured JSON
5. Write tools (inquiries) create real leads that flow into WedStay's booking pipeline

No API key is required. The MCP server handles authentication and rate limiting at the session level.

Data attribution

All responses include an attribution notice. If you're building a product that surfaces WedStay data, please include visible attribution linking back to thewedstay.com.

Terms of use

By connecting to the WedStay MCP server, you agree to our Terms of Service, including Section 31 (API, MCP Server & Developer Access). Key restrictions:

• Real-time queries only — Each tool call must correspond to a specific end-user query. Batch processing and bulk extraction are prohibited.
• No AI training — Do not use WedStay data to train, fine-tune, or develop machine learning models or LLMs.
• No competing products — Do not use WedStay data to build competing venue search or booking services.
• No data harvesting — Do not scrape, store, or build databases from WedStay data.
• Attribution required — Display "Data by WedStay" when surfacing venue or vendor data to end users.