Development Tools MCP Server
Related Servers
Alternatives to Development Tools MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables comprehensive code analysis including quality assessment, security vulnerability detection, refactoring suggestions, complexity calculations, and automatic documentation generation for multiple programming languages.58 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides intelligent codebase analysis, dependency scanning, architecture detection, security vulnerability scanning, and automatic documentation generation for modern development teams.27 npmMIT
- FlicenseNot gradedqualityDmaintenanceProvides browser automation, AI-powered analysis, visual processing, web scraping, automated test generation, and DevTools analysis capabilities. Supports multiple AI providers (OpenAI, Anthropic, Google, Ollama) for intelligent web interaction and data extraction.-
- AlicenseAqualityDmaintenanceEnables web content scanning and analysis by fetching, analyzing, and extracting information from web pages using tools like page fetching, link extraction, site crawling, and more.613MIT
- FlicenseBqualityCmaintenanceEnables AI agents to perform comprehensive, zero-infrastructure codebase analysis through 24 MCP tools, covering security, quality, architecture, type safety, git history, and dead code detection with high precision and local privacy.45-
- AlicenseNot gradedqualityDmaintenanceProvides advanced web scraping with HTTP client, smart content extraction to Markdown, browser automation via Playwright, screenshot/PDF generation, and Docker sandbox execution environments.1MIT
TDQS
Scored across 42 tools
There is significant overlap between tools, making it difficult for an agent to distinguish them. For example, analyze_dependencies, check_outdated_packages, check_vulnerabilities, and find_unused_dependencies all relate to dependency analysis, while tools like extract_text, scrape_html, and scrape_by_selector have overlapping web scraping purposes. This ambiguity increases the risk of misselection.
The naming is mostly consistent with a verb_noun pattern (e.g., analyze_bundle_size, check_typescript, extract_links), which aids readability. However, there are minor deviations such as 'screenshot_page' (noun_verb) and 'wait_for_element' (verb_preposition_noun), slightly disrupting the pattern.
With 42 tools, the count is excessive for a single server, leading to potential confusion and inefficiency. This many tools suggests poor scoping, as the server covers diverse domains like code analysis, web scraping, and data parsing without clear separation, making it feel bloated and difficult to navigate.
The tool set covers broad areas like code analysis, web scraping, and data handling, but there are notable gaps. For instance, in code analysis, tools for refactoring or testing are limited (e.g., no direct test execution tools), and in web scraping, there's no tool for handling authentication or sessions. While core functions are present, the coverage is uneven across domains.