web2mcp
Related Servers
Alternatives to web2mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables Claude and ChatGPT to call upstream APIs that existing connectors cannot, by registering credentials and using short-lived gateway tokens relayed through a Cloudflare Workers remote MCP server.MIT
- AlicenseNot gradedqualityBmaintenanceTurns existing REST/OpenAPI APIs into governed MCP tools for AI agents without modifying the APIs themselves, generating agent-friendly tools from specs, Postman collections, HAR files or cURL commands. Owners enable tools and set policies, while every call injects upstream credentials, redacts PII, projects responses to fit context limits, and produces a full audit trail.5Apache 2.0
- FlicenseNot gradedqualityNot gradedmaintenanceA serverless MCP implementation on Cloudflare Workers that allows connecting AI models to custom tools without requiring authentication.-
- AlicenseNot gradedqualityDmaintenanceExpose any API to an LLM agent as two sandboxed MCP tools (search + execute) on Cloudflare Workers.11 npm2MIT
- FlicenseNot gradedqualityNot gradedmaintenanceA serverless MCP implementation on Cloudflare Workers that allows connecting AI models to custom tools without authentication requirements.-
- FlicenseNot gradedqualityDmaintenanceExposes any REST API as MCP tools, enabling AI agents to discover and call existing HTTP endpoints without modifying the original API.-
TDQS
Scored across 13 tools
Each tool is tied to a distinct source and operation, with clear distinctions between search vs retrieval tools such as wikipedia_search/wikipedia_summary, hackernews_front_page/hackernews_search, and github_search_repos/github_repo. reader_read is explicitly positioned as a fallback, so it does not create meaningful ambiguity.
Tool names consistently use snake_case with service/source prefixes, making the set easy to scan. There are minor deviations such as noun-only names like npm_package and github_repo, plus the separate npmstats namespace, but the convention remains predictable.
With 13 tools spanning several lightweight web data sources, the count is well within a reasonable range and each tool has a clear role. There is no obvious bloat or duplicate operation.
The surface covers the core read paths for each included source and provides a generic reader_read fallback for arbitrary pages. Some gaps exist, such as HN item/comment retrieval, GitHub code/issues/PRs, currency conversion/history, npm search, and a general web search tool, but agents can often work around them via the reader or dedicated tools where provided.