find_anchorage — Nausika MCP Prompt

find_anchorage is one of 5 prompts on the Nausika MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke find_anchorage from your client

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

Other prompts on this server

• plan_sailing_trip
• check_conditions
• onboard_boat
• weather_window

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.