get_design_options — LivaGlow Shop MCP Tool Read-only
get_design_options
(get design options) is one of 11 tools on the
LivaGlow Shop
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_design_options from your client
- Claude Code LivaGlow Shop get_design_options run in your project directory
- Claude Desktop LivaGlow Shop get_design_options ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor LivaGlow Shop get_design_options ~/.cursor/mcp.json
- VS Code LivaGlow Shop get_design_options .vscode/mcp.json
- Zed LivaGlow Shop get_design_options ~/.config/zed/settings.json
- Windsurf LivaGlow Shop get_design_options ~/.codeium/windsurf/mcp_config.json
- Cline LivaGlow Shop get_design_options ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI LivaGlow Shop get_design_options ~/.gemini/settings.json
- Grok LivaGlow Shop get_design_options .mcp.json (in your project root)
- ChatGPT LivaGlow Shop get_design_options Settings → Connectors → Advanced → Developer mode
- Claude.ai LivaGlow Shop get_design_options Settings → Connectors → Add custom connector
- LangChain LivaGlow Shop get_design_options pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http livaglow-shop https://livaglow.de/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.