Short answer
There are three ways: paste or upload exports (simple, always stale), give the assistant direct database access (powerful, risky), or connect through the software's MCP server (live, with the software's own permissions). For CRM and field service data, an MCP server is the safe route. Fieldproxy's runs every read as a restricted read-only database role, enforces row limits in Postgres, hides chosen columns and makes every change a proposal a person confirms.
The three options compared
| Upload exports | Direct database | MCP server | |
|---|---|---|---|
| Data is live | No | Yes | Yes |
| Respects user permissions | No | Only if you build it | Yes |
| Can act (schedule, send) | No | Raw writes | Through the software's own tools |
| Undo and audit | No | Rarely | Yes, on Fieldproxy |
Limits that matter for business data
A Fieldproxy key can be limited to certain tables, certain rows (for example only one region's jobs or one team's customers) and can never read hidden columns, even through its own SQL. Row and column limits can be described in plain words, and Fieldproxy shows how many rows the key would see before it is created. Administrators see every key and connected app and can revoke any of them on the next request.
Fieldproxy facts on this page come from the Fieldproxy MCP reference. Competitor details are from each vendor's own documentation as of September 27, 2026; see the comparison table and sources.