resolve_supplier_link — POD Benchmark MCP Tool Read-only
resolve_supplier_link
(resolve supplier link) is one of 10 tools on the
POD Benchmark
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call resolve_supplier_link from your client
- Claude Code POD Benchmark resolve_supplier_link run in your project directory
- Claude Desktop POD Benchmark resolve_supplier_link ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor POD Benchmark resolve_supplier_link ~/.cursor/mcp.json
- VS Code POD Benchmark resolve_supplier_link .vscode/mcp.json
- Zed POD Benchmark resolve_supplier_link ~/.config/zed/settings.json
- Windsurf POD Benchmark resolve_supplier_link ~/.codeium/windsurf/mcp_config.json
- Cline POD Benchmark resolve_supplier_link ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI POD Benchmark resolve_supplier_link ~/.gemini/settings.json
- Grok POD Benchmark resolve_supplier_link .mcp.json (in your project root)
- ChatGPT POD Benchmark resolve_supplier_link Settings → Connectors → Advanced → Developer mode
- Claude.ai POD Benchmark resolve_supplier_link Settings → Connectors → Add custom connector
- LangChain POD Benchmark resolve_supplier_link pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http podbenchmark https://podbenchmark.com/api/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.