wrap_mcp_server — runx MCP Prompt

wrap_mcp_server is one of 4 prompts on the runx MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke wrap_mcp_server from your client

• Claude Code runx Prompt/wrap_mcp_server run in your project directory
• Claude Desktop runx Prompt/wrap_mcp_server ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor runx Prompt/wrap_mcp_server ~/.cursor/mcp.json
• VS Code runx Prompt/wrap_mcp_server .vscode/mcp.json
• Zed runx Prompt/wrap_mcp_server ~/.config/zed/settings.json
• Windsurf runx Prompt/wrap_mcp_server ~/.codeium/windsurf/mcp_config.json
• Cline runx Prompt/wrap_mcp_server ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI runx Prompt/wrap_mcp_server ~/.gemini/settings.json
• Grok runx Prompt/wrap_mcp_server .mcp.json (in your project root)
• ChatGPT runx Prompt/wrap_mcp_server Settings → Connectors → Advanced → Developer mode
• Claude.ai runx Prompt/wrap_mcp_server Settings → Connectors → Add custom connector
• LangChain runx Prompt/wrap_mcp_server pip install langchain-mcp-adapters

Other prompts on this server

• install_skill
• author_skill
• publish_skill

Read from the server itself, by connecting to it and calling prompts/list on 24 September 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.