norse_translate_to — norse MCP Prompt

norse_translate_to is one of 2 prompts on the norse MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke norse_translate_to from your client

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

Other prompts on this server

• norse_translate_from

norse also offers 2 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.