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