design_single_line — uniwire MCP Prompt
design_single_line
is one of 1 prompt on the
uniwire
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke design_single_line from your client
- Claude Code uniwire Prompt/design_single_line run in your project directory
- Claude Desktop uniwire Prompt/design_single_line ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor uniwire Prompt/design_single_line ~/.cursor/mcp.json
- VS Code uniwire Prompt/design_single_line .vscode/mcp.json
- Zed uniwire Prompt/design_single_line ~/.config/zed/settings.json
- Windsurf uniwire Prompt/design_single_line ~/.codeium/windsurf/mcp_config.json
- Cline uniwire Prompt/design_single_line ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI uniwire Prompt/design_single_line ~/.gemini/settings.json
- Grok uniwire Prompt/design_single_line .mcp.json (in your project root)
- ChatGPT uniwire Prompt/design_single_line Settings → Connectors → Advanced → Developer mode
- Claude.ai uniwire Prompt/design_single_line Settings → Connectors → Add custom connector
- LangChain uniwire Prompt/design_single_line pip install langchain-mcp-adapters
uniwire also offers 3 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 13 October 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.