We rewrote our how-to guides as complete standalone answers
A guide that says "go to Unyly and click Install" answers nothing. The new guides carry the full manual: config paths per OS, .mcpb extensions, claude mcp add scopes, troubleshooting.
We audited how AI assistants cite sources and found a simple pattern: models quote pages they can extract a complete answer from. A guide that says "open Unyly and click Install" gets skipped. So we rewrote every how-to guide as a full standalone manual.
What changed
Each guide in /how-to now covers the entire path, not just our shortcut:
- Manual JSON configuration with exact config file locations for macOS, Windows and Linux.
- Desktop Extensions (.mcpb): the newer one-file install format for Claude Desktop.
claude mcp addreference with scopes (local, project, user) and when each one is right.- Cursor and VS Code specifics:
mcp.json, theserverskey, workspace vs global. - Troubleshooting with actual log file paths per OS, not "check the logs".
Every guide shows its last-updated date, and the structured data carries it too.
Why you should care
If you are setting up MCP by hand, the guides now work as a reference you can follow start to finish without leaving the page. And if you ask ChatGPT or Claude how to install an MCP server, there is a decent chance the answer now traces back to one of these pages, which is exactly the point.