EDT-MCP is an Eclipse/OSGi plugin that implements a Model Context Protocol (MCP) server for 1C:Enterprise Development Tools (EDT). It exposes over 95 MCP tools enabling AI agents (Claude, Copilot, Cursor) to inspect and manipulate EDT workspaces – reading metadata, editing BSL code, running tests, managing debug sessions, performing git operations, and configuring infobases. The server runs as a plugin inside EDT, uses JSON-RPC 2.0 over HTTP/SSE transport, and supports progressive tool disclosure via toolsets. A separate proxy component allows routing MCP calls across multiple EDT backends with hot-plug failover. The architecture is layered: a protocol layer (session management, origin validation, JSON schema building), a tool registry with atomic catalog replacement, utility services for EDT model access (BmTransactions, ProjectContext, DebugSessionRegistry), and UI extensions (metadata tagging, virtual groups, call history view). The build uses Maven/Tycho and produces a p2 update site for EDT 2026.1 and 2026.2. Test coverage includes headless unit tests (JUnit/Mockito), Python e2e tests against a live server, conformance tests against the official MCP conformance suite, and ratchet tests that enforce coding standards, error quality, schema parity, and mutation safety. Key engineering patterns include: idempotent tool execution with destructive consent gates, PII redaction via HMAC pseudonymization, optimistic locking via ContentHash for read-modify-write cycles, bilingual Russian/English FQN normalization, and strict separation of read/write transactions (reads use IBmModel.executeReadonlyTask, writes use execute). The codebase is well-maintained with active issue triage and CI/CD pipelines.
This is the Spring Tools 4 (STS4) repository, a comprehensive set of IDE tooling for Spring Boot development. It provides language servers (LSP) for Spring Boot (Java, YAML, properties, XML), Concourse CI, BOSH, and Cloud Foundry manifests, along with Eclipse plugins and VS Code extensions. The architecture separates headless language servers (built as Spring Boot applications) from IDE-specific frontends, with shared commons libraries for YAML, Java project indexing, metadata, and live process monitoring via Actuator. The codebase is professional and well-structured but shows signs of organic growth over a decade, with some code duplication between the Eclipse and headless/VS Code paths, deprecated API usage, and developer-specific hardcoded paths. It is actively maintained by VMware/Spring engineering team with strong CI/CD pipelines.
Wild Web Developer is an Eclipse IDE plugin that integrates a suite of language servers (HTML, CSS, JavaScript/TypeScript, JSON, YAML, XML, Markdown, Vue, Angular, Astro, ESLint) and debug adapters (Node.js, Chrome, Firefox, npm) into the Eclipse workbench. It uses Language Server Protocol (LSP) via LSP4E and TextMate grammars for syntax highlighting, and Debug Adapter Protocol (DAP) via LSP4E's debug support. The plugin bundles an embedded Node.js runtime to execute external language servers and debug adapters, and provides extensive preference pages for each supported language. The architecture is a standard Eclipse RCP plugin with extension points for schema association and LemMinX extensions. The codebase demonstrates solid engineering practices with a clear separation between language server clients, debug delegates, and UI components, though some parts (e.g., preference pages) suffer from copy-paste duplication. It is actively maintained with frequent dependency updates and a comprehensive test suite.