Translated document — Samedoc: Translate PDF & PDF to Word MCP Resource
Translated document
is one of 1 resource on the
Samedoc: Translate PDF & PDF to Word
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Translated document from your client
- Claude Code Samedoc: Translate PDF & PDF to Word Resource/Translated document run in your project directory
- Claude Desktop Samedoc: Translate PDF & PDF to Word Resource/Translated document ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Samedoc: Translate PDF & PDF to Word Resource/Translated document ~/.cursor/mcp.json
- VS Code Samedoc: Translate PDF & PDF to Word Resource/Translated document .vscode/mcp.json
- Zed Samedoc: Translate PDF & PDF to Word Resource/Translated document ~/.config/zed/settings.json
- Windsurf Samedoc: Translate PDF & PDF to Word Resource/Translated document ~/.codeium/windsurf/mcp_config.json
- Cline Samedoc: Translate PDF & PDF to Word Resource/Translated document ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Samedoc: Translate PDF & PDF to Word Resource/Translated document ~/.gemini/settings.json
- Grok Samedoc: Translate PDF & PDF to Word Resource/Translated document .mcp.json (in your project root)
- ChatGPT Samedoc: Translate PDF & PDF to Word Resource/Translated document Settings → Connectors → Advanced → Developer mode
- Claude.ai Samedoc: Translate PDF & PDF to Word Resource/Translated document Settings → Connectors → Add custom connector
- LangChain Samedoc: Translate PDF & PDF to Word Resource/Translated document pip install langchain-mcp-adapters
Read from the server itself, by connecting to it and calling resources/list on 14 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.