Your first report
Install metalworks with a provider SDK, and set one key — any provider works (embeddings default to a local model, so there’s no second key to set):What you can do with it
Run demand research once, then turn that one report into whatever you need next. The work falls into five stages — each step is a single call:
New here? Walk one idea from start to finish in the end-to-end walkthrough.
Why it’s not just another AI tool
Most AI research tools make up plausible-sounding answers. metalworks doesn’t. It reads real conversations across real sources, and anything it can’t back with an actual quote, it drops. When the demand isn’t there, it tells you — instead of inventing an opportunity. That’s what makes the output safe to act on. See why you can trust the output.Four ways to use it
The same engine, whichever fits your workflow:- Python library —
from metalworks import Metalworks. The full toolkit, embeddable. → SDK reference - CLI —
metalworks research run --question "...", thenmetalworks build init, etc. → CLI - MCP server —
metalworks mcp serve. Drive it from any MCP-aware agent or app. → MCP tools - Claude Code plugin —
/demand-report,/build-spec, and more as slash commands. → Claude Code plugin