docs(readme): Improve MCP configuration guide and streamline setup with uvx

[nzkdevsaider]

Updated README to reflect new AI tools and configuration details for MCP compatibility.

What does this PR do?

Updates the "How You Actually Use It" section in the README.md to provide explicit MCP configuration guides for a broader set of AI clients. Specifically, it adds detailed JSON snippets and instructions for:

• Cursor, Claude Desktop, Windsurf, and Google Antigravity (using the standard "mcpServers" key).
• GitHub Copilot CLI (interactive setup).

It also standardizes the examples to use uvx to execute the MCP server directly from the repository without requiring users to clone it manually.

How to test

1. Preview the README.md file locally or on GitHub to ensure the markdown renders correctly, particularly the nested JSON blocks and bullet points.
2. Verify the paths and JSON structures provided for each client (e.g., ensuring Copilot uses the servers object while the others use mcpServers).
3. (Optional) Copy/paste the configuration into one of the mentioned clients (like Cursor or VS Code) to confirm the MCP server initializes correctly.

Checklist

• Tests pass (python -m pytest tests/ -v)
• No hardcoded paths
• Linter passes (ruff check .)

[bensig]

Good addition for Cursor/Windsurf users. README has changed a lot though — can you rebase on main?

[nzkdevsaider]

Good addition for Cursor/Windsurf users. README has changed a lot though — can you rebase on main?

thank you, done!

[armujahid]

LGTM. Optionally, you can also add an alternative installation command via uv.

Using pip

pip install mempalace

Using uv

uv tool install mempalace

[web3guru888]

📝 Review of #109 — docs(readme): Improve MCP configuration guide and streamline setup with uvx

Scope: +85/−7 · 1 file(s) · docs-only

• README.md (modified: +85/−7)

🟢 Approved — clean, well-structured PR. Good work @nzkdevsaider!

---

_{🏛️ Reviewed by MemPalace-AGI · Autonomous research system with perfect memory · Showcase: Truth Palace of Atlantis}

[igorls]

Thanks for putting this together — per-client MCP config is a real gap for Cursor / Windsurf / Claude Desktop / Copilot users, and the JSON snippets here are most of what's needed.

Two things have changed since you opened this that make merging against README.md the wrong path:

1. The README was rewritten to delegate MCP setup entirely to the docs site. Lines 67-68 now point at mempalaceofficial.com/guide/getting-started and lines 133-138 defer tool listings to the docs. The ### With Claude, ChatGPT, Cursor, Gemini (MCP-compatible tools) section this PR edits is gone from develop. Per-client config blocks in README.md would re-introduce content I explicitly moved out.

2. The MCP invocation changed in fix: add mempalace-mcp entry point for pipx/uv compatibility #340. The canonical command is no longer python -m mempalace.mcp_server — it's the mempalace-mcp entry point registered in pyproject.toml. Every uvx --from mempalace python -m mempalace.mcp_server in this PR would need to become uvx mempalace-mcp (or mempalace-mcp for users who've already pipx installed).

Closing this one, but I'd love to merge the same content in the right place. The natural home is website/guide/mcp-integration.md — it currently has two Claude Code lines and nothing for Cursor, Windsurf, Copilot, or Claude Desktop. If you'd open a fresh PR against that file with:

• The per-client blocks from this PR
• Commands updated to uvx mempalace-mcp / mempalace-mcp
• The truncated "Prerequisite: uvx" sentence finished (link to https://docs.astral.sh/uv/getting-started/installation/ and a one-line install hint)
• The "19 tools" wording dropped (the count moves over time; point at the docs tool list instead)

…I'll merge it promptly. Thanks again for the contribution.