MCP Tools

MCP Tools

Explyt Spring ships Spring-aware MCP tools for the bundled JetBrains MCP Server in IntelliJ IDEA 2025.2+. They let agentic AI clients ask the IDE for structured Spring context instead of relying only on generic file search — which means fewer broad tool calls, lower token usage, and more accurate Spring-specific answers.

Requires IntelliJ IDEA 2025.2+ with the bundled JetBrains MCP Server. Works with AI clients that can connect to the IntelliJ IDEA MCP Server, including Explyt AI.

Looking for AI-augmented editor actions (entity↔DTO, schema→entity, etc.) instead? See Explyt AI Actions.

Why this matters

Generic agents often grep for annotations, infer controller mappings by hand, and open many DTO/entity files before making a safe change. Explyt's MCP tools expose Spring-aware IDE knowledge directly:

• Which Spring Boot apps are in this workspace?
• Which beans exist for a chosen app?
• Which endpoint handles this URL, and what is its full contract?
• Which service/repository methods are called from this controller?
• How do JPA entities map to tables and relationships?

The 7 tools

explyt_get_spring_boot_applications

Lists Spring Boot applications in the current workspace, including detected Spring Boot versions and starters. Use it when an agent first enters a multi-module workspace and needs the right application context.

explyt_get_project_beans_by_spring_boot_application

Returns beans for a selected Spring Boot application, with filtering by bean type such as CONTROLLER, REPOSITORY, CONFIGURATION, COMPONENT, and more — without searching every source file for stereotypes.

explyt_find_spring_endpoint

Finds endpoints matching a URL pattern across all endpoint types: Spring MVC, WebFlux, JAX-RS, HttpExchange, OpenFeign, OpenAPI, message brokers (Kafka/RabbitMQ listeners), and event listeners. Resolves composed paths (class-level @RequestMapping + method-level @GetMapping/@PostMapping), supports partial URL matching and path-variable wildcards, and returns full path, HTTP methods, controller class, method name, parameters (source, type, required flag), return type, file path, line number, and endpoint type.

explyt_get_spring_http_endpoints

Lists all HTTP endpoints in the project, optionally filtered by controller class name or endpoint type (SPRING_MVC, SPRING_WEBFLUX, SPRING_JAX_RS, …). Returns endpoints (a per-endpoint summary), totalCount (how many matched), and truncated (true when matches exceed the result cap — narrow with filters).

explyt_get_spring_endpoint_contract

Returns the full API contract for a specific endpoint: all parameters (path variables, query params, request body, headers) with types and required flags, the response DTO schema recursively expanded up to 3 levels, produces/consumes media types, and the first service method called from the controller.

explyt_trace_spring_call_chain

Traces the call chain from a method through Spring layers (Controller → Service → Repository). Given a file path and line number, it recursively follows method calls via UAST, detects Spring stereotypes (CONTROLLER, SERVICE, REPOSITORY, COMPONENT, CONFIGURATION), and returns the full chain with parameters, file paths, line numbers, and called methods. Optionally finds test files referencing discovered methods — essential for planning cross-cutting changes such as adding a new parameter.

explyt_get_spring_data_entities

Lists all JPA entities (@Entity) in the project (detects both jakarta.persistence and javax.persistence). For each entity it returns the class name, file path and line, resolved table name (from @Table or @Entity(name=...)), fields with column names/types, primary-key flags (@Id/@EmbeddedId), nullability, JPA relationships (@OneToOne, @OneToMany, @ManyToOne, @ManyToMany) with joinColumn/mappedBy metadata, and table indexes from @Table(indexes=[...]). Supports an optional package-prefix filter. Useful for schema understanding, migration planning, DTO design, and query writing.

Implementation

• Tool implementation and DTOs
• Toolset registration

Learn more

• Explyt Spring: Tools for MCP Server plugin (RU)

See also: Features · Native Context Mode · Explyt AI Actions