web_search_post is the one to use when the answer has to be checkable, since the sources come back with it; ai_search_post skips that and hands over Yazeka's summary. Access is the real gate: you have to already be a Yandex Search API customer, with a key carrying the yc.search-api.execute scope and a service account holding search-api.editor in the same folder.
Yandex's own MCP server for the Yandex Search API. Two tools run a real-time web search: one returns an answer with the sources behind it, the other returns an answer written by the Yazeka model over the same results.
- A real-time web search returning an answer with its sources
- A real-time web search returning an AI-generated answer from Yandex's Yazeka model
- A hosted endpoint reached over SSE, so nothing runs on your own machine
A Yandex Search API subscription, an API key carrying the yc.search-api.execute scope, and the folder id whose service account holds the search-api.editor role. Both are passed as headers when the client connects.
One command plus a key — npx -y mcp-remote https://d5de9siimt9bkld7viic.emzafcgx.apigw.yandexcloud.net:3000/sse, then supply credentials