Your model can do what you can do in the studio, through the same tools.
Connect it
From the desktop app. Open Settings, Model, and copy the command under Connect Claude Code. Run it in a terminal, then start Claude Code: it adds knitted to Claude Code for every folder you work in. Or paste the command into Claude Code and ask it to connect. Other apps that speak MCP over HTTP take the address underneath it. It works while knitted is open. The address holds a key, so keep it to yourself; Make a new address shuts the old one.
From a clone of the repository. Add the stdio server to your model's MCP settings, using the path to your clone:
{
"mcpServers": {
"knitted": {
"command": "node",
"args": ["/path/to/knitted-studio/packages/mcp/src/server.mjs"]
}
}
}
Then restart your model's app so it picks up the new tools.
What to ask
- "List my projects."
- "Show me the launch story Pattern. Which Stitches are locked?"
- "Fill the headline with something short about our spring sale."
- "Knit six of those."
What it cannot do
It cannot change a locked Stitch. If it tries, knitted refuses and tells your model which slot was refused and why. Your model will tell you, so nobody thinks a change happened when it did not. Only a person unlocks a Stitch, in the studio.
Keys and privacy
The studio's own model uses a key you bring, in Settings, Model. Claude Code and other apps use their own. Text you send to a model goes to that model's provider. Nothing else leaves your computer.