languages — Remoto interpreting (ProZ.com) MCP Resource
languages
is one of 8 resources on the
Remoto interpreting (ProZ.com)
MCP server. Connect the server and your client can attach it as context.
by client
How to attach languages from your client
- Claude Code Remoto interpreting (ProZ.com) Resource/languages run in your project directory
- Claude Desktop Remoto interpreting (ProZ.com) Resource/languages ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Remoto interpreting (ProZ.com) Resource/languages ~/.cursor/mcp.json
- VS Code Remoto interpreting (ProZ.com) Resource/languages .vscode/mcp.json
- Zed Remoto interpreting (ProZ.com) Resource/languages ~/.config/zed/settings.json
- Windsurf Remoto interpreting (ProZ.com) Resource/languages ~/.codeium/windsurf/mcp_config.json
- Cline Remoto interpreting (ProZ.com) Resource/languages ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Remoto interpreting (ProZ.com) Resource/languages ~/.gemini/settings.json
- Grok Remoto interpreting (ProZ.com) Resource/languages .mcp.json (in your project root)
- ChatGPT Remoto interpreting (ProZ.com) Resource/languages Settings → Connectors → Advanced → Developer mode
- Claude.ai Remoto interpreting (ProZ.com) Resource/languages Settings → Connectors → Add custom connector
- LangChain Remoto interpreting (ProZ.com) Resource/languages pip install langchain-mcp-adapters
Other resources on this server
Remoto interpreting (ProZ.com) also offers 2 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 11 November 2026.
A listing does not declare its resources, 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 resource's type and contents.