Hydrafetch vs Enconvert
A side-by-side look at the Hydrafetch and Enconvert MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
H
HydrafetchSearch & Data ExtractionTurn any URL into clean Markdown and structured data. Scrape, crawl, search and extract.37FairAuth: not declaredVerdict: choose Hydrafetch for search & data extraction work; choose Enconvert 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?
HChoose Hydrafetch when
- You need dedicated capabilities in the Search & Data Extraction domain.
Choose Enconvert when
- You need dedicated capabilities in the Search & Data Extraction domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
ENCONVERT_API_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | H Hydrafetch | |
|---|---|---|
| Category | Search & Data Extraction | Search & Data Extraction |
| Quality signal | 37/100 · Fair | 47/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | None listed | ENCONVERT_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 7 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Hydrafetch | View Enconvert |
Tools & capabilities
Hydrafetch tools
No tool names declared yet. Check the project README from the listing page.
Enconvert 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.
Hydrafetch
No confirmed install command for Hydrafetch yet — follow the setup steps linked from its listing page rather than a guessed package name.
Enconvert
{
"mcpServers": {
"enconvert": {
"command": "npx",
"args": [
"-y",
"@enconvert/mcp"
],
"env": {
"ENCONVERT_API_KEY": "YOUR_ENCONVERT_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Hydrafetch is categorized under Search & Data Extraction and uses an install path we have not confirmed yet. Enconvert belongs to Search & Data Extraction and uses a local stdio subprocess. Pick Hydrafetch for search & data extraction work and Enconvert 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. Hydrafetch has no confirmed install command yet — follow its own setup instructions.
Hydrafetch has no declared pricing — check the project's own site. Enconvert is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key 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 hydrafetch and enconvert as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Hydrafetch has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Enconvert has 47/100 (Fair) with 3 views, 0 installs and 7 GitHub stars.