API Tools
livuma.com
Provides tools to search and retrieve property listings and knowledge base information from Livuma's platform.
ENDPOINT 1
https://livuma.com/mcp
MCP server metadata
- Name
- livuma
- Version
- 1.0
Known tools 4
search_knowledgeSearch Livuma's public knowledge base (FAQs, policies, how booking/payments/payouts work, platform fees, verification) by natural-language question.
Inferred read-onlyget_search_optionsList valid values for search_listings parameters: property types, common areas, currencies, price periods, and amenity names.
Inferred read-onlyget_listing_detailsGet full public details for one listing: description insights, all rates and minimum stays, amenities, location, and the publicUrl to send the user to.
Potential side effectsCONNECT 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.livuma]
url = "https://livuma.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"livuma": {
"type": "http",
"url": "https://livuma.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: livuma
Remote MCP URL: https://livuma.com/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": {
"livuma": {
"url": "https://livuma.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"livuma": {
"type": "http",
"url": "https://livuma.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "livuma",
"transport": "streamable-http",
"url": "https://livuma.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for livuma.com was fetched 2026-08-04T03:54:43.101Z and is being refreshed.
livuma.com is assessed as Trusted: Domain runs a meaningful technology spend, consistent with a real business.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.