Gradle MCP server enables AI tools to interact with Gradle projects through a standardized interface built on the Gradle Tooling API. It exposes tools for retrieving project metadata and executing Gradle tasks remotely, with support for both stdio and SSE transport modes. Particularly valuable for developers who want to automate Gradle project management and builds through conversational AI without manual configuration.
아직 리뷰가 없습니다. 첫 번째 리뷰를 작성해 보세요!
대화에 참여하려면 로그인하세요
Retrieves specific details about a Gradle project, returning structured JSON. Allows requesting only necessary information categories (`buildStructure`, `tasks`, `environment`, `projectDetails`). If `requestedInfo` is omitted, all categories are fetched. Key Inputs: projectPath (string, required), requestedInfo (array of strings, optional). Output: JSON object containing the requested data fields and potential errors.
Executes general Gradle tasks (like `build`, `clean`). Not recommended for running tests if detailed results are needed (use the test tool instead). Returns formatted text output summarizing execution and including captured stdout/stderr. Key Inputs: projectPath (string, required), tasks (array of strings, required), arguments (array of strings, optional), jvmArguments (array of strings, optional), environmentVariables (object, optional). Output: Formatted text response with execution summary, final status (Success/Failure), and combined stdout/stderr.
Executes Gradle test tasks and returns results as a structured JSON hierarchy (Suite > Class > Test). Filters/truncates output lines by default, focusing on failures. Provides options to include output for passed tests and control log limits. Key Inputs: projectPath (string, required), gradleTasks (array of strings, optional), arguments (array of strings, optional), environmentVariables (object, optional), testPatterns (array of strings, optional), includeOutputForPassed (boolean, optional), maxLogLines (integer, optional), defaultMaxLogLines (integer, optional). Output: JSON object containing execution details, overall build success status, informative notes, and the test hierarchy tree.