Guide / Every rule
Setting defined in one environment and missing in another
The check connections/key-missing-in-env, in the group Connections.
Why it matters
A property or an MCP client that one environment configures and the other does not behaves differently there, often by silently using a default.
How to fix it
Add the setting to the target environment, or confirm that the default is what it needs.
Where you see it
The Problems tab lists it under Connections, the Connections screen shows it beside the map, and penstock check --only connections reports it as connections/key-missing-in-env. It also appears in the SARIF and GitHub outputs. Comparing two environments is part of Penstock Pro, and Team in a pipeline.
Rule details
| Id | connections/key-missing-in-env |
| Group | Connections |
| Level | Advice: it works, and reads or runs better without it |
Read more: Connections map. All rules: Every rule.