Development Tools MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Node environment setting | production |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_security_issuesC | Scan code for security issues including secrets, vulnerabilities, and insecure patterns |
| detect_secretsC | Detect hardcoded secrets and credentials in code |
| analyze_permissionsC | Analyze file permissions and access control issues |
| check_complianceB | Check code compliance with security standards (simplified) |
| analyze_code_qualityB | Analyze overall code quality including complexity, maintainability, code smells, and duplications |
| calculate_complexityC | Calculate cyclomatic complexity for code files |
| detect_code_smellsC | Detect code smells in code files |
| analyze_maintainabilityC | Calculate maintainability index for code |
| find_duplicate_codeC | Find duplicate code blocks across files |
| analyze_test_coverageC | Analyze test coverage for code files (simplified) |
| generate_code_metricsC | Generate detailed code metrics report |
| suggest_refactoringC | Suggest refactoring opportunities based on code analysis |
| analyze_dependenciesC | Analyze project dependencies including unused, outdated, and vulnerable packages |
| find_unused_dependenciesC | Find unused dependencies in project |
| check_vulnerabilitiesC | Check for security vulnerabilities in dependencies |
| check_outdated_packagesC | Check for outdated packages |
| analyze_bundle_sizeC | Analyze bundle size of dependencies |
| suggest_dependency_updatesC | Suggest dependency updates based on analysis |
| lint_codeC | Lint code files using ESLint |
| format_codeB | Format code files using Prettier |
| check_typescriptB | Check TypeScript files for type errors |
| validate_syntaxC | Validate syntax of code files |
| fix_lint_issuesC | Automatically fix linting issues in code files |
| scrape_htmlC | Scrape HTML content from a URL |
| extract_textC | Extract text content from a web page |
| extract_linksC | Extract all links from a web page |
| extract_imagesB | Extract all image URLs from a web page |
| extract_tablesC | Extract table data from a web page |
| scrape_by_selectorC | Scrape content using CSS selector |
| scrape_dynamic_contentC | Scrape JavaScript-rendered content using browser |
| scrape_with_interactionC | Scrape content after user interactions (click, scroll, etc.) |
| screenshot_pageC | Take a screenshot of a web page |
| wait_for_elementC | Wait for an element to appear and extract its content |
| extract_after_clickC | Click an element and extract content from another element |
| discover_api_endpointsC | Discover API endpoints by monitoring network requests on a web page |
| analyze_network_requestsC | Analyze all network requests made by a web page |
| extract_api_schemaB | Extract API schema from discovered endpoints |
| test_api_endpointC | Test an API endpoint with HTTP request |
| parse_jsonC | Parse JSON data |
| parse_xmlC | Parse XML data |
| parse_csvC | Parse CSV data |
| format_scraped_dataC | Format scraped data into different output formats |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.