Official MCP server for OpenWeb Ninja APIs - 40+ real-time web data and SERP APIs as MCP tools
If you already use Openwebninja, the openwebninja mcp server is the piece that lets your assistant work with it directly. Official MCP server for OpenWeb Ninja APIs - 40+ real-time web data and SERP APIs as MCP tools.
One tool per API product (41 tools), each exposing that API's operations, plus a subscribe tool for adding an API's free tier on demand — 42 tools in total. Schemas are generated directly from OpenWeb Ninja's OpenAPI specs, so the server always matches the live APIs.
@openwebninja/mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
operation — which endpoint to call (e.g. search, product_details)args — the parameters for that operationConfiguration is passed through the environment: OPENWEBNINJA_API_KEY, OPENWEBNINJA_BASE_URL. 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.
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. Openwebninja's toolset — operation, args — is a fair guide to whether it matches your workflow. It is maintained by OpenWeb-Ninja; 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 |
|---|---|
| operation | which endpoint to call (e.g. search, product_details) |
| args | the parameters for that operation |
{
"mcpServers": {
"openwebninja": {
"command": "npx",
"args": ["-y", "@openwebninja/mcp-server"],
"env": { "OPENWEBNINJA_API_KEY": "your-api-key" }
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| OPENWEBNINJA_API_KEY | Credential the server authenticates with. | Yes |
| OPENWEBNINJA_BASE_URL | Endpoint or connection string the server talks to. | 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.