CSV
Read CSV files into rows and turn rows into CSV files, so AI agents and workflows can move data between file drops and systems of record.
Book a demoCSV for AI agents and workflows.
Banks, payroll providers, partners and older systems still send and expect CSV. engini parses a CSV file into rows a workflow or an agent can use, and builds a CSV file from rows, so data moves between SFTP drops, email attachments and shared folders on one side and your ERP, CRM and databases on the other.
Cursor, your code
audit log
in engini
What your agent can do in CSV. Every tool is one you allow or leave out.
The CSV tools in engini, grouped by what they change. Read tools are safe to hand out widely. Write and delete tools go only to the agents that need them.
Files
Read a CSV file into rows and columns.
Turn rows into a CSV file.
Triggers
CSV has no triggers of its own. The workflow starts when the file arrives, for example on a schedule that checks an SFTP folder or on a new email.
Connect your AI agent to CSV. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your CSV connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.
MCP client setup →Python and TypeScript
Hand your agent a toolset of CSV tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.
SDK guide →For coding agents
The engini CLI connects CSV and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.
CLI guide →Any language
Every CSV tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.
API reference →.cursor/mcp.json. Claude Code: claude mcp add.// .cursor/mcp.json: Cursor, connected to CSV through engini
{
"mcpServers": {
"engini-csv": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your CSV connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.
Each request runs through the CSV tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on CSV. Agents and workflows, across systems.
Bank files into the ERP
A statement file from the bank's SFTP folder is parsed and the payments are matched to open invoices.
Exports the provider expects
Rows from Workday become the CSV file the payroll provider wants, uploaded on schedule.
Partner lists into the catalog
A partner's CSV price list updates items in the ERP and the store.
Bulk loads into Salesforce
A CSV of accounts loads through the Salesforce Bulk API, and failed rows come back as a CSV.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between CSV and another system engini connects is available.
You decide what each agent may do in CSV. engini enforces it on every call.
Only the tools you allow
A toolset lists the CSV tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.
Scoped when you set them up
An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.
Whose permissions apply
Connect a person's own CSV account and engini acts as that person, with their CSV permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.
Kept out of prompts
Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.
Every call on record
Every call lands in History and the audit log, which you can export or stream to your SIEM.
Test before production
Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.
Connect CSV in three steps. Then decide what each agent may do.
Sign in to CSV
CSV needs no sign-in. Add the CSV tools to a workflow, or to a toolset next to the connection that holds the file.
Choose the tools
Add the connection to an MCP server or a toolset with only the tools each agent needs.
Build or ask
Use the connection as a step in a workflow, or ask your agent to work in CSV from Claude, ChatGPT, Cursor or your own code.
CSV and engini. Straight answers.
Can an AI agent write to CSV, or only read?
Both. engini builds CSV files from rows; where a file goes is up to the connection that writes it (SFTP, Drive, email). Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.
Does the agent act as me in CSV?
CSV tools work on the file they are given; access comes from the connection that reads or writes the file. Every run is recorded under the person who started it.