jmunch-suite

jmunch-suite-plugin

Plugin-scope wrapper for jgravelle's jmunch MCP suite.

What

Bundles three MCP servers + four slash commands as plugin-scope so they propagate to Task()-spawned subagents:

MCP servers:

• jcodemunch — code intelligence (symbol graphs, blast radius, dead code, hotspots) — replaces raw grep/find on indexed Python/TS/JS/Go codebases
• jdocmunch — documentation intelligence (section retrieval, broken-link detection, doc coverage) — replaces raw Read on indexed docs
• jdatamunch — tabular data intelligence (CSV/Excel/Parquet/JSONL) — replaces raw pandas spelunking

Slash commands (UI to the MCP servers):

• /find <pattern> [file_pattern?] → mcp__jcodemunch__search_text
• /look <symbol> [decorator?] [kind?] → mcp__jcodemunch__search_symbols
• /outline <path> → mcp__jcodemunch__get_file_outline
• /blast <symbol_id_or_path:line> → mcp__jcodemunch__get_blast_radius

Why this plugin exists

Project-scope and user-scope MCPs do NOT inherit to Task()-spawned subagents. Only plugin-scope MCPs do. See Claude Code Issue #38920.

Empirical receipt (2026-05-08): Phase H of the staffcloud OS audit shipped a "Phase 0: call jcodemunch_guide first" directive into 32 reviewer-agent system prompts. The directive REACHED the agents (verified — they correctly attempted MCP-first), but the runtime tools were not actually accessible because the project-scope jcodemunch/jdocmunch registrations don't propagate. This plugin closes that gap by re-registering the same servers at plugin-scope.

Install

The directory is a self-contained marketplace. Register in ~/.claude/settings.json:

{
  "plugins": {
    "enabledPlugins": {
      // ... existing plugins ...
      "jmunch-suite@jmunch-plugins": true
    }
  },
  "extraKnownMarketplaces": {
    // ... existing marketplaces ...
    "jmunch-plugins": {
      "source": {
        "source": "directory",
        "path": "/home/danny/projects/jmunch-suite-plugin"
      }
    }
  }
}

Restart Claude Code. The three MCP servers become available as mcp__jcodemunch__*, mcp__jdocmunch__*, mcp__jdatamunch__* in BOTH the main session AND every Task()-spawned subagent.

After install

Remove the duplicate project-scope and user-scope registrations:

# Remove project-scope jcm/jdm (manually edit ~/projects/staffcloud/.mcp.json
# to delete the jcodemunch + jdocmunch entries)

# Remove user-scope jdat
claude mcp remove jdatamunch -s user

The plugin-scope versions take over.

Verify subagent inheritance

Spawn a Task() subagent with subagent_type="senior-reviewer" or any project agent. The agent should see `mcp__jcodemunch__*` in its tool inventory and successfully call `mcp__jcodemunch__plan_turn(query=...)` without falling back to bash grep.

Source

The wrapped MCP servers are owned by jgravelle — install via:

uv tool install jcodemunch-mcp
uv tool install jdocmunch-mcp
uv tool install jdatamunch-mcp

This plugin only re-declares them at plugin-scope; it does not vendor or modify the source.