Repository navigation
docs: add MCP setup guides for Claude Desktop and LM Studio - #9
Conversation
Closes #2 and #3 - docs/mcp-clients/claude-desktop.md: config file location on Windows and macOS, the Clippy Vision mcpServers entry, restart and verification, and example questions to try - docs/mcp-clients/lm-studio.md: adding Clippy Vision as an MCP server in LM Studio, a recommended tool-calling model, a quick test, and a note on what stays on your machine - Both linked from README and docs/mcp.md
protocorn
left a comment
There was a problem hiding this comment.
Hi @Furox-Art, thanks a lot for this, and welcome! The Claude Desktop guide is really solid. I checked it against electron-ui/electron/lib/mcp.js and the config path, the mcpServers shape, the env vars, the full-quit step and the Disconnect behavior all match what the app actually does.
One thing I have to ask you to change, though: #3 (the LM Studio guide) was already claimed by @Afrin-banu-A a few hours before this PR and I assigned it to them, so it wouldn't be fair to merge a second LM Studio guide over their work. Could you split this PR down to just #2?
- Drop
docs/mcp-clients/lm-studio.md, plus the LM Studio links inREADME.md(both the "client guides" line and the docs table row) and indocs/mcp.md. - Change the description to
Closes #2only.
If Afrin ends up releasing #3, I'll ping you first so you can pick it back up. (Small heads-up for whoever writes it: names like qwen3:8b are Ollama tags, and LM Studio lists models under different names, so the guide should use the name and quant shown in LM Studio itself.)
Two small fixes in claude-desktop.md while you're in there:
- In "Check the tools appear", I couldn't confirm a Help → Enable Logging menu in Claude Desktop. The reliable pointer is the MCP log files:
%APPDATA%\Claude\logs\mcp*.logon Windows and~/Library/Logs/Claude/mcp*.logon macOS. Could you swap that in? - In the macOS example,
/usr/bin/python3is just Apple's stub, and Clippy resolves whateverwhich python3returns (often/opt/homebrew/bin/python3). Please add a line saying that path is a placeholder too, same as you did for Windows.
Once those are in, I'll approve and merge. The Python test workflow hasn't run on your fork yet, but since this PR only touches docs, that won't hold it up.
(I'm Grok Bot, the AI assistant maintaining this experimental copy of clippy-vision for protocorn.)
- Drop the LM Studio guide (#3 was claimed by another contributor) - Replace the Help → Enable Logging pointer with the MCP log file paths on Windows and macOS - Note that the macOS command path is a placeholder too, since which python3 resolves to Homebrew's python on many machines
|
Done — addressed all three points:
Good catch on the Ollama tag names in LM Studio vs qwen3:8b — noted for whoever picks up #3. |
|
Done — addressed all three points:
Good catch on the Ollama tag names — noted for whoever picks up #3. |
|
Thanks for removing the duplicate LM Studio guide and its links! I appreciate you noting the Ollama vs. LM Studio model naming difference as well. I'll keep that in mind while working on issue #3. |
protocorn
left a comment
There was a problem hiding this comment.
Thanks @Furox-Art, that's all three points covered. I re-read the guide: the LM Studio file and its links are gone, the MCP log paths are right for both platforms, the macOS command placeholder note is clear, and the ../usage.md#privacy-settings and ../mcp.md#tool-reference anchors resolve. GitGuardian is green, and since this only touches Markdown the Python test run (still waiting on fork approval) doesn't affect it. Approving and merging now. This closes #2, and it's the first outside contribution to this copy, so thank you!
@Afrin-banu-A, thanks for keeping an eye on it. #3 is all yours, and feel free to link this Claude Desktop guide from yours so the two read as a set.
(I'm Grok Bot, the AI assistant maintaining this experimental copy of clippy-vision for protocorn.)
Closes #2
Adds
docs/mcp-clients/claude-desktop.md— a step-by-step Claude Desktop setup guide:mcpServersentryLinked from the README's MCP section and from
docs/mcp.md.(The LM Studio guide was dropped from this PR per review feedback — issue #3 was claimed by another contributor.)