Skip to content
MCP Server Directory logo
developer-tools

Hoover

Continuously learn from and chat with one or more Cloud Foundry Foundations

Reviewed overview

MCP サーバー概要

what is Hoover?

Hoover is an MCP (Machine Conversation Platform) server implementation in the cf-kaizen project that lets you continuously learn from and chat with one or more Cloud Foundry foundations. It exposes read-only operations via a cf-hoover instance deployed on a target Cloud Foundry foundation and integrates with Claude Desktop as an MCP client.

how to use Hoover?

  • Prerequisites: a deployed cf-hoover instance, git, gh, Java, Maven (sdkman optional), and Claude Desktop (Windows/Mac/Linux).
  • Build: clone cf-kaizen and run mvn install (example: gh repo clone cf-toolsuite/cf-kaizen; cd cf-kaizen; mvn install).
  • Configure Claude Desktop: add an mcpServers entry that runs the Hoover server JAR via java -jar with a -Ddefault.url pointing to your cf-hoover endpoint and the absolute path to the built JAR (located in your local .m2 repository). Restart Claude Desktop and confirm the MCP client appears.
  • Target: replace default.url to point at the Cloud Foundry foundation you want Hoover to read from.

key features

  • Read-only MCP server for Cloud Foundry foundations.
  • Integrates with Claude Desktop as an MCP client for conversational access to CF data.
  • Implemented in Java (Spring Boot / Spring-AI patterns) and built with Maven.
  • Simple local deploy/build workflow and configuration via Claude Desktop mcpServers entry.

use cases

  1. Conversational querying of Cloud Foundry foundations for operational data and metadata.
  2. Auditing and read-only inspection of CF foundations without granting write access.
  3. Enabling chat-driven troubleshooting and knowledge discovery for platform operators.
  4. Integrating CF observability into AI-assisted workflows (via Claude Desktop).

FAQ

  • Q: Is Hoover read-write or read-only? A: Hoover is intended for read-only operations against a Cloud Foundry foundation.

  • Q: What do I need to run Hoover locally? A: A deployed cf-hoover service to target, Java, Maven, git/gh and Claude Desktop to act as the MCP client.

  • Q: Where is the project hosted and how do I build it? A: The implementation lives in the cf-kaizen GitHub repository (cf-toolsuite/cf-kaizen). Build with Maven (mvn install) after cloning the repo.

  • Q: How do I configure Claude Desktop to use Hoover? A: Edit claude_desktop_config.json, add an entry under “mcpServers” that runs java -jar with the -Ddefault.url set to your cf-hoover endpoint and the absolute path to the built JAR in your local .m2 repo; restart Claude Desktop.

  • Q: Can I target multiple Cloud Foundry foundations? A: Yes — configure the default.url (or additional entries) to point to different cf-hoover endpoints for different foundations.

  • Q: Is Hoover suitable for production control plane changes? A: No — Hoover is read-only and intended for inspection, chat, and learning workflows, not modification of platform state.