MCP server for interacting with Bazos.cz and Bazos.sk
Bazos MCP server exists for a simple reason — assistants are far more useful when they can act on Bazos directly instead of describing what you should do. MCP server for interacting with Bazos.cz and Bazos.sk.
Arguments: - domain: "cz", "sk", "at", or "pl" - section: Section code (e.g. AU for Auto) - query: Search query string - price_from: Minimum price - price_to: Maximum price - sort: date, price_asc, price_desc, distance - latitude / longitude: Required when sort is distance - offset: Pagination offset (multiples of 20) - limit: Page size (multiples of 20, max 200)
Once Bazos is connected, these are the calls the assistant has available:
search_ads — Arguments: - domain: "cz", "sk", "at", or "pl" - section: Section code (e.g. AU for Auto) - query: Search query string - price_from: Minimum price -get_ad_detail — The get_ad_detail tool exposed by this serverget_user_ratings — Arguments: - domain: "cz", "sk", "at", or "pl" - phone: Phone ID - email: Email ID - offset: Pagination offset - limit: Page size@andrijdavid/bazos-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of team communication servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Bazos's toolset — search_ads, get_ad_detail, get_user_ratings — is a fair guide to whether it matches your workflow. It is maintained by andrijdavid; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| search_ads | Arguments: - domain: "cz", "sk", "at", or "pl" - section: Section code (e.g. AU for Auto) - query: Search query string - price_from: Minimum price - price_to: Maximum price - sort: date, price_asc, price_desc, distance - |
| get_ad_detail | The get_ad_detail tool exposed by this server. |
| get_user_ratings | Arguments: - domain: "cz", "sk", "at", or "pl" - phone: Phone ID - email: Email ID - offset: Pagination offset - limit: Page size |
{
"mcpServers": {
"bazos": {
"command": "npx",
"args": ["-y", "@andrijdavid/bazos-mcp"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.