Tracking tradeoff from agentic MCP migration plan.
Open question: How should the MCP server adapt when a user's Airtable base schema doesn't match the hardcoded fields in mapToAirtableRecord (backend/src/services/airtable-sync.ts:9)?
Options:
- Auto-detect via
airtable_get_schema tool and build field map at runtime
- Require user-supplied
fieldMap in ~/.jobsync/config.json
- Hybrid: auto-detect, allow override
Other concerns:
- Graceful degradation when a field is missing (skip vs error)
- Field type validation (single-select options, linked records)
Tracking tradeoff from agentic MCP migration plan.
Open question: How should the MCP server adapt when a user's Airtable base schema doesn't match the hardcoded fields in
mapToAirtableRecord(backend/src/services/airtable-sync.ts:9)?Options:
airtable_get_schematool and build field map at runtimefieldMapin~/.jobsync/config.jsonOther concerns: