MCP server for IP-Symcon — lets an LLM/agent inspect, develop and control an IP-Symcon home-automation system over its JSON-RPC API: read the object tree, read/edit/create PHP scripts, read variables, control devices. Write/dev tools gated behind a safety flag.
Schimmilab/ipsymcon-mcp-server
Skill Claude CodeCodex
Part of ipsymcon
Design and build a NEW IP-Symcon automation: thresholds, state transitions, adjustable settings, verification. Triggers: "Automation bauen", "Zeitschaltung", "Schwellwert", "Standby abschalten".
Schimmilab/ipsymcon-mcp-server
Skill Claude CodeCodex
Part of ipsymcon
Audit and clean up an IP-Symcon system — recurring errors, red logs, instances in error state, dead objects. Triggers: "Fehler-Audit", "rote Logs", "tote Instanzen entfernen", "IPS-Health-Check".
Schimmilab/ipsymcon-mcp-server
Skill Claude CodeCodex
Part of ipsymcon
Migrate an IP-Symcon object subtree between instances, or verify such a migration. Triggers: "IPS umziehen", "IP-Symcon auf neuen Rechner", "Subtree auf andere Instanz", "Config migrieren".
Schimmilab/ipsymcon-mcp-server
Skill Claude CodeCodex
Part of ipsymcon
Restructure WORKING IP-Symcon parts without changing behaviour — duplicates, renaming, grouping, extracting constants. Not ips-cleanup (that removes dead things). Triggers: "Struktur sortieren".
Schimmilab/ipsymcon-mcp-server
Skill Claude CodeCodex
Part of ipsymcon
Inspect and modify an IP-Symcon system via the ipsymcon MCP — object tree, variables, PHP scripts, events, automations. Use for any Symcon/Hausautomation request. Changes are always planned first.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: