MCP Helm Server

Created By
zekker6a year ago
MCP server for Helm package manager
Overview

what is MCP Helm Server?

MCP Helm Server is a server that provides tools for interacting with Helm repositories and charts, enabling AI assistants to query Helm repositories, retrieve chart information, and access chart values without requiring local Helm installations.

how to use MCP Helm Server?

To use MCP Helm Server, clone the repository, build the binary, and run the server. Configure your MCP client to connect to this server, which implements the standard MCP protocol for tool discovery and execution.

key features of MCP Helm Server?

  • list_repository_charts: Lists all charts available in a Helm repository.
  • get_latest_version_of_chart: Retrieves the latest version of a specific chart.
  • get_chart_values: Retrieves the values file for a chart (latest version or specific version).

use cases of MCP Helm Server?

  1. Querying Helm repositories for available charts.
  2. Retrieving the latest versions of charts for deployment.
  3. Accessing specific chart values for configuration.

FAQ from MCP Helm Server?

  • Can I use MCP Helm Server without local Helm installation?

Yes! MCP Helm Server allows you to interact with Helm repositories without needing a local Helm installation.

  • What are the prerequisites for building MCP Helm Server?

You need Go 1.24.3 or later to build from source.

  • Is MCP Helm Server open-source?

Yes! MCP Helm Server is available on GitHub.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
zekker6
Star
2
Language
Go
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

42 minutes ago