Openwebninja Mcp

io.github.OpenWeb-NinjaPublished by GitHub account OpenWeb-Ninjav0.1.1Updated Oct 27, 2026

Official MCP server for OpenWeb Ninja APIs - 40+ real-time web data and SERP APIs as MCP tools

Overview

AI-generated overview

Official OpenWeb Ninja MCP server exposing 50+ real-time web data APIs — search, local business, jobs, commerce, real estate, finance and news — as tools for…

What you can do
  • Search and discovery: real-time web, news, forums, image, video and shorts search, autocomplete, AI overviews and social links
  • Local and maps: local business and review data, rank tracking, driving directions, traffic alerts and EV charging
  • Jobs and companies: job search across several boards, salary data and company review data
  • Commerce and product: Amazon, Walmart, eBay, Costco, Wayfair, Home Depot, books and app store lookups
  • Real estate, finance and events: property listings, market data and event data
  • Contact enrichment and utility: website contact scraping, email search, a web unblocker and LLM relay tools, plus a subscribe tool for free API tiers
When to use it
Useful when an assistant needs live public web data — SERP results, local business listings, job postings, product prices or property listings — without building and maintaining scrapers or API integrations itself.
Requirements
Runs locally over stdio via npx (Node.js required) or from a built source checkout. Needs an OpenWeb Ninja account and an API key passed in the OPENWEBNINJA_API_KEY environment variable; the optional OPENWEBNINJA_BASE_URL overrides the API host. Network access to the OpenWeb Ninja API is required.
Before you install
The API key in OPENWEBNINJA_API_KEY is sent as a request header to OpenWeb Ninja, and every query and its arguments go to that third-party service. Some tools scrape contact details and email addresses, and the subscribe tool adds paid API products to your account, which may incur usage costs. Review the provider's pricing and terms before use.

Installation

In SourceWeft

  1. Open Openwebninja Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

OpenWeb Ninja MCP Server

Official Model Context Protocol server for OpenWeb Ninja APIs. Gives any MCP-compatible AI agent (Claude, Cursor, Cline, and others) real-time access to web search, local business data, jobs, e-commerce, real estate, finance, news, and more, through a single connection.

One tool per API product (52 tools), each exposing that API's operations, plus a subscribe tool for adding an API's free tier on demand — 53 tools in total. Schemas are generated directly from OpenWeb Ninja's OpenAPI specs, so the server always matches the live APIs.

Setup

You need an OpenWeb Ninja API key. Get one at openwebninja.com.

The server runs via npx — there's nothing to install globally. Pick your client below; npx fetches @openwebninja/mcp-server on demand.

Claude Desktop

Add to claude_desktop_config.json (Settings -> Developer -> Edit Config):

json
{  "mcpServers": {    "openwebninja": {      "command": "npx",      "args": ["-y", "@openwebninja/mcp-server"],      "env": { "OPENWEBNINJA_API_KEY": "your-api-key" }    }  }}

Claude Code

bash
claude mcp add openwebninja -e OPENWEBNINJA_API_KEY=your-api-key -- npx -y @openwebninja/mcp-server

Cursor / Cline / Continue / Windsurf

Use the same command / args / env shape in the client's MCP config (mcp.json or equivalent).

From source (local development)

bash
git clone <repo> && cd openwebninja-mcpnpm installnpm run build

Then point your MCP client at the built entry:

json
{  "mcpServers": {    "openwebninja": {      "command": "node",      "args": ["/absolute/path/to/openwebninja-mcp/dist/index.js"],      "env": { "OPENWEBNINJA_API_KEY": "your-api-key" }    }  }}

How the tools work

Each tool maps to one OpenWeb Ninja API and takes two inputs:

  • operation: which endpoint to call (e.g. search, product_details)
  • args: the parameters for that operation

The tool description lists every operation and its required parameters. Example call to the jsearch tool:

json
{  "operation": "search",  "args": { "query": "site reliability engineer remote", "country": "us" }}

Arguments are validated and type-coerced before the request is sent, and responses return the OpenWeb Ninja data payload plus a request_id.

Environment variables

VariableRequiredDescription
OPENWEBNINJA_API_KEYyesYour OpenWeb Ninja API key (sent as x-api-key).
OPENWEBNINJA_BASE_URLnoOverride the API host (defaults to https://api.openwebninja.com). For staging/testing.

Available tools (54)

Search & discovery: realtime_web_search, realtime_bing_search_data, realtime_news_data, real_time_news_search, realtime_forums_search, web_search_autocomplete, realtime_image_search, reverse_image_search, realtime_lens_data, real_time_video_search, realtime_shorts_search, ai_overviews, google_ai_mode, social_links_search

Local & maps: local_business_data, local_business_database, yelp_business_data, trustpilot_company_and_reviews, local_rank_tracker, driving_directions, waze, google_maps_traffic_alerts, ev_charge_finder

Jobs & companies: jsearch, realtime_linkedin_data, realtime_indeed_data, realtime_ziprecruiter_data, realtime_monster_data, job_salary_data, realtime_glassdoor_data

Commerce & product: realtime_amazon_data, realtime_product_search, real_time_walmart_data, real_time_ebay_data, realtime_aliexpress_data, realtime_costco_data, real_time_wayfair_data, realtime_homedepot_data, realtime_lowes_data, realtime_books_data, play_store_apps

Real estate: realtime_zillow_data, real_time_redfin_data

Finance & events: realtime_finance_data, realtime_events_data

Contact & enrichment: website_contacts_scraper, email_search, realtime_similarweb_data

Utility: web_unblocker

LLM relays: chatgpt, gemini, copilot

Access: subscribe (add an API's free tier on demand)

Development

bash
npm run sync       # sync OpenAPI specs from S3 into openapi-cache/ (needs AWS creds)npm run generate   # regenerate src/generated/manifest.ts from the specsnpm run build      # compile TypeScript to dist/npm run dev        # run the server over stdio (tsx, no build)npm run inspect    # launch the MCP Inspector against the servernpx tsx test/smoke.ts   # smoke test: list tools + validation + request path

The pipeline is: OpenAPI specs (openapi-cache/) -> scripts/generate.ts -> src/generated/manifest.ts -> tools registered at runtime in src/server.ts. To add or update an API, re-sync the specs and regenerate; no hand-written per-tool code is needed (only the curated descriptions in src/lib/descriptions.ts).

Source: README.md at commit 7ed6588

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts