About

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 under the MIT License.

The work spans 78 public repositories in the mcp-tool-shop-org organization: servers for the Model Context Protocol, command-line tools, model training and dataset pipelines, image and audio production tooling, agent infrastructure, and the games that tooling exists to make. All of it is designed to run on a workstation you own.

What we build

  • MCP servers for tool discovery, local-model job delegation, speech, translation, and vision. They work with Claude Code, Claude Desktop, Cursor, VS Code, and any other MCP client.
  • Training and dataset pipelines: headless fine-tuning with GGUF export, canon-bound visual datasets, contamination-checked code datasets, and verifiers for training steps.
  • Image and media tooling: programmatic ComfyUI, pre-submission workflow gates, sprite generation, GLB-driven video, and audiobook production.
  • Agent infrastructure: multi-agent orchestration, context routing, cross-family output verification, and runtime health for coding agents.
  • Developer tooling: a release quality gate, Astro site templates, a repo knowledge base, and package download analytics.
  • Games and game tooling: a deterministic RPG simulation engine, world authoring, adaptive soundtracks, and playable titles.

The catalog lists every repository with its status, install command, and release history.

A sister organization for testing

Testing methods live in a second organization, dogfood-lab: an open workshop for how AI-assisted software should be verified. Its two main projects are testing-os, an operating system for testing with provenance-confirmed evidence stores and learning loops, and study-swarm, a protocol for grounding design decisions in cited research and verifying every citation with a different model family. The tools published here are developed with both.

How we work

  • Local-first. Core functionality never requires an API key or a hosted service. Where a tool offers cloud routing, it is opt-in and falls back to local execution.
  • MCP-native. Tools compose through the Model Context Protocol rather than bespoke integrations.
  • Gated releases. Every tagged release passes the shipcheck gate: a security policy and threat model, structured errors with exit codes, current documentation and changelog, and clean packaging. Versions follow semantic versioning and publish to npm or PyPI from CI.
  • Deterministic where it matters. Same input, same output in critical paths. Simulation engines, verifiers, and dataset builders are reproducible by design.
  • Documented in eight languages. Most repositories ship READMEs in English, Japanese, Chinese, Spanish, French, Hindi, Italian, and Brazilian Portuguese, translated locally with our own translation server.
  • Accessible by default. Low-vision-first CLI output and WCAG tooling, built in rather than bolted on.

Stack

  • Python
  • TypeScript
  • Rust
  • C#
  • Godot 4
  • Astro
  • MCP
  • Ollama
  • ComfyUI
  • SQLite
  • CUDA

Developed on Windows with NVIDIA hardware. Most tools are cross-platform; where a tool is Windows-only, its README says so.

Who

MCP Tool Shop is a one-person studio. Most of what is published here is built with the same local AI tooling it ships, which is the point: tools are used in production before they are released. Development happens in the open, and every repository accepts issues and pull requests.

This site

The catalog is generated from the GitHub organization by a scheduled sync; editorial fields such as taglines and install commands are reviewed by hand. Spotlight picks and their receipts are documented in the Trust Center. The site's source is public at mcp-tool-shop/mcp-tool-shop.