olx-mcp-api
Related Servers
Alternatives to olx-mcp-api
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables searching and retrieving details from OLX classifieds across multiple domains (Portugal, Poland, Bulgaria, Romania, Ukraine) using browser automation.260 npm29MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for the OLX.ba API that enables searching, publishing, editing, and managing listings (ads), including image handling, sponsorships, categories, locations, and user account operations through 36 tools covering all official API endpoints.11 npm7MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for OLX marketplace. Enables AI assistants to search listings, get offer details, track prices over time, and compare offers across OLX Poland and other supported countries.60 npm4MIT
- AlicenseBqualityBmaintenanceEnables browser-free search and retrieval of Rozetka.ua product catalog data, including product search, batch hydration, filters, categories, URL resolution, and saved searches through public JSON backends.108 npmMIT
- FlicenseAqualityDmaintenanceExposes the OLX.ba marketplace API as MCP tools, enabling LLM clients to authenticate, browse and manage listings, read categories/attributes/locations, and run sponsorship/discount actions.35-
- AlicenseAqualityDmaintenanceEnables searching, viewing details, and filtering listings on Letgo.com by using Playwright to bypass Akamai anti-bot protection.61MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct role: search_offers finds listings, get_offer retrieves full details for one listing, and resolve_olx_url converts human-readable URLs into API parameters. There is no overlap in purpose, and the descriptions explicitly explain how the tools relate.
All tool names use consistent snake_case with a verb_noun structure: get_offer, resolve_olx_url, and search_offers. The inclusion of 'olx' in resolve_olx_url is a minor domain-specific detail but does not break the pattern.
Three tools is a well-scoped set for a read-only search API: one for discovery, one for detail retrieval, and one for input normalization. Each tool earns its place without redundancy.
The surface covers the core read-only workflow of resolving a URL, searching offers, and fetching offer details. Minor gaps exist, such as no direct category/city lookup tools, but resolve_olx_url provides a workaround for common cases.