Kal contributor

Charm

Register Charm as an MCP-backed operations marketplace so your agent can run diagnostics, release checks, and safer tool workflows with less context bloat.

Overview

Charm is a plugin marketplace for the Operate phase that exposes an MCP operations toolkit with diagnostics, release checks, and multi-agent adapter support.

What is this marketplace?

  • MCP server over stdio with charm doctor for adapter-aware diagnostics
  • charm release-check and release-check --ci for beta release-candidate readiness
  • Explicit security modes: compat versus strict
  • Adapter coverage for Claude Code, Cursor, Codex, Gemini CLI, VS Code Copilot, Zed, and more
  • Prompt-only onboarding via bootstrap URL when not using the Claude marketplace path
  • 1 plugin in marketplace listing
  • 10+ named agent platform adapters in README coverage table

Compatible agents: Claude Code, Cursor, Codex, Windsurf

Community signal: 2 GitHub stars.

What problem does it solve?

Agent sessions balloon with repeated project context and lack a single MCP layer for safe, observable, repeatable ops across Claude, Cursor, and Codex.

Who is it for?

Power users running multiple coding agents who want MCP-level diagnostics, RC checklists, and strict security mode in one beta toolkit.

Skip if: Beginners who only need a single install-and-forget skill with no MCP or CLI maintenance.

What do I get? / Deliverables

After setup, you run charm doctor and release-check locally and wire MCP stdio so agents use indexed, mode-aware tooling instead of ad-hoc shell exploration.

  • Running Charm MCP server over stdio
  • doctor and release-check command outputs for local RC validation
  • Adapter-aligned config for supported agent platforms

Plugins in this marketplace

1 plugin — install individually after you add the marketplace.

Recommended Marketplaces

Journey fit

Charm is pitched as an operations toolkit with doctor and release-check; Operate is the canonical home even though MCP hooks apply during Build and Ship. Monitoring fits observability, diagnostics, and release-readiness checks that Charm emphasizes over raw feature coding.

How it compares

MCP server and ops marketplace, not a lightweight single-skill coding assistant.

Common Questions / FAQ

Who is Charm for?

Solo builders and small teams standardizing agent workflows across Claude Code, Cursor, Codex, and similar tools with MCP diagnostics.

When should I use Charm?

Use it when you need release-candidate checks, doctor-style health reports, or stricter tool execution during build-through-operate agent work.

How do I add Charm to my agent?

Add the qkal/Charm Claude plugin marketplace, or fetch and follow https://raw.githubusercontent.com/qkal/Charm/refs/heads/main/Charm for prompt-only onboarding; point MCP clients at start.mjs as documented.

This week for builders

Five minutes, every Monday — the tools, releases and tactics for shipping solo.

unsubscribe anytime.