Development Tools MCP Server
Supports CSS selector-based web scraping to extract specific elements from HTML pages.
Provides code linting capabilities, enabling automated code quality checks and automatic fixing of lint issues in JavaScript and TypeScript projects.
Generates formatted reports and documentation output for code analysis results and scraping data.
Analyzes Node.js project dependencies, detecting unused packages, security vulnerabilities, outdated dependencies, and bundle size analysis.
Provides npm package analysis including dependency tree analysis, vulnerability scanning, and package update suggestions.
Enables code formatting operations to automatically format and standardize code style across projects.
Provides TypeScript-specific analysis including type checking, syntax validation, and code quality metrics for TypeScript projects.
Provides XML parsing capabilities for processing structured data from scraped web content.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Development Tools MCP Server check my project's dependencies for security vulnerabilities"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP Development Tools Server
Comprehensive MCP (Model Context Protocol) server for code analysis and web scraping. Supports code quality analysis, linting, dependency analysis, static/dynamic web scraping, and API discovery.
🎯 Ne İşe Yarar?
MCP Development Tools, AI asistanlarının (Cursor, Claude Desktop, vb.) kod kalitesini analiz etmesi, web içeriklerini çekmesi ve development görevlerini gerçekleştirmesi için kapsamlı bir MCP server'dır.
Temel Özellikler
📊 Kod Kalitesi Analizi: Complexity, maintainability, code smells detection
🔍 Linting & Formatting: ESLint, Prettier, TypeScript checking
📦 Bağımlılık Analizi: Unused deps, vulnerabilities, outdated packages
🔒 Güvenlik Analizi: Secret detection, vulnerability scanning
🌐 Web Scraping: Static ve dynamic content scraping
🔎 API Keşfi: Endpoint discovery, network analysis
Related MCP server: Smart Code Reviewer
🚀 Kurulum
Gereksinimler
Node.js 18 veya üzeri
npm veya yarn
TypeScript (dev dependency)
Adımlar
Repository'yi klonlayın:
git clone https://github.com/code-alchemist01/development-tools-mcp-Server.git
cd development-tools-mcp-ServerBağımlılıkları yükleyin:
npm installPlaywright browser'larını yükleyin (dynamic scraping için):
npx playwright install chromiumProjeyi derleyin:
npm run buildTest edin:
npm start📦 MCP Client'lara Kurulum
Cursor IDE
1. MCP Config Dosyasını Oluştur/Düzenle
Windows:
%APPDATA%\Cursor\User\globalStorage\mcp.jsonmacOS/Linux:
~/.config/Cursor/User/globalStorage/mcp.json2. Config İçeriği
{
"mcpServers": {
"development-tools": {
"command": "node",
"args": [
"C:\\Users\\YourUsername\\path\\to\\development-tools-mcp-Server\\dist\\index.js"
]
}
}
}Not: args içindeki path'i kendi proje yolunuza göre güncelleyin.
3. Cursor'u Yeniden Başlatın
Config dosyasını kaydettikten sonra Cursor'u tamamen kapatıp yeniden açın.
4. Doğrulama
Cursor'da Settings > Tools & MCP bölümünde "development-tools" listede görünmeli ve "42 tools enabled" yazmalı.
Claude Desktop
1. MCP Config Dosyasını Oluştur/Düzenle
Windows:
%APPDATA%\Claude\claude_desktop_config.jsonmacOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonLinux:
~/.config/Claude/claude_desktop_config.json2. Config İçeriği
{
"mcpServers": {
"development-tools": {
"command": "node",
"args": [
"/absolute/path/to/development-tools-mcp-Server/dist/index.js"
]
}
}
}3. Claude Desktop'u Yeniden Başlatın
Diğer MCP Client'lar
Herhangi bir MCP client kullanıyorsanız, client'ın MCP server yapılandırma formatına göre aşağıdaki bilgileri kullanın:
Command:
nodeArgs:
[path/to/dist/index.js]Transport:
stdio(standard input/output)
Örnek Config Formatları
Genel MCP Config:
{
"mcpServers": {
"development-tools": {
"command": "node",
"args": ["/absolute/path/to/dist/index.js"],
"env": {}
}
}
}Environment Variables ile:
{
"mcpServers": {
"development-tools": {
"command": "node",
"args": ["/absolute/path/to/dist/index.js"],
"env": {
"NODE_ENV": "production"
}
}
}
}🛠️ Kullanım
MCP Client'larda Kullanım
MCP server kurulduktan sonra, client'ınızın chat arayüzünde doğal dil komutları kullanarak işlemleri gerçekleştirebilirsiniz.
Code Analysis Örnekleri
Kod Kalitesi Analizi:
Bu projedeki kod kalitesini analiz etsrc/**/*.ts dosyalarının kod kalitesini analiz etComplexity Hesaplama:
src/utils klasöründeki dosyaların complexity'sini hesaplaCode Smell Tespiti:
Kodda code smell'leri bulDuplicate Kod Bulma:
Projede duplicate kod bloklarını bulLinting Örnekleri
Kod Lint:
src/**/*.ts dosyalarını lint etKod Formatla:
src/**/*.ts dosyalarını Prettier ile formatlaTypeScript Kontrolü:
TypeScript dosyalarında type hatalarını kontrol etDependency Analysis Örnekleri
Bağımlılık Analizi:
Proje bağımlılıklarını analiz etKullanılmayan Paketleri Bul:
Kullanılmayan npm paketlerini bulGüvenlik Açıklarını Kontrol Et:
Dependency'lerdeki güvenlik açıklarını kontrol etWeb Scraping Örnekleri
HTML Scraping:
https://example.com sayfasını scrape etLink Çıkarma:
https://example.com sayfasındaki tüm linkleri çıkarDynamic Content:
https://example.com sayfasını browser ile scrape et (JavaScript render)API Endpoint Keşfi:
https://example.com sayfasındaki API endpoint'lerini keşfetSecurity Analysis Örnekleri
Secret Detection:
Kodda hardcoded secret'ları bulGüvenlik Taraması:
Güvenlik açıklarını tara📋 MCP Tools (42 Araç)
Code Quality Tools (8)
analyze_code_quality- Genel kod kalitesi analizicalculate_complexity- Cyclomatic complexity hesaplamadetect_code_smells- Code smell tespitianalyze_maintainability- Maintainability index hesaplamafind_duplicate_code- Duplicate kod tespitianalyze_test_coverage- Test coverage analizigenerate_code_metrics- Detaylı kod metriklerisuggest_refactoring- Refactoring önerileri
Linting Tools (5)
lint_code- ESLint ile kod kontrolüformat_code- Prettier ile kod formatlamacheck_typescript- TypeScript type checkingvalidate_syntax- Syntax doğrulamafix_lint_issues- Otomatik lint düzeltmeleri
Dependency Analysis Tools (6)
analyze_dependencies- Bağımlılık ağacı analizifind_unused_dependencies- Kullanılmayan paketleri bulcheck_vulnerabilities- Güvenlik açığı kontrolücheck_outdated_packages- Eski paketleri tespit etanalyze_bundle_size- Bundle boyutu analizisuggest_dependency_updates- Güncelleme önerileri
Security Analysis Tools (4)
scan_security_issues- Güvenlik taramasıdetect_secrets- Hardcoded secret'ları bulanalyze_permissions- Dosya izin analizicheck_compliance- Compliance kontrolü
Static Scraping Tools (6)
scrape_html- HTML içeriği çekmeextract_text- Metin çıkarmaextract_links- Link çıkarmaextract_images- Görsel URL'leri çıkarmaextract_tables- Tablo verilerini çıkarmascrape_by_selector- CSS selector ile scraping
Dynamic Scraping Tools (5)
scrape_dynamic_content- JavaScript render edilmiş içerikscrape_with_interaction- Kullanıcı etkileşimi ile scrapingscreenshot_page- Sayfa ekran görüntüsüwait_for_element- Element beklemeextract_after_click- Tıklama sonrası içerik çekme
API Discovery Tools (4)
discover_api_endpoints- API endpoint keşfianalyze_network_requests- Network trafiği analiziextract_api_schema- API şema çıkarmatest_api_endpoint- API endpoint testi
Data Processing Tools (4)
parse_json- JSON parsingparse_xml- XML parsingparse_csv- CSV parsingformat_scraped_data- Veri formatlama
📁 Proje Yapısı
development-tools-mcp-Server/
├── src/
│ ├── index.ts # MCP server ana giriş noktası
│ ├── server.ts # MCP server implementasyonu
│ ├── tools/ # MCP tools
│ │ ├── code-analysis.ts # Security analysis tools
│ │ ├── code-quality.ts # Code quality tools
│ │ ├── dependency-analysis.ts # Dependency analysis tools
│ │ ├── linting.ts # Linting tools
│ │ ├── web-scraping.ts # Web scraping tools
│ │ └── api-discovery.ts # API discovery tools
│ ├── analyzers/ # Analiz motorları
│ │ ├── code-analyzer.ts # Kod analizi
│ │ ├── complexity-analyzer.ts # Complexity analizi
│ │ ├── dependency-analyzer.ts # Bağımlılık analizi
│ │ └── security-analyzer.ts # Güvenlik analizi
│ ├── scrapers/ # Scraping motorları
│ │ ├── static-scraper.ts # Static HTML scraping
│ │ ├── dynamic-scraper.ts # Dynamic content scraping
│ │ └── api-scraper.ts # API endpoint keşfi
│ ├── utils/ # Yardımcı fonksiyonlar
│ │ ├── file-reader.ts
│ │ ├── formatters.ts
│ │ ├── validators.ts
│ │ └── linting-utils.ts
│ └── types/ # TypeScript tip tanımları
│ └── index.ts
├── dist/ # Derlenmiş JavaScript dosyaları
├── package.json
├── tsconfig.json
└── README.md🔧 Geliştirme
Development Modu
npm run devBuild
npm run buildTest
npm test📝 Örnek Kullanım Senaryoları
Senaryo 1: Kod Kalitesi Analizi
MCP Client Chat'te:
src/**/*.ts dosyalarının kod kalitesini analiz et
En karmaşık fonksiyonları göster
Code smell'leri tespit etBeklenen Sonuç:
Kod kalitesi metrikleri
Complexity analizi
Code smell listesi
Refactoring önerileri
Senaryo 2: Web Scraping
MCP Client Chat'te:
https://example.com sayfasını scrape et
Sayfadaki tüm linkleri çıkar
Tablo verilerini extract etBeklenen Sonuç:
HTML içeriği
Link listesi
Tablo verileri
Senaryo 3: API Keşfi
MCP Client Chat'te:
https://example.com sayfasındaki API endpoint'lerini keşfet
Network request'leri analiz etBeklenen Sonuç:
API endpoint listesi
Request/response analizi
Authentication bilgileri
Senaryo 4: Dependency Temizliği
MCP Client Chat'te:
Kullanılmayan paketleri bul
Güvenlik açıklarını kontrol et
Güncelleme önerileri yapBeklenen Sonuç:
Unused dependencies listesi
Vulnerability raporu
Update suggestions
🔐 Güvenlik
Input validation ve sanitization
URL validation
Timeout yönetimi
Error handling
Secret detection
SQL injection koruması
📊 Çıktı Formatları
JSON - Structured data responses
Markdown - Raporlar ve dokümantasyon
CSV - Veri export
Text - Plain text output
🤝 Katkıda Bulunma
Fork edin
Feature branch oluşturun (
git checkout -b feature/amazing-feature)Commit edin (
git commit -m 'Add amazing feature')Push edin (
git push origin feature/amazing-feature)Pull Request açın
📄 Lisans
MIT License - Detaylar için LICENSE dosyasına bakın.
🔗 MCP Client Desteği
Bu MCP server aşağıdaki client'lar ile uyumludur:
✅ Cursor IDE - Tam destek
✅ Claude Desktop - Tam destek
✅ Anthropic API - MCP protokolü üzerinden
✅ Diğer MCP Client'lar - Standart MCP protokolü destekleyen tüm client'lar
🙏 Teşekkürler
Model Context Protocol - MCP standardı için
Cursor - MCP desteği için
Claude - MCP desteği için
📞 İletişim
Sorularınız veya önerileriniz için issue açabilirsiniz.
⭐ Bu projeyi beğendiyseniz yıldız vermeyi unutmayın!
Available Tools
42 toolsanalyze_bundle_sizeC
Analyze bundle size of dependencies
Inputs: projectPath.
analyze_code_qualityB
Analyze overall code quality including complexity, maintainability, code smells, and duplications
Inputs: files (required), includePatterns, excludePatterns, maxComplexity, +2 more.
analyze_dependenciesC
Analyze project dependencies including unused, outdated, and vulnerable packages
Inputs: projectPath, checkUnused, checkOutdated, checkVulnerabilities, +1 more.
analyze_maintainabilityC
Calculate maintainability index for code
Inputs: files (required).
analyze_network_requestsC
Analyze all network requests made by a web page
Inputs: url (required), timeout.
analyze_permissionsC
Analyze file permissions and access control issues
Inputs: files (required).
analyze_test_coverageC
Analyze test coverage for code files (simplified)
Inputs: files (required), testFiles.
calculate_complexityC
Calculate cyclomatic complexity for code files
Inputs: files (required).
check_complianceB
Check code compliance with security standards (simplified)
Inputs: files (required), standard.
check_outdated_packagesC
Check for outdated packages
Inputs: projectPath.
check_typescriptB
Check TypeScript files for type errors
Inputs: files (required).
check_vulnerabilitiesC
Check for security vulnerabilities in dependencies
Inputs: projectPath.
detect_code_smellsC
Detect code smells in code files
Inputs: files (required), maxComplexity.
detect_secretsC
Detect hardcoded secrets and credentials in code
Inputs: files (required).
discover_api_endpointsC
Discover API endpoints by monitoring network requests on a web page
Inputs: url (required), timeout.
extract_after_clickC
Click an element and extract content from another element
Inputs: url (required), clickSelector (required), extractSelector (required).
extract_api_schemaB
Extract API schema from discovered endpoints
Inputs: url (required), endpoint.
extract_imagesB
Extract all image URLs from a web page
Inputs: url (required), useBrowser.
extract_linksC
Extract all links from a web page
Inputs: url (required), useBrowser.
extract_tablesC
Extract table data from a web page
Inputs: url (required), useBrowser.
extract_textC
Extract text content from a web page
Inputs: url (required), useBrowser.
find_duplicate_codeC
Find duplicate code blocks across files
Inputs: files (required), minLines.
find_unused_dependenciesC
Find unused dependencies in project
Inputs: projectPath.
fix_lint_issuesC
Automatically fix linting issues in code files
Inputs: files (required).
format_codeB
Format code files using Prettier
Inputs: files (required), options.
format_scraped_dataC
Format scraped data into different output formats
Inputs: data (required), format.
generate_code_metricsC
Generate detailed code metrics report
Inputs: files (required), format.
lint_codeC
Lint code files using ESLint
Inputs: files (required).
parse_csvC
Parse CSV data
Inputs: data (required), delimiter.
parse_jsonC
Parse JSON data
Inputs: data (required).
parse_xmlC
Parse XML data
Inputs: data (required).
scan_security_issuesC
Scan code for security issues including secrets, vulnerabilities, and insecure patterns
Inputs: files (required).
scrape_by_selectorC
Scrape content using CSS selector
Inputs: url (required), selector (required), useBrowser.
scrape_dynamic_contentC
Scrape JavaScript-rendered content using browser
Inputs: url (required), waitForSelector, waitForTimeout, timeout.
scrape_htmlC
Scrape HTML content from a URL
Inputs: url (required), useBrowser, timeout, headers.
scrape_with_interactionC
Scrape content after user interactions (click, scroll, etc.)
Inputs: url (required), interactions (required).
screenshot_pageC
Take a screenshot of a web page
Inputs: url (required), fullPage, waitForSelector.
suggest_dependency_updatesC
Suggest dependency updates based on analysis
Inputs: projectPath.
suggest_refactoringC
Suggest refactoring opportunities based on code analysis
Inputs: files (required).
test_api_endpointC
Test an API endpoint with HTTP request
Inputs: url (required), method, headers, body.
validate_syntaxC
Validate syntax of code files
Inputs: files (required).
wait_for_elementC
Wait for an element to appear and extract its content
Inputs: url (required), selector (required), timeout.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Code intelligence platform for AI agents. 20 tools for architecture, security & impact analysis.
30+ deterministic dev and delivery tools: linting, metrics, diagrams, model advice, AI-text checks.
AI-powered codebase analysis — call graphs, security, dead code, complexity. 150+ tools.
Web scraping, code review, content gen, sentiment. Zero Core Tools.
Related MCP Servers
- 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
- AlicenseAqualityDmaintenanceEnables comprehensive code analysis including quality assessment, security vulnerability detection, refactoring suggestions, complexity calculations, and automatic documentation generation for multiple programming languages.59 npmMIT
- 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
- 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.-