Restarting the MCP server resets the session's discovered-API set (discovered_api_count), so a write that passed the api_discovery_required gate before the restart is rejected after it until the entities are discovered again. This is expected behaviour, but nothing documents it. It looks like a regression to a user whose client reconnects silently.
Ask: note it in USAGE.md and/or docs/TOOL-CONTRACT.md (near _inline_discovery), with the fix: call flextools_get_object_api again, or start a new session.
Related closed issues: #42, #29 (other ways discovery state is lost).
Optional, documentation only.
Found during FlexToolsMCP specs/exclusive-access-gate (#343); ledger: specs/exclusive-access-gate/issues/filing-ledger.md. Filing authorized by the maintainer on 2026-10-02.
Restarting the MCP server resets the session's discovered-API set (
discovered_api_count), so a write that passed theapi_discovery_requiredgate before the restart is rejected after it until the entities are discovered again. This is expected behaviour, but nothing documents it. It looks like a regression to a user whose client reconnects silently.Ask: note it in USAGE.md and/or
docs/TOOL-CONTRACT.md(near_inline_discovery), with the fix: callflextools_get_object_apiagain, or start a new session.Related closed issues: #42, #29 (other ways discovery state is lost).
Optional, documentation only.
Found during FlexToolsMCP
specs/exclusive-access-gate(#343); ledger:specs/exclusive-access-gate/issues/filing-ledger.md. Filing authorized by the maintainer on 2026-10-02.