Connect AI assistants to WedStay's wedding venue and vendor data via the Model Context Protocol. No API key required for search and pricing.

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 8 tools to AI assistants:

Read tools (no authentication required)

Tool	Description
`search_venues`	Search wedding venues by state, city, capacity, venue type, and amenities. Returns up to 20 results with pricing, photos, and booking links.
`get_venue`	Get full details for a venue by slug — description, capacity, pricing, preview photos, testimonials, and direct booking link.
`calculate_pricing`	Estimate total wedding costs by region, guest count, venue type, and season. Shows savings vs. traditional venues.
`search_vendors`	Search vendors across 12 categories by location, price, and keyword.
`get_vendor`	Get vendor profile including bio, pricing, website, Instagram, and contact link.
`list_vendor_categories`	Get all vendor categories with active vendor counts.

Write tools (require valid guest contact info)

Tool	Description
`submit_venue_inquiry`	Submit a real booking request. A WedStay concierge responds within 24 hours.
`submit_vendor_inquiry`	Send a contact request to a vendor. They typically respond within 48 hours.

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

Parameter	Type	Required	Description
`state`	string	No	State name (e.g. "Texas", "California")
`city`	string	No	City name (e.g. "Austin", "Palm Springs")
`venue_type`	string	No	estate, villa, ranch, barn, resort, winery, garden, historic, cabin, castle, compound
`capacity_min`	number	No	Minimum guest capacity
`capacity_max`	number	No	Maximum guest capacity
`amenities`	string	No	Comma-separated: pool, hot-tub, ocean-view, outdoor-ceremony, pet-friendly

get_venue

Parameter	Type	Required	Description
`slug`	string	Yes	Venue URL slug from search results

calculate_pricing

Parameter	Type	Required	Description
`region`	string	Yes	State name: California, New York, Texas, Florida, Michigan, Colorado, North Carolina, Tennessee, Georgia, Utah
`event_type`	string	No	`weekday` or `weekend` (default: weekend)
`event_guests`	number	No	20-300 (default: 100)
`overnight_guests`	number	No	10-100 (default: 20)
`nights`	number	No	2-7 (default: 2)
`venue_type`	string	No	barn, estate, resort, winery, garden, historic, ranch, villa (default: estate)
`season`	string	No	peak, shoulder, off (default: peak)

search_vendors

Parameter	Type	Required	Description
`category`	string	No	Service category (e.g. "Photography", "Catering")
`state`	string	No	State name
`city`	string	No	City name
`search`	string	No	Free-text search
`price_max`	number	No	Maximum starting price (USD)

get_vendor

Parameter	Type	Required	Description
`slug`	string	Yes	Vendor URL slug from search results

submit_venue_inquiry

Parameter	Type	Required	Description
`property_slug`	string	Yes	Venue slug
`start_date`	string	Yes	Check-in date (YYYY-MM-DD)
`end_date`	string	Yes	Check-out date (YYYY-MM-DD)
`event_guests`	number	Yes	Number of event guests
`overnight_guests`	number	No	Overnight guests
`guest_name`	string	Yes	Guest full name
`guest_email`	string	Yes	Guest email
`guest_phone`	string	No	Phone number
`message`	string	No	Additional details

submit_vendor_inquiry

Parameter	Type	Required	Description
`vendor_slug`	string	Yes	Vendor slug
`guest_name`	string	Yes	Guest full name
`guest_email`	string	Yes	Guest email
`guest_phone`	string	No	Phone number
`event_date`	string	No	Event date (YYYY-MM-DD)
`event_location`	string	No	Event location
`event_guests`	number	No	Guest count
`budget_range`	string	No	Budget range
`service_needed`	string	No	Specific service
`message`	string	No	Message for the vendor

How it works

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

The client sends an initialize request to establish a session
The server responds with available tools and capabilities
The client calls tools as needed — each tool call is a separate HTTP POST
Read tools query WedStay's database directly and return structured JSON
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.

