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