gridctl

gridctl is an open-source MCP gateway and skill library. It aggregates every MCP server you use behind a single local endpoint, and serves your Agent Skills to clients as MCP prompts - defined in one YAML file, applied with one command. Instead of maintaining a separate JSON config for Claude Desktop, another for Cursor, another for VS Code, and hand-editing all of them every time you add a server, gridctl holds one declarative spec and writes the client configs for you. HOW IT WORKS 1. Install the single Go binary (curl one-liner, Homebrew, or go install) 2. Declare your servers and skills in gridctl.yaml 3. Run "gridctl apply", then "gridctl link --all" - clients wired up, no manual JSON editing WHAT YOU GET - Stack as code: validate, plan, apply, export. Background drift detection flags when reality diverges from your spec. - 15 clients auto-linked: Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Gemini, Zed, and more. "gridctl import" runs it in reverse to adopt an existing setup. - Token control: per-server tool whitelists, cross-server groups, per-client scoping, and TOON/CSV output conversion that cuts 25-61% off tabular payloads. - Skill library and packs: author SKILL.md in the web UI, project skills and subagents onto disk for file-reading clients, or ship a whole team setup as one versioned git pack. - Visual stack canvas: every client, the gateway, and every server with live health, transport, and tool counts. SUPPLY CHAIN SECURITY gridctl treats every MCP server as untrusted input, because that is what it is. - Tool definition pinning: every tool description and schema is fingerprinted on first sight. A server that quietly rewrites a tool description surfaces as a reviewable diff instead of silently reaching your agent. - Skill document scanning: skills get the same treatment, plus injection heuristics for hidden instructions, zero-width characters, and Unicode homoglyphs. - Scoped exposure: clients only see the tools you grant them. A whitelist is a boundary, not a suggestion. TOKEN GUARDRAILS "gridctl optimize" reports projected weekly token impact per server and returns paste-ready remediation. Most stacks are paying for hundreds of tool definitions that no client ever calls. Single Go binary. Apache 2.0. No runtime dependency beyond a container engine, and only if your stack actually deploys containers.