Open-source tooling for local-first AI development.
MCP servers, command-line tools, training and dataset pipelines, and game-production tooling
that run on your own hardware. MIT licensed.
Website · Tool catalog · Releases · npm · Discussions
MCP Tool Shop is an independent software studio. We build the tools we use to develop AI-assisted software and games, and we publish them as open source. Everything is designed to run locally: on a workstation GPU, with Ollama, ComfyUI, and the Model Context Protocol, and with no cloud dependency for core functionality.
| Area | Repositories | What they do |
|---|---|---|
| MCP servers | tool-compass · ollama-intern-mcp · mcp-voice-soundboard · polyglot-mcp · plain-sight | Tool discovery by intent, local-model job delegation, text-to-speech, GPU translation, image description |
| Training and datasets | backpropagate · style-dataset-lab · repo-dataset · backprop-trace · runforge-vscode | Headless fine-tuning with GGUF export, canon-bound visual datasets, contamination-checked code datasets, training-step verification |
| Image and media pipelines | comfy-headless · comfy-preflight · sprite-foundry · armature · audiobooker | Programmatic ComfyUI, pre-submission workflow gates, sprite generation, GLB-driven video, multi-voice audiobooks |
| Agent infrastructure | role-os · loadout-os · prism-verify · claude-guardian · research-os | Multi-agent orchestration, context routing, cross-family output verification, runtime health, research control plane |
| Developer tooling | shipcheck · site-theme · repo-knowledge · registry-stats · npm-launcher | Release quality gates, Astro site templates, repo knowledge base, package download stats, verified binary launcher |
| Games and game tooling | ai-rpg-engine · world-forge · motif · saints-mile · roll | Deterministic RPG simulation, 2D/2.5D world authoring, adaptive soundtracks, a frontier JRPG, dice and probability engine |
| Ledger and verification | attestia · xrpl-lab · xrpl-camp · repomesh | Financial truth infrastructure, XRPL training, release verification for repo networks |
The table above is a selection. Every public repository is classified by area, lane and install path in the Ecosystem Specification, with a machine-readable catalog.yaml.
The full catalog, with install commands and release history, is at mcptoolshop.com/tools.
# Find MCP tools by describing what you need
npx @mcptoolshop/tool-compass
# Drive ComfyUI from Python, no node canvas required
pip install comfy-headless
# Fine-tune a local model and export GGUF for Ollama
pip install backpropagate
# Run the release quality gate on your own repository
npx @mcptoolshop/shipcheck auditMCP servers work with Claude Code, Claude Desktop, Cursor, VS Code, and any other MCP client.
- Local-first. Core functionality never requires an API key or a hosted service. Optional cloud routing is opt-in and falls back to local.
- A release gate, not a vibe check. Every tagged release passes shipcheck: security policy and threat model, structured errors with exit codes, current docs and changelog, clean packaging.
- Semantic versioning. Every release is tagged on GitHub and published to npm or PyPI from CI.
- Documented in eight languages. Most repositories ship READMEs in English, Japanese, Chinese, Spanish, French, Hindi, Italian, and Brazilian Portuguese, translated locally with polyglot-mcp.
- Accessible by default. Low-vision-first CLI output and WCAG tooling via accessibility-suite.
Testing methods live in dogfood-lab, an open workshop for how AI-assisted software should be verified. The tools in this organization are developed with both of its main projects.
| Project | What it is | Install |
|---|---|---|
| testing-os | Operating system for testing in the AI era: protocols, provenance-confirmed evidence stores, and learning loops. Handbook | npx @dogfood-lab/dogfood-swarm |
| study-swarm | Ground design decisions in cited research, then verify every citation with a different model family before it becomes canon. Handbook | npx @dogfood-lab/study-swarm |
Every repository's README states which lane it is in:
| Lane | Meaning |
|---|---|
| Shipped | Tagged releases, CI, an install command, and a support policy |
| In development | Active work, pre-1.0 or not yet released. APIs may change |
| Archive | Retired prototypes and reusable patterns, kept in prototypes |
- Questions and ideas: GitHub Discussions
- Bugs and feature requests: open an issue on the relevant repository. See SUPPORT.md for what to include.
- Security: use private vulnerability reporting on the affected repository. Do not open a public issue. See SECURITY.md.
- Contributing: CONTRIBUTING.md and the Code of Conduct.
