# Honey MCP Server [Health: Active]

**Category:** ☁️ Cloud Platforms  
**Repository:** https://github.com/shareed2k/honey  
**GitHub Stars:** 3  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/honey-mcp-server

## Description
Search instances across GCP, AWS, K8s, Consul & Proxmox

## Claude Desktop Quick Installation
Heuristic fallback — verify the package name and runner against the repository README before running it. Uses `npx` (confidence: low):

```json
"mcpServers": {
  "honey-mcp-server": {
    "command": "npx",
    "args": ["-y","honey-mcp-server"]
  }
}
```

## Documentation

## What Honey MCP Server MCP server does

Honey provides a single search workflow for instances spread across cloud, container, cluster, service-discovery, virtualization, and storage backends. The documented providers include GCP, AWS, Kubernetes, Docker, Consul, Proxmox, and TrueNAS. Searches can cover all configured backends or be narrowed to selected providers and a name substring.

The Honey MCP Server MCP server makes this operational inventory available to MCP-compatible clients. Honey also offers the same underlying application through an interactive terminal UI, JSON output, and a web UI. After finding a result, Honey can support SSH access, Docker `exec`, or recipe execution according to the configured capabilities and workflows.

## How it works

Honey connects to the backends configured by the operator and searches them in parallel. A basic command searches all configured sources, while provider filters can restrict a request to sources such as AWS and Kubernetes. JSON output is available for command-line workflows; the MCP mode is intended for clients listed in the project documentation, including Cursor, LM Studio, and OpenCode.

The project is implemented as a Go CLI and can be built from source with Go 1.26.2 or newer. It can also be installed through the project's Homebrew cask or Debian/Ubuntu packages. The Debian package installs the `honey` executable, a systemd service, an example configuration file, and a plugin initialization shim.

## Setup and configuration

Running Honey requires credentials for each backend that will be queried. Provider-specific credential and configuration details are maintained in the project's provider documentation. The packaged Linux setup places an example configuration at `/etc/honey/config.yaml`; operators edit that file before enabling the service with systemd.

A local build uses `go build -o honey ./cmd/honey`. The repository also documents Homebrew installation with `brew install --cask shareed2k/tap/honey`. On Debian or Ubuntu, installation uses a downloaded release package with `dpkg -i`.

Docker-related workflows need access to the Docker socket. Package installation does not grant that access automatically. An administrator must explicitly add the `honey` service user to the Docker group and restart the service if Docker access is required. The package recommends `tmux`, `shellcheck`, and `python3-flake8` for recordings and recipe linting; these are auxiliary tools rather than MCP requirements.

## Tools and capabilities

The provided material supports these capabilities:

- Search instances across configured GCP, AWS, Kubernetes, Docker, Consul, Proxmox, and TrueNAS providers.
- Search all configured providers or filter by provider and name substring.
- Return command-line results as JSON.
- Connect to matching instances over SSH.
- Run `docker exec` operations where Docker access is configured.
- Execute documented recipes and use Honey macros.
- Expose the application through an MCP server, TUI, or web UI.

The exact MCP tool names and request schemas are not included in the supplied material, so they should be checked in the MCP-specific documentation before client configuration.

## Limitations and notes

Honey is explicitly labeled alpha software. APIs, configuration schema, and CLI flags may change between releases without notice. Backend coverage and available actions depend on the providers configured and the credentials supplied for them.

The Honey MCP Server MCP server is not described as a hosted service in the supplied material; the documentation presents Honey as software installed or built by the operator. No universal credential format is specified because each backend has its own requirements. Docker actions also carry an operational security consideration: membership in the Docker group is root-equivalent, so access should be granted deliberately.

The repository is licensed under MIT. Some included research algorithms have separate Creative Commons notices, including CC BY 4.0 and CC BY-NC-ND 4.0, so downstream users should review those notices when relying on those components.

_Full upstream README: https://allmcps.com/mcp/honey-mcp-server/readme_