spring-plugin
Reduces context-switching and debugging cycles by providing IntelliJ integration that maps actual Spring bean lifecycles, endpoint routes, and runtime behavi…
Spring Explyt — a free, source-available plugin for IntelliJ IDEA Community Edition that brings runtime-accurate Spring Framework tooling (beans, endpoints, debugger, HTTP client, MCP tools).
- Ask Claude to help debug why a Spring bean isn't being autowired correctly in your application.
- Generate HTTP requests to test your Spring REST endpoints directly from the IDE.
- Find all Spring bean dependencies and their injection points across your codebase quickly.
Reduces context-switching and debugging cycles by providing IntelliJ integration that maps actual Spring bean lifecycles, endpoint routes, and runtime behavior without leaving the IDE. Cuts time spent cross-referencing configuration files and logs.
Spring Framework development teams using IntelliJ Community Edition who need visibility into bean wiring, endpoint mapping, and request-response flows during active development.
https://github.com/explyt/spring-plugin
By explyt
How to Get It
claude plugins install explyt/spring-plugin
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Help debug why a Spring bean isn't being autowired correctly in my application
Trust Signals Auto-scanned
Community Pulse New
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 155 GitHub stars; contributors unknown; last commit 0d ago; license Apache-2.0.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 155 GitHub stars; contributors unknown; last commit 0d ago; license Apache-2.0.