Instead of finding a server for every small integration, you describe the call you want and it becomes a tool on disk. The cost is a client restart before it can be used, and the code that gets written is yours to read.
An MCP server that creates other tools. A tool is described in natural language and saved as a Python scriptlet under the server's tools directory, with its definition written into tools.json alongside it. The new tool becomes usable after the client restarts. Two examples ship with it — a Bitcoin price lookup and a US ZIP-code weather forecast.
- New tools created from a natural-language description
- Each one saved as a Python scriptlet in the server's tools directory
- Its definition written into tools.json next to the script
- get_bitcoin_price, fetching the current Bitcoin price from CoinGecko
- get_weather_forecast, returning weather for US ZIP codes using geopy
Python with uv: the repository is cloned, a virtual environment created, and the package installed with uv pip install -e. The README marks the project work in progress and its setup uses Windows paths. Restart the client after creating a tool — a new one is not available until then.
Build from source — clone the repository and build it, then point your client at the binary
