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