MCP Server

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 8 tools to AI assistants:

Read tools (no authentication required)

Tool	Description
`search_venues`	Search wedding venues by state, city, capacity, venue type, and amenities. Returns up to 20 results with pricing, photos, and booking links.
`get_venue`	Get full details for a venue by slug — description, capacity, pricing, preview photos, testimonials, and direct booking link.
`calculate_pricing`	Estimate total wedding costs by region, guest count, venue type, and season. Shows savings vs. traditional venues.
`search_vendors`	Search vendors across 12 categories by location, price, and keyword.
`get_vendor`	Get vendor profile including bio, pricing, website, Instagram, and contact link.
`list_vendor_categories`	Get all vendor categories with active vendor counts.

Write tools (require valid guest contact info)

Tool	Description
`submit_venue_inquiry`	Submit a real booking request. A WedStay concierge responds within 24 hours.
`submit_vendor_inquiry`	Send a contact request to a vendor. They typically respond within 48 hours.

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

Parameter	Type	Required	Description
`state`	string	No	State name (e.g. "Texas", "California")
`city`	string	No	City name (e.g. "Austin", "Palm Springs")
`venue_type`	string	No	estate, villa, ranch, barn, resort, winery, garden, historic, cabin, castle, compound
`capacity_min`	number	No	Minimum guest capacity
`capacity_max`	number	No	Maximum guest capacity
`amenities`	string	No	Comma-separated: pool, hot-tub, ocean-view, outdoor-ceremony, pet-friendly

get_venue

Parameter	Type	Required	Description
`slug`	string	Yes	Venue URL slug from search results

calculate_pricing

Parameter	Type	Required	Description
`region`	string	Yes	State name: California, New York, Texas, Florida, Michigan, Colorado, North Carolina, Tennessee, Georgia, Utah
`event_type`	string	No	`weekday` or `weekend` (default: weekend)
`event_guests`	number	No	20-300 (default: 100)
`overnight_guests`	number	No	10-100 (default: 20)
`nights`	number	No	2-7 (default: 2)
`venue_type`	string	No	barn, estate, resort, winery, garden, historic, ranch, villa (default: estate)
`season`	string	No	peak, shoulder, off (default: peak)

search_vendors

Parameter	Type	Required	Description
`category`	string	No	Service category (e.g. "Photography", "Catering")
`state`	string	No	State name
`city`	string	No	City name
`search`	string	No	Free-text search
`price_max`	number	No	Maximum starting price (USD)

get_vendor

Parameter	Type	Required	Description
`slug`	string	Yes	Vendor URL slug from search results

submit_venue_inquiry

Parameter	Type	Required	Description
`property_slug`	string	Yes	Venue slug
`start_date`	string	Yes	Check-in date (YYYY-MM-DD)
`end_date`	string	Yes	Check-out date (YYYY-MM-DD)
`event_guests`	number	Yes	Number of event guests
`overnight_guests`	number	No	Overnight guests
`guest_name`	string	Yes	Guest full name
`guest_email`	string	Yes	Guest email
`guest_phone`	string	No	Phone number
`message`	string	No	Additional details

submit_vendor_inquiry

Parameter	Type	Required	Description
`vendor_slug`	string	Yes	Vendor slug
`guest_name`	string	Yes	Guest full name
`guest_email`	string	Yes	Guest email
`guest_phone`	string	No	Phone number
`event_date`	string	No	Event date (YYYY-MM-DD)
`event_location`	string	No	Event location
`event_guests`	number	No	Guest count
`budget_range`	string	No	Budget range
`service_needed`	string	No	Specific service
`message`	string	No	Message for the vendor

How it works

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

The client sends an initialize request to establish a session
The server responds with available tools and capabilities
The client calls tools as needed — each tool call is a separate HTTP POST
Read tools query WedStay's database directly and return structured JSON
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.

MCP Server

On this page

MCP Server

On this page