ai_search_postLABSCO SUMMARY
Two ways to take the same results — cited, or already summarised.
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.
What it is
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.
What you get
- 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
Requirements
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.
Setup effort
Paste a URL with a key — add the endpoint to your client
USE CASES
01
Getting current facts a model's training data cannot cover
Run a live search and read the answer against sources published after the model was trained.
02
Backing a claim with links someone can check
Take the search answer together with its sources, so the citation is available when the claim is questioned.
03
Taking a fast answer when the sources are not the point
Ask Yazeka to answer over the search results directly, skipping the step of reading them.
04
Deciding how much to trust a generated answer
Run both: read the generated answer, then check it against the version that arrives with sources attached.
2 tools
Listed in project docs. Your client may show a different list.
web_search_postBEFORE YOU INSTALL
What to know first
Tools you get
2 tools named in the project's documentation.
Requires
- A Yandex Search API subscription
- A Yandex Search API key with the yc.search-api.execute scope (ApiKey header)
- Your folder id (FolderId header)
- npx on PATH for the Claude Desktop bridge
Where it runs
All 3 documented clients connect to a hosted endpoint.
INSTALLATION
Connect your client
Add the endpoint to your client.
Server setup
ENDPOINT URL
https://d5de9siimt9bkld7viic.emzafcgx.apigw.yandexcloud.net:3000/sseMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"yandexSearch": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://d5de9siimt9bkld7viic.emzafcgx.apigw.yandexcloud.net:3000/sse",
"--header",
"ApiKey:<YOUR_API_KEY>",
"--header",
"FolderId:<YOUR_FOLDER_ID>"
]
}
}
}Cursor
CURSOR · JSON
{
"mcpServers": {
"yandexSearch": {
"type": "sse",
"url": "https://d5de9siimt9bkld7viic.emzafcgx.apigw.yandexcloud.net:3000/sse",
"headers": {
"ApiKey": "<YOUR_API_KEY>",
"FolderId": "<YOUR_FOLDER_ID>"
}
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"yandexSearch": {
"type": "sse",
"url": "https://d5de9siimt9bkld7viic.emzafcgx.apigw.yandexcloud.net:3000/sse",
"headers": {
"ApiKey": "<YOUR_API_KEY>",
"FolderId": "<YOUR_FOLDER_ID>"
}
}
}
}
