diff --git a/README.md b/README.md
index 0be5e5481..c79c7409b 100644
--- a/README.md
+++ b/README.md
@@ -20,6 +20,7 @@
+
@@ -512,6 +513,19 @@ python -m graphify.serve graphify-out/graph.json --transport http --host 0.0.0.0
The MCP server gives your assistant structured access: `query_graph`, `get_node`, `get_neighbors`, `shortest_path`, `list_prs`, `get_pr_impact`, `triage_prs`.
+### One-click install (VS Code · Smithery)
+
+Prefer not to edit MCP config by hand? Register the graphify MCP server in one step. Run `/graphify` first so a `graphify-out/graph.json` exists in the workspace; the server reads it on launch.
+
+[](https://insiders.vscode.dev/redirect/mcp/install?name=graphify&config=%7B%22command%22%3A%22uvx%22%2C%22args%22%3A%5B%22--from%22%2C%22graphifyy%5Bmcp%5D%22%2C%22graphify-mcp%22%5D%7D)
+
+The button adds a `graphify` server that launches with `uvx --from "graphifyy[mcp]" graphify-mcp` (no API key, no prior install). Or install via [Smithery](https://smithery.ai/servers/graphify/graphify) for Claude, Cursor, VS Code, and other clients:
+
+```bash
+# pick your client (claude, cursor, vscode, windsurf, ...)
+npx -y @smithery/cli install graphify/graphify --client claude
+```
+
### Shared HTTP server
`--transport stdio` (the default) spawns one local server per developer. `--transport http` serves the same tools over the MCP Streamable HTTP transport, so a single shared process can serve the graph for the whole team — clients point their IDE MCP config at `http://:8080/mcp` instead of running graphify locally.