analyze_supply_chain — Cycle Intelligence MCP Tool
analyze_supply_chain
(analyze supply chain) is one of 13 tools on the
Cycle Intelligence
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call analyze_supply_chain from your client
- Claude Code Cycle Intelligence analyze_supply_chain run in your project directory
- Claude Desktop Cycle Intelligence analyze_supply_chain ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Cycle Intelligence analyze_supply_chain ~/.cursor/mcp.json
- VS Code Cycle Intelligence analyze_supply_chain .vscode/mcp.json
- Zed Cycle Intelligence analyze_supply_chain ~/.config/zed/settings.json
- Windsurf Cycle Intelligence analyze_supply_chain ~/.codeium/windsurf/mcp_config.json
- Cline Cycle Intelligence analyze_supply_chain ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Cycle Intelligence analyze_supply_chain ~/.gemini/settings.json
- Grok Cycle Intelligence analyze_supply_chain .mcp.json (in your project root)
- ChatGPT Cycle Intelligence analyze_supply_chain Settings → Connectors → Advanced → Developer mode
- Claude.ai Cycle Intelligence analyze_supply_chain Settings → Connectors → Add custom connector
- LangChain Cycle Intelligence analyze_supply_chain pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http cycle-intelligence https://edge.cycle-platform.com/v1/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.