latin_translate_from — latin MCP Prompt

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

by client

How to invoke latin_translate_from from your client

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

Other prompts on this server

• latin_translate_to

latin 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.