This is a bridge, not a toolkit: what your client sees is decided on the Toolhouse side, and changing one environment variable changes the entire tool set. That makes it easy to keep separate bundles for separate jobs and switch between them without touching the client. The Windows UTF-8 flag is the one non-obvious requirement, and it is documented rather than left to be discovered.
An MCP server that provides access to tools from the Toolhouse platform. Which tools appear depends on the bundle you name in the configuration, so the surface is whatever you assembled on Toolhouse rather than a fixed list.
- The tools in the Toolhouse bundle you point it at, available to any MCP client
- A single config block that swaps the whole tool set by changing the bundle name
A Toolhouse API key as `TOOLHOUSE_API_KEY` and the bundle name as `TOOLHOUSE_BUNDLE`. On Windows, set `PYTHONUTF8` to 1 — some tools need it to work. Launch with `uv` running `mcp-toolhouse`, or install for Claude Desktop through Smithery. The package is `mcp-toolhouse` (0.1.0 in pyproject).
One command plus a key — npx -y @smithery/cli install @SecretiveShell/MCP-toolhouse --client claude, then supply credentials