Install in any client
Every install below adds the same MCP server, generated by internal/installlinks:
{"command":"npx","args":["-y","deedglass","mcp","serve"]}deedglass mcp install-links prints all of them (--json for scripts). deedglass.com/install,
the README buttons, the registry server.json, the Claude Code plugin and the listing kits all come
from the same package, and a test decodes every link back to this object.
No link holds a key. Run npx deedglass init first. mcp serve uses, in order: --api-key,
DEEDGLASS_API_KEY, then .deedglass/quickstart.key in the working directory or its nearest
parent. The server is --server, DEEDGLASS_SERVER, DEEDGLASS_BASE_URL, then the local stack
init started, then http://127.0.0.1:8080. Without a key it answers every call with
No Deedglass key found. Run npx deedglass init in a terminal, then restart your MCP client.
| Client | How | Format source (checked 2026-10-02, re-checked 2026-10-11 where noted) |
|---|---|---|
| Cursor | cursor://anysphere.cursor-deeplink/mcp/install?name=deedglass&config=<base64 JSON>; web form https://cursor.com/en/install-mcp?…; URLs at most 10,000 characters |
cursor.com/docs/context/mcp/install-links |
| VS Code | vscode:mcp/install?<urlencoded JSON with name>; https://vscode.dev/redirect/mcp/install?name=…&config=…; code --add-mcp '<json>' |
code.visualstudio.com/api/extension-guides/ai/mcp |
| LM Studio | lmstudio://add_mcp?name=deedglass&config=<base64 JSON> |
lmstudio.ai/docs/app/mcp/deeplink |
| Goose | goose://extension?cmd=npx&arg=-y&arg=deedglass&arg=mcp&arg=serve&id=deedglass&name=Deedglass&description=… |
goose-docs.ai/docs/getting-started/using-extensions |
| Claude Code | claude mcp add deedglass -- npx -y deedglass mcp serve (--scope project writes .mcp.json) |
code.claude.com/docs/en/mcp |
| Claude Code plugin | /plugin marketplace add deedglass/deedglass, then /plugin install deedglass@deedglass (after 10-15) |
integrations/claude-code/, root .claude-plugin/marketplace.json |
| Claude Desktop | the .mcpb bundle on each release (not built yet; see the S47 report) |
github.com/modelcontextprotocol/mcpb |
| Windsurf | the mcpServers block in ~/.codeium/windsurf/mcp_config.json |
deedglass mcp snippet --client windsurf |
| Docker MCP Catalog | deploy/docker-catalog/server.yaml, submitted by PR (founder) |
github.com/docker/mcp-registry |
| MCP Registry | root server.json, io.github.deedglass/deedglass (founder publishes) |
modelcontextprotocol.io/registry/quickstart |
README buttons use https only (GitHub drops other schemes): Cursor’s web link with its badge image, the vscode.dev redirect, and deedglass.com/install anchors for the rest.
Listing kits the founder submits: integrations/cursor/ (Cursor marketplace),
integrations/supabase/ and integrations/neon/ (integration directories). node scripts/check-listings.mjs checks every kit.
What it doesn’t do
Section titled “What it doesn’t do”No telemetry. A link never carries a key or a URL with credentials. Installing the server doesn’t
put your other MCP servers behind Deedglass; that is deedglass mcp wrap.