js-ts-mcp
Related Servers
Alternatives to js-ts-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to retrieve live CPython standard-library documentation and PyPI package metadata as clean markdown, with cached, throttled, robots-aware requests and local module search.MIT
- AlicenseAqualityCmaintenanceEnables any MCP-compatible AI agent to search the live web and fetch pages as clean Markdown, including batch fetching with rate limiting, retries, and context-safe truncation.3MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents and LLM pipelines to fetch webpages and crawl sites locally, stripping noise and converting content to clean, token-efficient Markdown with preserved links, caching, and polite crawling.-
- AlicenseNot gradedqualityDmaintenanceGives AI agents full-text search over any Markdown/MDX documentation folder.6 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to search, fetch, and clean live documentation from LangChain, LlamaIndex, and OpenAI via Model Context Protocol, with token-optimized extraction.-
- AlicenseNot gradedqualityAmaintenanceEnables AI agents and IDE workflows to fetch and crawl webpages locally, extracting readable content and converting it to token-efficient Markdown with preserved links.MIT
TDQS
Scored across 5 tools
js_docs/js_search and npm_package have clearly distinct purposes, but health_check and js_status overlap in concept; the description of js_status as the 'Real health check' helps, though an agent could still hesitate over which to call first.
Mostly consistent snake_case with domain prefixes (js_*, npm_*), but health_check lacks a prefix and breaks the js_ family pattern, a minor deviation.
Five tools is well-scoped for a focused docs/registry server: search, fetch, package lookup, and health probes are each justified without bloat.
The surface covers docs search/fetch and exact npm package lookup, but there is no npm package search by keyword or broader registry discovery, a notable gap for a js/ts knowledge server with no general web fallback.