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