MCP Settings Specs
MCP-001: Sparse mutations preserve sibling servers
- Adding, updating, or deleting an MCP server shall issue exactly one dedicated MCP settings request containing only the affected server.
- An MCP mutation shall never use redacted or encrypted settings snapshots as its mutation base.
- Untouched sibling servers and credentials shall survive add, update, delete, concurrent different-key updates, and failed mutations.
MCP-002: Secret patches preserve user intent
- Omitting an unchanged secret shall preserve its stored value.
- Supplying a secret shall replace its stored value.
- Explicitly clearing a supported secret field shall send
null. - The display-only redaction sentinel shall never be sent as mutation data.
MCP-003: Settings map keys are stable MCP identities
- Rendering order and transport grouping shall not change persistence identity.
- Deletion shall address the settings map key without matching URL, command, or arguments.
- Rename shall use one atomic map patch, reject collisions, and reject hidden-secret renames that could lose credentials.