Openwebninja MCP vs Units LE
A side-by-side look at the Openwebninja MCP and Units LE MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Openwebninja MCP for search & data extraction work as a local process; choose Units LE for search & data extraction as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Openwebninja MCP when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
OPENWEBNINJA_API_KEY, OPENWEBNINJA_BASE_URL.
Choose Units LE when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 47/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | OPENWEBNINJA_API_KEYOPENWEBNINJA_BASE_URL |
Tools & capabilities
Openwebninja MCP tools
No tool names declared yet. Check the project README from the listing page.
Units LE tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Openwebninja MCP
{
"mcpServers": {
"openwebninja-mcp": {
"command": "npx",
"args": [
"-y",
"@openwebninja/mcp-server"
],
"env": {
"OPENWEBNINJA_API_KEY": "YOUR_OPENWEBNINJA_API_KEY_HERE",
"OPENWEBNINJA_BASE_URL": "YOUR_OPENWEBNINJA_BASE_URL_HERE"
}
}
}
}
Units LE
{
"mcpServers": {
"units-le": {
"command": "npx",
"args": [
"-y",
"units-le-mcp"
]
}
}
}
Frequently asked questions
Openwebninja MCP is categorized under Search & Data Extraction and uses a local stdio subprocess. Units LE belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Openwebninja MCP for search & data extraction work and Units LE for search & data extraction.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Openwebninja MCP has no declared pricing — check the project's own site. Units LE is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add openwebninja-mcp and units-le as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Openwebninja MCP has a quality signal of 47/100 (Fair) with 1 views, 0 installs and 36 GitHub stars. Units LE has 37/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.
