Document setup for more MCP clients

[himanshu231204]

Problem

Connect your client covers Claude Code, Claude Desktop, Cursor, Zed, and Windsurf. Every client missing from that page is someone who has to work out the config themselves — and the most common reason a working tool goes unused is a setup step that didn't quite fit.

What to add

Any MCP client you actually use. Some that come to mind:

• OpenClaw
• Continue
• Cline
• Goose
• LibreChat
• JetBrains AI Assistant
• Visual Studio Code (MCP support)

Acceptance criteria

• A section in docs/getting-started/clients.md matching the existing format
• The exact config file path, per OS where it differs
• A working config block — uvx localmem-mcp, with the pip alternative noted if the client needs an absolute path
• How to verify it connected in that client's UI
• Actually tested by you. An untested config is worse than none: it burns the reader's time and their trust

Why this is a good first issue

No knowledge of the codebase needed. If you already use an MCP client that isn't listed, you're most of the way there — you had to work the config out anyway.

One client per PR is ideal; it keeps review quick.

Notes

Client-specific gotchas are especially welcome. Several clients don't inherit your shell's PATH, so uvx resolves in a terminal but not in the app — the troubleshooting section mentions this generically, but a client-specific note is more useful.

Pointers

• docs/getting-started/clients.md — follow an existing section's shape
• mkdocs serve after pip install -e ".[docs]" previews locally