@raytio/mcp-server 5.0.0 → 7.0.0

package/README.md

@@ -498,3 +498,51 @@ MIT
 ## Support
 
 For issues or questions, please open an issue in the repository.
+
+### Shared imports
+
+Use the FND domain tools for COA values/combinations, SFA leads and daily rates.
+`fnd_import_definitions` reads the server registry and availability.
+`fnd_import_run_create` takes an existing authorised `source_id`,
+`destination_org_id`, definition/version, strict domain context and an explicit
+`processing_policy.partial_policy` (`NONE` or `INDEPENDENT_OBJECTS`). COA context
+requires `structure_id` and `upsert_mode` (`CREATE_ONLY` or `REPLACE`), without a
+ledger. Lead context requires `org_id`. Daily-rate context requires `rate_type`,
+`date_from`, `date_to`, `currencies` and `upsert_mode`. The server checks all
+source, tenant, domain and destination permissions using the caller identity.
+
+For files, reserve evidence with `fnd_import_upload_reserve`, obtain its private
+URL with `fnd_import_upload_url`, upload the exact bytes, then call
+`fnd_import_upload_complete`. Set a saved ETL template or allowlisted field
+transforms using `fnd_import_profile_set`, extract bounded chunks using the
+server checkpoint, set reviewed reference mappings with
+`fnd_import_mapping_set`, and seal the complete batch with `fnd_import_seal`.
+For an external rate source, create a `FND_DAILY_RATES` run with its existing
+API source ID and call `fnd_import_acquire`. Source registration/provider
+configuration remains server-side: the inspected shared API has no source
+registration endpoint. No tool accepts provider URLs, credentials, arbitrary
+tables or executable functions.
+
+Call `fnd_import_validate`, inspect the run/findings/results, then
+`fnd_import_process` for the reviewed snapshot. Mutations require a stable
+`idempotency_key`; retry identical requests with that key, including after
+timeouts. Changed requests need a new key. Lifecycle commands require the
+current run `expected_version`; seal/reference mapping commands require their
+server version. Use `fnd_import_run_get` to restore a run and its batches, and
+`fnd_import_objects_list`, `fnd_import_findings_list` and
+`fnd_import_results_list` for bounded pages (`limit` 1–100, `offset` up to
+100000). `fnd_import_pause`, `fnd_import_resume` and `fnd_import_cancel` retain
+committed outcomes and use the same durable run ID.
+
+A successful MCP response means the API command returned. Preserve its
+`accepted`, run/operation/job identifiers and authoritative state; an accepted
+async request does not mean a completed import. Lead import outcomes can be
+`DEDUP_PENDING`, which is a handoff rather than completed deduplication or
+promotion. Server findings expose safe messages rather than raw source evidence.
+
+**6.0 migration:** `sfa_lead_import` now creates a shared `SFA_LEADS` run using
+the same inputs as run creation except for the fixed definition code. Replace
+legacy `tenant_id`, S3 coordinates, inline mappings and `trigger_dedup` with
+the shared source/evidence/profile journey above. Enable the `fnd` domain to
+continue a run created through the SFA tool. `fnd-readonly` remains limited
+to its existing reference reads and does not advertise import commands.