"Java command reference and usage" matching MCP servers:

A local MCP server that exposes Blacksmith.sh's usage and cost data, enabling queries for CI spend through agents, alerts, or dashboards.

. A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{

Automates Java Maven testing workflows with decision table-based test generation, security vulnerability scanning, JaCoCo coverage analysis, and Git automation.

Enables AI coding tools to scaffold, build, and deploy Node.js or Python apps to Varity with a single command, automatically provisioning databases and backend services.

Local CI/CD engine for AI agents. ActionD listens to LGH git events and runs plugin jobs (Go/Python/Java/web toolchains) in isolated checkouts, with structured results, root-cause failure diagnosis, approval gates, and auto-rollback. The MCP server exposes 23 tools, including dev_cycle_run (commit → CI → structured verdict in one call) and actiond_diagnose for failed-job analysis.

Provides coding agents read-only access to Depot's CI failure diagnoses, container build forensics, run history, cache effectiveness, registry contents, and usage data through MCP tools.

A reference MCP server for observing Vercel projects and deployments over stdio. It provides read-only tools to list and fetch details of Vercel projects and deployments.

MCP security trust layer. Continuously monitors 800+ MCP packages on npm for install scripts, command injection, hardcoded secrets, capability drift, and publisher posture. Ships a GitHub Action policy gate for PR-level allow/warn/block decisions. 5 MCP tools, no API key required.

Enables agents and CI pipelines to audit MCP servers and agent tool-chains by statically scanning repositories, local checkouts, tools/list exports, or live endpoints for risks such as destructive actions without confirmation, mismatched safety annotations, injection surfaces, credential or PII exposure, and unguarded command, path, or URL sinks. All checks are read-only and never execute the scanned code or call tools/call.

MCP server that analyzes GitHub Actions workflow performance, audits configuration for optimization, and provides billing and cache usage insights.

A comprehensive MCP server for Dokploy that provides 14 action-based tools covering the full DevOps lifecycle with minimal token usage. It enables AI assistants to manage projects, applications, databases, domains, servers, and more through a unified interface.

Enables checking project files like Dockerfile, .nvmrc, and CI workflows to determine whether pinned runtime, database, and OS versions are still supported, providing end-of-life dates, latest patches, and upgrade targets for 470+ products.

A GitHub-native secrets manager that allows AI assistants to securely manage, generate, and validate credentials without exposing sensitive values in conversation history. It supports secret scanning, environment diffing, and secure command execution by injecting masked variables directly into the runtime environment.

Provides structured build, compile, and test operations with parsed output to reduce token usage and improve readability.

Monitor failing GitHub Actions workflows, auto-fix them with OpenCode, and retry the run — driven by a workflow_run webhook, coordinated through an MCP server.

Self-hosted coding agent that runs Claude Code or Codex in your own infrastructure and works from Slack. Exposes codebase investigation, file edits, branch and PR creation, allowlisted command execution, CI status and an audit log as MCP tools, keeping every credential behind the tool layer instead of handing it to the model.

Integrates Ploi.io API functionality into AI assistants for managing servers, sites, and databases through natural language. It enables features like one-command deployments, project linking, server log retrieval, and database backup management.

Enables SSH-based deployment operations such as git pull, command execution, script upload/run, and SSH config management.

Enables interaction with Blacksmith CI analytics to query workflow runs, jobs, test results, and usage metrics. It provides detailed access to CI/CD data including job logs and billing information directly through Claude.

Runs a long-lived command and converts its marked output into versioned build snapshots, exposing status, output, and waiting tools over MCP.