Korg Introspect Mcp
Expose any korg:introspect@v1-aware CLI as a typed Claude Code MCP tool with declared side-effects respected at invoke time.
Overview
korg-introspect-mcp is an MCP server for the Build phase that wraps korg:introspect@v1 binaries as agent tools with honored side-effect metadata.
What is this MCP server?
- NPM package @korgg/introspect-mcp v0.1.1 with stdio MCP transport
- Adapts korg:introspect@v1 metadata so agents see structured tool definitions
- Honors declared side-effects on binaries instead of treating every wrapper as read-only
- Pairs with the New1Direction/korg repo for introspect-aware command authoring
- Thin bridge layer—your logic stays in the binary; MCP handles discovery and invocation
- Server version 0.1.1
- NPM identifier @korgg/introspect-mcp
- Targets korg:introspect@v1 contract
Community signal: 3 GitHub stars.
What problem does it solve?
Your custom CLI is perfect for automation but agents only see opaque shell snippets with no declared read/write side-effects.
Who is it for?
Builders maintaining korg-introspect CLIs who want Claude Code to call them as named tools with effect boundaries.
Skip if: Projects without introspect metadata, HTTP-only APIs, or teams that do not run Node-based MCP servers.
What do I get? / Deliverables
After registration, introspect-aware binaries appear as structured MCP tools so agents invoke them with declared effects instead of raw shell guesses.
- MCP-discoverable tools backed by local introspect binaries
- Side-effect declarations enforced at the wrapper layer
- Reduced shell glue when agents run repo-specific commands
Recommended MCP Servers
Journey fit
Wrapping binaries as agent tools happens while you integrate local commands and scripts into the Build stack. Integrations is the shelf for bridging external executables into MCP rather than authoring a new skill from scratch.
How it compares
Introspect binary wrapper MCP, not a general remote API connector or packaged Claude skill.
Common Questions / FAQ
Who is korg-introspect-mcp for?
Developers using the Korg introspect convention who want MCP hosts to discover and run their local binaries safely.
When should I use korg-introspect-mcp?
Use it while integrating custom commands during Build once binaries export korg:introspect@v1 schemas and side-effects.
How do I add korg-introspect-mcp to my agent?
Install @korgg/introspect-mcp from npm, add the io.github.New1Direction/korg-introspect-mcp stdio server to your MCP config, and point tools at introspect-aware binaries on your PATH.