PicPrepConnect your AI assistant.
Pick the assistant you use. Each page has the exact steps, how to check it works, and what to try first. About two minutes.
Available at launch. The connector, picprep-mcp, is not published yet, so the commands on this page will not work until PicPrep launches. The steps are the ones you will follow then.
- Claude CodeAnthropic's coding agent in the terminal. A plugin brings the connector and the skills together.
- Claude DesktopThe Claude app for macOS and Windows. One click, with a bundle that needs nothing else installed.
- OpenAI CodexOpenAI's coding agent: the CLI, the app and the IDE extension. A plugin, or one command.
- CursorOne click from an install link, or a few lines in Cursor's MCP settings.
- Gemini CLIGoogle's terminal agent. An extension brings the connector and the skills together.
- VS Code (GitHub Copilot)Copilot's agent mode in VS Code, through a workspace or user MCP file.
- WindsurfCascade in Windsurf, and Devin Desktop, its successor.
- ClineThe Cline extension, through its MCP servers settings.
- ZedZed's assistant, where MCP servers are called context servers.
- Google AntigravityGoogle's agent IDE and its CLI.
- OpenCodeThe open-source terminal agent.
- GooseBlock's open-source agent, for one session or kept.
- Devin CLIDevin on your own computer. A Devin cloud session cannot reach PicPrep.
- oh-my-piThe omp terminal agent.
- Any other MCP clientAnything that can run a local MCP server: the two settings it needs.
The same for all of them
The connector is picprep-mcp: free, with no dependencies. An assistant runs it as a local command, and it passes messages between the assistant and PicPrep on your computer.
npx -y picprep-mcpAn assistant that runs only in the cloud, such as a chat website or a cloud agent session, cannot reach an app on your computer. Use one that runs on the computer where PicPrep is.