< Back to all integrations

SFTP

Data & Infrastructure

Connect AI agents and workflows to SFTP servers: list, get, upload, append, move, rename and delete files and folders, with password or private key sign-in.

Book a demo
[ SFTP + engini ]

SFTP for AI agents and workflows.

engini lets your AI agents and workflows work with files on SFTP servers: list folders, get, upload, create and append to files, and move, rename and delete files and folders. Banks, insurers, payroll providers and older ERPs still exchange files this way, so SFTP is often where a process starts or ends. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.

MCPPython and TypeScript SDKCLIREST APIWorkflow Studio
Read the SFTP guide →
Sign-inA user name with a password, or a private key in PEM format with an optional passphrase
ServerAny SFTP server by host and port (22 by default)
Accessengini connects from fixed IP addresses you can allow on your server
[ 01 / What agents can do ]

What your agent can do on SFTP. Every tool is one you allow or leave out.

The SFTP tools in engini, grouped by what they change. Listing and reading are safe to hand out widely. Writes, moves and deletes go only to the agents and workflows that need them.

Read

List Folder Content

List the files and folders in a folder.

Read
Get File

Read a file's contents.

Read

Write

Upload File

Put a file on the server.

Write
Append to file

Add content to the end of a file.

Write
Create Folder

Make a folder.

Write
Move a File, Rename File, Rename Folder

Move or rename files and folders.

Write
Update File Permissions

Change a file's permissions.

Write

Delete

Delete File, Delete Folder

Remove a file or a folder.

Delete

Triggers

There are no SFTP triggers. Run a workflow on a schedule that lists a folder and picks up new files, then moves them to a done folder.

[ 02 / Connect your agent ]

Connect your AI agent to SFTP. Four ways in, one set of permissions.

MCP

Claude, ChatGPT, Cursor

Create an MCP server in engini with your SFTP 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 →
SDK

Python and TypeScript

Hand your agent a toolset of SFTP tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.

SDK guide →
CLI

For coding agents

The engini CLI connects SFTP and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.

CLI guide →
REST API

Any language

Every SFTP tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.

API reference →
MCP in four steps
In engini, connect SFTP and create an MCP server with that connection and the tools this agent may use.
Claude: Settings, Connectors, Add custom connector, then paste the server address.
Cursor: add the address to .cursor/mcp.json. Claude Code: claude mcp add.
Sign in through engini when the client asks. The agent sees only the tools you chose.
Cursor, connected to SFTP through engini
// .cursor/mcp.json: Cursor, connected to SFTP through engini
{
"mcpServers": {
"engini-sftp": {
"url": "<your engini MCP server address>"
}
}
}

Create the MCP server in engini with your SFTP 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.

Try asking your agent
“Which files arrived in the inbound folder today?”
“Read the latest bank statement file and list the payments in it.”
“Upload this CSV to the outbound folder for the payroll provider.”
“Move the processed files to the archive folder.”
“Is there a remittance file from Acme this week?”
“Append today's totals to the daily log file.”

Each request runs through the SFTP tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.

[ 03 / What teams build ]

What teams build on SFTP. File drops, into systems of record.

Finance

Bank files into the ERP

Pick up statement and remittance files from the bank's SFTP folder, match the payments to open invoices and record them in NetSuite or SAP.

SFTPNetSuiteSAP S/4HANA
Payroll

Payroll exports, sent on time

Build the payroll file from Workday and upload it to the provider's SFTP server on schedule.

WorkdaySFTP
Operations

Partner files into your database

Read CSV files that partners drop on SFTP and insert the rows into SQL Server or DB2 in batches, then archive the file.

SFTPCSVSQL Server
Analytics

Files, explained

An agent in Claude reads a file from SFTP and answers questions about it. Its toolset holds list and read tools only.

SFTPClaude

Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between SFTP and another system engini connects is available.

[ 04 / Agent Policy ]

You decide what each agent may do in SFTP. engini enforces it on every call.

Toolsets

Only the tools you allow

A toolset lists the SFTP 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.

MCP servers

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.

Identity

Whose permissions apply

engini acts as the SFTP user behind the connection, with that user's permissions on the server. Give each agent or workflow a user limited to the folders it needs. Every run is recorded under the person who started it.

Credentials

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.

Audit

Every call on record

Every call lands in History and the audit log, which you can export or stream to your SIEM.

Environments

Test before production

Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.

SOC 2 Type IIISO 27001GDPRSecurity at engini →
[ 05 / Set up ]

Connect SFTP in three steps. Then decide what each agent may do.

Step 01

Allow engini

Make sure the server accepts connections on its SFTP port, and allow engini's fixed IP addresses. Our support team sends them on request.

Step 02

Connect in engini

Add an SFTP connection with the host, port and user name, and sign in with a password or a private key.

Step 03

Choose the tools

Add the connection to an MCP server or a toolset with only the tools each agent needs, or use it as a step in a workflow.

Full SFTP setup guide →
[ 06 / Questions ]

SFTP and engini. Straight answers.

Can an AI agent write to SFTP, or only read?

Both. engini has tools to upload, create, append to, move, rename and delete files and folders. 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.

Can I sign in with a key instead of a password?

Yes. Choose Private Key and paste the key in PEM format, with its passphrase if it has one.

What about files in a folder on our own network?

For folders and network shares inside your network, use the On Prem Files connector with the engini On-Prem Agent, which connects out to engini on port 443 with no inbound ports.

Does the agent act as me in SFTP?

It acts as the SFTP user behind the connection, with that user's permissions on the server. Every run is recorded under the person who started it.

Can a change in SFTP start work?

There are no SFTP triggers. Run a workflow on a schedule that lists a folder and picks up new files. The workflow can include an AI agent step.