eCommerce
callstay.com
MCP server for Callstay that enables hotel searches, property details, and live room pricing for specified stays.
ENDPOINT 1
https://callstay.com/api/mcp
MCP server metadata
- Name
- callstay
- Version
- 0.1.0
Callstay sells hotel rooms worldwide with live rates and a human desk on the phone. Call `capabilities` first. Prices are decimal amounts in the stated currency and `total_all_in` includes every itemised fee. When `price_stay` returns no rooms, give the guest the phone number in `human_desk` rather than saying the hotel is full.
Known tools 4
capabilitiesWhat Callstay is, which tools exist, what prices mean, and the human desk's phone number.
Inferred read-onlyget_propertyFull detail for one property by slug: description, facilities, check-in and check-out times, parking, pets, children, policies, review summary and nearby places.
Inferred read-onlyprice_stayEvery room and rate one property has for an exact stay, live from the supplier.
Inferred read-onlyCONNECT 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.callstay]
url = "https://callstay.com/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"callstay": {
"type": "http",
"url": "https://callstay.com/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: callstay
Remote MCP URL: https://callstay.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": {
"callstay": {
"url": "https://callstay.com/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"callstay": {
"type": "http",
"url": "https://callstay.com/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "callstay",
"transport": "streamable-http",
"url": "https://callstay.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.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.