OpenSERP MCP server with Yandex search

@openserp/mcp

An MCP server for the OpenSERP search platform: web and image search across several engines including Yandex, plus page text extraction

MCP server

Low risk

We rate an entry low when it mostly gives the agent instructions and reference material.

Why this level

  • The server only reads public search results and page content
All reasons and checks
Russian stack

openserpapi/mcp

Install

In your terminal, with SkillFoxx CLI

npx skillfoxx add mcp/openserp-mcp

Detects the agents on your machine, checks the risk and pins the version.

Other ways to install

Run in a terminal

claude mcp add --transport stdio openserp -- npx -y @openserp/mcp

Or add to the file .mcp.json, in the project

{
  "mcpServers": {
    "openserp": {
      "command": "npx",
      "args": [
        "-y",
        "@openserp/mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Install in Cursor

The button opens the agent and offers to add the server. If nothing happens, copy the config below.

Add to the file ~/.cursor/mcp.json, for all projects

{
  "mcpServers": {
    "openserp": {
      "command": "npx",
      "args": [
        "-y",
        "@openserp/mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key. For a single project, put the same block into .cursor/mcp.json.

Install in VS Code

The button opens the agent and offers to add the server. If nothing happens, copy the config below.

Run in a terminal

code --add-mcp '{"name":"openserp","type":"stdio","command":"npx","args":["-y","@openserp/mcp"]}'

Or add to the file .vscode/mcp.json, in the project

{
  "servers": {
    "openserp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@openserp/mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the servers key.

Run in a terminal

codex mcp add openserp -- npx -y @openserp/mcp

Or add to the file ~/.codex/config.toml, for all projects

[mcp_servers.openserp]
command = "npx"
args = ["-y", "@openserp/mcp"]

If the file already exists, append the block to the end.

Add to the file ~/.gemini/settings.json, for all projects

{
  "mcpServers": {
    "openserp": {
      "command": "npx",
      "args": [
        "-y",
        "@openserp/mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

Add to the file ~/.config/devin/mcp_config.json, for all projects

{
  "mcpServers": {
    "openserp": {
      "command": "npx",
      "args": [
        "-y",
        "@openserp/mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Legacy Cascade keeps the MCP config in ~/.codeium/windsurf/mcp_config.json.

Formerly Windsurf.

Add to the file cline_mcp_settings.json, for all projects

{
  "mcpServers": {
    "openserp": {
      "command": "npx",
      "args": [
        "-y",
        "@openserp/mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key. Open the settings file in Cline: MCP Servers tab, Configure MCP Servers.

Add to the file .roo/mcp.json, in the project

{
  "mcpServers": {
    "openserp": {
      "command": "npx",
      "args": [
        "-y",
        "@openserp/mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

A fork of Roo Code, same .roo folders.

Add to the file opencode.json, in the project

{
  "mcp": {
    "openserp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@openserp/mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcp key.

Add to the file ~/.config/zed/settings.json, for all projects

{
  "context_servers": {
    "openserp": {
      "command": "npx",
      "args": [
        "-y",
        "@openserp/mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the context_servers key.

Add to the file .codeassistant/mcp.json, in the project

{
  "mcpServers": {
    "openserp": {
      "command": "npx",
      "args": [
        "-y",
        "@openserp/mcp"
      ]
    }
  }
}

If the file already exists, add the server inside the mcpServers key.

You will need: Node.js

Checked against the repository on Sep 25, 2026, commit 8d35b47.

Text for your agent

Connect the server with npx -y @openserp/mcp --stdio; for cloud mode add the OPENSERP_API_KEY variable with a key from openserp.org/dashboard/keys.

Other ways from the author
npm install -g @openserp/mcp

Global install of the npm package.

This is third-party code. Review the repository files before installing.

What it does

The server provides ten tools on top of OpenSERP: regular, mega (across several engines at once), fast and any search, image search, clean text extraction from one URL or up to 20 at a time, checking remaining quota, and listing available engines. Yandex sits alongside Google and Bing among the engines, selected via the engine parameter in a call. Without OPENSERP_API_KEY the server runs in OSS mode against a local instance at localhost:7000; with a key it switches to OpenSERP Cloud.

Who it is for. For developers who want one search MCP server covering several engines including Yandex, with page text extraction for LLMs.

Good fit when

  • You need to compare Google, Bing and Yandex results in one request
  • You need to batch-extract clean markdown from up to 20 pages to ground an answer
  • You are fine with the OpenSERP Cloud plan or running your own OSS instance

Not a fit when

  • You only need Yandex: this is a general multi-engine server, not Yandex-specific
  • You lack a Cloud key and do not want to run an OSS instance: without one of the two the server will not work

Example request

Compare Google and Yandex results for this SEO keyword and extract text from the top three links

Limitations

OSS mode requires a separately running OpenSERP instance at localhost:7000, which this server's README does not describe how to set up. Cloud mode is paid, with a key issued at openserp.org. Yandex search depends on how OpenSERP implements that engine on its side; the details are not disclosed in this repository.

How to disable. Remove the openserp entry from mcpServers in your client configuration.

MCP

Transport
stdio, http, sse
Authentication
API key
Environment variables
Environment variables
OPENSERP_API_KEY
secret
OpenSERP Cloud key; without it the server runs in OSS mode
OPENSERP_BASE_URL
A compatible OpenSERP API base URL, if not the default

Security check

  • The server only reads public search results and page content

README in short

The README shows install via npm or npx, OSS and Cloud modes with different environment variables, a list of ten tools, examples comparing engines and geo-fenced search via the region parameter, and configs for Claude Desktop and Cursor in stdio and HTTP modes.

FAQ

Do I need a key for basic use?

No, without OPENSERP_API_KEY the server runs in OSS mode against localhost:7000, but that instance must be set up separately.

Can I search only Yandex?

Yes, pass engine set to Yandex's identifier in the search or image_search tools, or check list_engines for the exact name.

Editors’ pick

CLI, skill and Python library for browser control: the agent clicks, fills forms and reads pages over CDP

CLIHigh risk116.6KRepository stars
Editors’ pick

A skill that gathers the last 30 days of discussion on a topic from Reddit, X, YouTube, HN, Polymarket and GitHub into one brief

SkillHigh risk63.1KRepository stars
Official

The Chrome DevTools team's official MCP server: the agent drives a live Chrome, reads network and console, and records performance traces

MCP serverMedium risk52.7KRepository stars
Official

A fast Rust CLI for agent browser automation: accessibility snapshots with element refs, an MCP server and skills

CLIHigh risk43.3KRepository stars
Foxx AIOpenSERP MCP server with Yandex search

I am Foxx AI and I have already vetted this tool. Ask about install, setup or anything else, and I will keep it simple.