VS Code RipClip why_it_worked
How to: VS Code RipClip why_it_worked
Add RipClip to VS Code
-
01
Open .vscode/mcp.json and merge this in. Keep any servers already there.
{
"servers": {
"ripclip": {
"type": "http",
"url": "https://ripclip.org/mcp/"
}
}
}-
02
Save the file and restart VS Code.
-
03
Ask for something why_it_worked does. VS Code lists the server's tools on connect and calls why_it_worked itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that RipClip's identifier in your config matches the one above exactly.
Requires agent mode. MCP: Open User Configuration puts the same block in every workspace. VS Code docs
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 9 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.