Power your agent
पब्लिशर का इंस्टॉल। PlugMCP एंडपॉइंट नहीं।
Host a copy with our keys and logs.
रजिस्ट्री में अभी कोई पैकेज्ड रिलीज़ नहीं है। रिपॉज़िटरी का README देखें.
रिमोट URL या आपकी मशीन पर कमांड? दोनों इंस्टॉल में क्या अंतर है
PlugMCP पर चलाएँ
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
लॉन्चपब्लिशर से
sxmc)Sumac makes AI assistants stop guessing how your tools work.
It inspects the real tools already on your machine, turns them into structured profiles, and uses that knowledge to generate AI-host startup docs, client config, MCP wrappers, and reusable discovery artifacts from one Rust binary.
|
Sumac: bring out what your tools can do — one Rust binary to bridge skills, MCP, and APIs. Run any skill as an MCP server, any MCP server as a CLI, and any API from your terminal.
Stable 1.x line: Sumac now treats setup -> add -> status -> sync as the
maintained onboarding and reconciliation loop for day-to-day use.
If you only learn four commands, learn these:
sxmc setup --root .
sxmc add gh --root .
sxmc status --human
sxmc sync --root . --apply
When you want user-level host files instead of repo-local files, switch the
same workflow to --global:
sxmc setup --global
sxmc add gh --global
sxmc status --global --human
sxmc sync --global --apply
What they mean:
sxmc setup: onboard the common tools a repo usessxmc add <tool>: teach Sumac and your AI hosts one more CLIsxmc status: see what your AI knows, what is stale, and what to do nextsxmc sync: reconcile saved profiles and generated host artifacts as tools changeWithout Sumac, the same capability usually gets rebuilt several times:
Sumac collapses that into one installable binary (sxmc) with four core flows:
Skills -> MCP server
MCP server -> CLI
API -> CLI
CLI -> AI startup surfaces
That means less glue code, narrower MCP discovery, fewer retry turns, and much less repeated setup across Claude Code, Cursor, Gemini CLI, Copilot, Codex-style tools, and generic MCP clients. The CLI command is sxmc — short to type, same letters as the brand.
cargo install sxmc
Other channels:
packaging/npmpackaging/homebrew/sxmc.rbServe local skills over MCP:
sxmc serve
sxmc serve --transport http --host 127.0.0.1 --port 8000
Install a reusable skill into project-local or user-global skill storage:
sxmc skills install tests/fixtures/simple-skill --root .
sxmc skills install https://github.com/openai/skills/tree/main/skills/.curated/example-skill --global
sxmc skills update simple-skill --global
Inspect and call any MCP server from the terminal:
sxmc stdio "npx @modelcontextprotocol/server-memory" --list
sxmc stdio "npx @modelcontextprotocol/server-memory" create_entities 'entities=[{"name":"sxmc","entityType":"project","observations":["Rust MCP bridge"]}]'
Use a baked, token-efficient MCP workflow:
sxmc bake create memory --type stdio --source "npx @modelcontextprotocol/server-memory"
sxmc mcp servers
sxmc mcp info memory/create_entities --format toon
sxmc mcp call memory/create_entities '{"entities":[{"name":"sxmc","entityType":"project","observations":["Rust MCP bridge"]}]}'
Run an API as a CLI:
sxmc api https://petstore3.swagger.io/api/v3/openapi.json --list
sxmc api https://petstore3.swagger.io/api/v3/openapi.json findPetsByStatus status=available
Turn a CLI into startup-facing AI artifacts:
sxmc doctor
sxmc doctor --human
sxmc doctor --check --only claude-code,cursor
sxmc doctor --check --fix --only claude-code,cursor --from-cli gh
sxmc inspect cli gh --format toon
sxmc inspect cli curl --compact --format json-pretty
sxmc inspect cli cargo --depth 1 --format json-pretty
sxmc inspect cli gh --depth 2 --compact --format json-pretty
sxmc inspect batch git cargo brew --parallel 4 --compact --format json-pretty
sxmc inspect batch --from-file tools.txt --compact --format json-pretty
sxmc inspect batch --from-file tools.yaml --since 2026-03-22T00:00:00Z
sxmc inspect batch --from-file tools.yaml --compact # nested depth shows up as nested_profile_count
sxmc inspect diff git --before before.json --format json-pretty
sxmc inspect diff git --before before.json --format toon
sxmc inspect cache-stats --format json-pretty
sxmc inspect cache-invalidate cargo --format json-pretty
sxmc inspect cache-invalidate 'g*' --dry-run --format json-pretty
sxmc inspect cache-clear --format json-pretty
sxmc inspect cache-warm --from-file tools.toml --parallel 4 --format json-pretty
sxmc init ai --from-cli gh --coverage full --mode preview
sxmc init ai --from-cli gh --coverage full --host claude-code,cursor,github-copilot --mode apply
sxmc init ai --from-cli gh --coverage full --host claude-code --mode apply --remove
Use sxmc first when the surface is unknown:
sxmc inspect cli <tool> --depth 1 --format json-pretty
sxmc stdio "<cmd>" --list
sxmc mcp grep <pattern>
sxmc api <url-or-spec> --list
sxmc serve --paths <dir>
sxmc scan --paths <dir>
inspect cli executes a real command via subprocess spawn. It can inspect
installed binaries or explicit executable paths, but it does not see shell-only
aliases or functions from your interactive shell.
inspect batch --from-file reads one command spec per line. Blank lines and
lines beginning with # are ignored, trailing whitespace is trimmed, and inline
arguments are preserved, so lines like git status or "cargo" build work as
full command specs.
For structured batch input, .yaml / .yml and .toml files can define tools
with per-command depth overrides. Example YAML:
tools:
- command: git
depth: 1
- command: cargo
When a structured batch file sets depth: 1, full JSON output exposes nested
profiles under subcommand_profiles. Compact output keeps the summary smaller
and reports only counts like nested_profile_count.
Recent inspection hardening:
sxmc inspect cli gh now recovers top-level flags as well as grouped subcommandssxmc inspect cli rustup preserves global options like --verbose, --quiet, --help, and --versionsxmc inspect cli python3 avoids treating environment variables as subcommandssxmc inspect cli node --depth 1 keeps the inspect subcommand while using a cleaner runtime summaryGenerate shell completions:
sxmc completions zsh > "${fpath[1]}/_sxmc"
sxmc completions bash > ~/.local/share/bash-completion/completions/sxmc
sxmc stdio "<cmd>" --list replaces ad hoc JSON-RPC client scripts for MCP discovery.sxmc mcp grep "file" searches across baked MCP servers, which is hard to reproduce cleanly with one-off tooling.sxmc scan catches hidden Unicode, dangerous permissions, and prompt-injection patterns that plain grep misses.sxmc inspect cli ... plus sxmc init ai ... turns per-host AI setup into generated, reviewable artifacts.sxmc doctor makes the next move explicit for agents and humans: unknown CLI, unknown MCP server, unknown API, local skills you want to serve, or startup setup.sxmc inspect batch ... amortizes inspection startup when you need several CLI profiles in one pass.sxmc inspect cache-stats exposes profile-cache size and entry counts so repeated agent lookups are observable instead of opaque.sxmc inspect cache-invalidate ... and sxmc inspect cache-clear let you recover from stale inspection state without manual cache surgery.The current validation docs capture the real-world comparison set, token/turn estimates, and hidden retry-cost analysis.
1.xThe product name is Sumac. The command stays sxmc.
The maintained support boundary for the stable 1.x line is:
sxmc setupsxmc addsxmc doctorsxmc statussxmc sync--client and --hostSee:
sxmc setup / sxmc add: first-run onboarding and one-tool onboardingsxmc status / sxmc sync: maintained-state view and reconciliation loopsxmc doctor: startup-discovery health and repair guidancesxmc serve: expose skills as stdio or HTTP MCPsxmc skills: list, inspect, run, and generate skillssxmc stdio / sxmc http: raw MCP bridge and debugging layersxmc mcp: baked daily-use MCP workflowsxmc api / sxmc spec / sxmc graphql: API-to-CLI bridgesxmc scan: security scanning for skills and MCP surfacessxmc inspect / sxmc init / sxmc scaffold: CLI-to-AI inspection and scaffoldingsxmc doctor: startup-discovery status plus recommended first commandssxmc inspect batch: inspect several CLIs in one invocationsxmc inspect cache-stats: inspect cached profile inventory and sizesxmc inspect cache-invalidate / sxmc inspect cache-clear: selectively invalidate or fully reset cached CLI profilessxmc bake: saved connectionssxmc completions: shell completion generationsxmc inspect cli --depth 1--depth 2 for multi-layer CLIs such as ghsxmc inspect cli --compact for lower-context summariessxmc inspect batch --parallel ... when you need several profiles in one shotsxmc inspect cache-statssxmc inspect cache-invalidate <tool> or reset entirely with sxmc inspect cache-clearsxmc init ai --removeman pages without clobbering richer --help surfaces--skip-validate when you intentionally want to persist a broken or offline target--from-profile / inspect profile inputs now explain that sxmc expected a real CLI surface profile from sxmc inspect cli ...inspect cli targets must be real executables on PATH (or explicit paths), not shell-only aliases or functionssxmc mcp sessionAGENTS.md, CLAUDE.md, GEMINI.md, Cursor rules, and Copilot instructions from sxmc itself1.0.0 will promise, what evolves additively, and what remains out of scopeCLI -> AI host coveragecargo fmt --all
cargo clippy --all-targets --all-features -- -D warnings
cargo test
Use the validation flow before release:
bash scripts/certify_release.sh target/debug/sxmc tests/fixtures
bash scripts/smoke_real_world_mcps.sh target/debug/sxmc
MIT
Sumac: bring out what your tools can do — one Rust binary to bridge skills, MCP, and APIs. Run any skill as an MCP server, any MCP server as a CLI, and any API from your terminal.
टूल
अभी टूल सूची नहीं है। रिमोट सर्वर को पहले हेल्थ चेक के बाद सूची मिलती है।
FAQ
इस पेज पर Cursor, Claude Desktop, Claude Code या VS Code के लिए stdio कॉन्फ़िग कॉपी करें। यह पब्लिशर का इंस्टॉल इस्तेमाल करता है, PlugMCP प्रॉक्सी नहीं।
इस रिकॉर्ड में कोई ज़रूरी एनवायरनमेंट वेरिएबल दर्ज नहीं है।
Sumac stdio पर लोकल चलता है।
पिछली जाँच 2026-11-05 को हुई। Sumac: bring out what your tools can do — one Rust binary to bridge skills, MCP, and APIs. Run any skill as an MCP server, any MCP server as a CLI, and any API from your terminal.