MCP server for Yandex Search API (web, image, generative, wordstat).
Most search and retrieval work still happens through a UI a human drives. Yandex Searchapi MCP MCP server moves it into the conversation instead. MCP server for Yandex Search API (web, image, generative, wordstat).
MCP server for Yandex Search API over REST with 7 tools: - web_search - image_search - generative_search - wordstat_get_top - wordstat_get_dynamics - wordstat_get_regions_distribution - wordstat_get_regions_tree
The server publishes 8 tools. What each one is for:
web_search — image_searchgenerative_search — wordstat_get_topwordstat_get_dynamics — wordstat_get_regions_distributionFOLDER_ID — API_KEYimage_search — Use this tool when you need image search results and image metadata (thumbnail/original links and dimensions)wordstat_get_top — Use this tool to understand what related queries users search for around a keywordwordstat_get_regions_distribution — Use this tool to see in which regions/cities a keyword is relatively more popularwordstat_get_regions_tree — Use this tool to get valid region IDs and names for regional Wordstat filtersConfiguration is passed through the environment: FOLDER_ID, API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
yandex-searchapi-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of search and retrieval 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. Yandex Searchapi MCP's toolset — web_search, generative_search, wordstat_get_dynamics and 5 more — is a fair guide to whether it matches your workflow. It is maintained by shufl9dka; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| web_search | image_search |
| generative_search | wordstat_get_top |
| wordstat_get_dynamics | wordstat_get_regions_distribution |
| FOLDER_ID | API_KEY |
| image_search | Use this tool when you need image search results and image metadata (thumbnail/original links and dimensions). |
| wordstat_get_top | Use this tool to understand what related queries users search for around a keyword. |
| wordstat_get_regions_distribution | Use this tool to see in which regions/cities a keyword is relatively more popular. |
| wordstat_get_regions_tree | Use this tool to get valid region IDs and names for regional Wordstat filters. |
## MCP client config example
```json
{
"mcpServers": {
"yandex-searchapi": {
"command": "npx",
"args": ["-y", "yandex-searchapi-mcp"],
"env": {
"FOLDER_ID": "your-folder-id",
"API_KEY": "your-api-key"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| FOLDER_ID | Configuration value read at startup. | Optional |
| API_KEY | Credential the server authenticates with. | Yes |
The simplest web tool that matters — fetch any URL and get model-ready markdown back.
Industrial-strength web extraction — render, scrape, crawl and search entire sites into clean markdown.
Puppeteer-powered browser control that drives pages from the accessibility tree instead of pixels.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Put 6,000+ pre-built scrapers at your assistant's fingertips through one MCP endpoint.