PLCGateway support MCP Server

Checks whether a PLC, CNC, controller family, model, brand or protocol is supported and returns its page: which driver, connection settings, address syntax with examples, what can be read, tips and FAQ. Examples: "S7-1200", "CompactLogix", "MELSEC iQ-R", "FANUC 0i-F", "Modbus RTU", "IEC 104", "BACnet". Without a match it lists the supported protocols.

Searches all pages of plcgateway.com (products, modules, protocols, controllers, guides) and returns the best matching pages with URL and summary. Follow up with product_info or device_support for the full text.

Calculates the list price of PLCGateway licences in EUR, excluding VAT: product, number of computers, optional modules (SCADA and Embedded only) and optional years of updates and support after the first year (included). Licences are perpetual, one per computer, with every driver and no device or tag limit. Embedded and Enterprise are priced on request: offer request_demo then.

Explains what a PLCGateway product, module or topic is for, who it is for, what it includes and how it works, from the official website. Topics: overview (compare Connect, SCADA and Embedded, what each includes, platforms), connect (machine connectivity and OPC UA server), scada (screens, alarms, history, reports, OEE), embedded (operator panel on the device's own display, ARM panels, panel PCs), quality_maintenance (module: SPC control charts, maintenance plans, CMMS), energy (module: ISO 50001 energy management), oee_production (production model, OEE, batches, downtime), ai_mcp (the MCP server built into every product and what AI assistants can do with it), integrations (OPC UA, MQTT, Modbus TCP server, REST API), protocols (all drivers and supported controllers), pricing (prices, licences, trial, maintenance), plc_gateway_guide (what a PLC gateway is), kepserverex_migration (moving tags from KEPServerEX), contact, references (customers and installations: in use at factories in many countries, names not published).

Sends a demo, trial or offer request to the PLCGateway team by e-mail; they answer the user directly. Ask the user for their name and e-mail address; company, phone, the product they are interested in and a short description of their machines and goals are optional but help. Never invent, guess or reuse contact details the user did not give for this request. Before calling, show the user exactly what will be sent and ask for permission; set user_confirmed to true only after they explicitly agreed. Their details are used only to answer the request (privacy notice: https://plcgateway.com/privacy).