analyze_nccl_benchmark — XportL MCP Tool
analyze_nccl_benchmark
(analyze nccl benchmark) is one of 6 tools on the
XportL
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call analyze_nccl_benchmark from your client
- Claude Code XportL analyze_nccl_benchmark run in your project directory
- Claude Desktop XportL analyze_nccl_benchmark ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor XportL analyze_nccl_benchmark ~/.cursor/mcp.json
- VS Code XportL analyze_nccl_benchmark .vscode/mcp.json
- Zed XportL analyze_nccl_benchmark ~/.config/zed/settings.json
- Windsurf XportL analyze_nccl_benchmark ~/.codeium/windsurf/mcp_config.json
- Cline XportL analyze_nccl_benchmark ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI XportL analyze_nccl_benchmark ~/.gemini/settings.json
- Grok XportL analyze_nccl_benchmark .mcp.json (in your project root)
- ChatGPT XportL analyze_nccl_benchmark Settings → Connectors → Advanced → Developer mode
- Claude.ai XportL analyze_nccl_benchmark Settings → Connectors → Add custom connector
- LangChain XportL analyze_nccl_benchmark pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http xportl https://xportl.io/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 19 October 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.