PRACTICAL FIELD GUIDE
A create request lost its response: avoid duplicate rows
A lost response does not establish whether a create request reached the server. Retrying an uncertain mutation can create duplicates unless the application has a reliable reconciliation strategy.
MCPBackend editorial team · · Examples are illustrative
Put it into practice
- Keep a stable business reference for the intended operation where the schema supports it.
- Look up the resulting state through an authorized query before retrying.
- Use uniqueness and application reconciliation deliberately rather than assuming an undocumented idempotency header exists.
What this looks like
ILLUSTRATIVE EXAMPLE
A form times out after the server saves a lead. A blind resubmission creates a second lead unless the application can recognize the original operation.
A boundary to keep clear
A client-generated reference must be validated and scoped correctly. It is not a substitute for authorization.
MCPBackend context
Use get_project_api or the dashboard's generated OpenAPI contract for your project's exact data-plane routes. Machine keys and end-user tokens have different access models. Treat error status and JSON code together, keep credentials out of URLs, and test against disposable records before changing real data.
Take the next step
Inspect the current project contract, try the change with disposable data, and verify the result through the same credentials your app will use. Record the expected response and one denied-access case before release.
Sources and further reading
These references explain the underlying protocols and design principles. For supported MCPBackend operations and exact request shapes, inspect your project’s generated API contract.