order_wine — NEVINI Wines MCP Prompt
order_wine
is one of 1 prompt on the
NEVINI Wines
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke order_wine from your client
- Claude Code NEVINI Wines Prompt/order_wine run in your project directory
- Claude Desktop NEVINI Wines Prompt/order_wine ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor NEVINI Wines Prompt/order_wine ~/.cursor/mcp.json
- VS Code NEVINI Wines Prompt/order_wine .vscode/mcp.json
- Zed NEVINI Wines Prompt/order_wine ~/.config/zed/settings.json
- Windsurf NEVINI Wines Prompt/order_wine ~/.codeium/windsurf/mcp_config.json
- Cline NEVINI Wines Prompt/order_wine ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI NEVINI Wines Prompt/order_wine ~/.gemini/settings.json
- Grok NEVINI Wines Prompt/order_wine .mcp.json (in your project root)
- ChatGPT NEVINI Wines Prompt/order_wine Settings → Connectors → Advanced → Developer mode
- Claude.ai NEVINI Wines Prompt/order_wine Settings → Connectors → Add custom connector
- LangChain NEVINI Wines Prompt/order_wine pip install langchain-mcp-adapters
NEVINI Wines also offers 1 resource — 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 25 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.