Skip to content
MCP Server Directory logo
developer-tools

Butler

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

Reviewed overview

MCP server overview

What is Butler?

Butler is the MCP (Machine Chat Protocol) server implementation inside the cf-kaizen project that enables continuous learning from and chatting with one or more Cloud Foundry foundations. It exposes read-and-write operations via one or more deployed cf-butler instances and is implemented in Java/Spring (Spring Boot / Spring AI).

How to use Butler?

  • Prerequisites: have one or more cf-butler instances deployed to your target Cloud Foundry foundation(s) and install required CLIs/SDKs (git, gh, Java, Maven; sdkman optional). Install Claude Desktop if you want the desktop MCP client integration.
  • Build: clone the repo (gh repo clone cf-toolsuite/cf-kaizen) and run mvn install to produce the server JAR in your local Maven (.m2) repository.
  • Integrate with Claude Desktop: edit the Claude Desktop developer configuration file (claude_desktop_config.json) and add an MCP server entry that runs the Butler server JAR with a -Ddefault.url pointing at the target cf-butler endpoint(s). Use the absolute path to the built JAR found under your local .m2 repository. Restart Claude Desktop to pick up the new tool.
  • Run standalone: you can also run the generated JAR directly with Java as a service if you prefer not to use the Claude Desktop integration.

Key features

  • Bridges Claude/assistant clients to Cloud Foundry foundations via cf-butler instances
  • Supports read and write operations against CF foundations
  • Integrates as an MCP server (works with Claude Desktop developer tools)
  • Java / Spring Boot implementation; built with Maven
  • Can target one or multiple Cloud Foundry foundations (multi-foundation configuration)

Typical use cases

  1. Chat-based operational assistant for Cloud Foundry (query apps, services, orgs, spaces)
  2. Read/write automation for CF foundations (create/update/delete resources via conversational prompts)
  3. Troubleshooting and diagnostics through conversational queries
  4. Auditing and reporting on multiple CF foundations from a single MCP endpoint
  5. Integrating conversational UIs (Claude Desktop) into CF operator workflows

FAQ

  • What do I need before using Butler?

Deploy one or more cf-butler instances to the target Cloud Foundry foundations and have git, gh, Java and Maven available. Claude Desktop is optional but required for the built-in MCP client integration.

  • How do I build the Butler server JAR?

Clone cf-kaizen and run mvn install. The server JAR will be placed in your local Maven repository (~/.m2/repository/...).

  • How do I configure Claude Desktop to use Butler?

Add an MCP server entry in claude_desktop_config.json that runs java -jar against the built server JAR and include a -Ddefault.url that points to your cf-butler endpoint. Restart Claude Desktop after editing.

  • Can Butler target multiple foundations?

Yes — configure multiple MCP server stanzas or provide multiple target URLs in the configuration as described in the project docs.

  • Is Claude Desktop required?

No. Claude Desktop is required only if you want the desktop MCP integration; the server JAR can be run directly with Java for headless or service deployments.

  • Where is the built artifact located?

After mvn install the artifact is in your local Maven repository under ~/.m2/repository/org/cftoolsuite/.../cf-kaizen-butler-server-<version>.jar.

  • Is this safe to use in production?

Security and production readiness depend on how you deploy cf-butler and the Butler server (network exposure, authentication, and CF access controls). Follow your org’s security practices and ensure CF credentials and endpoints are protected.