< Back to all integrations

On Prem Files

Data & Infrastructure

Give AI agents and workflows the files and folders inside your network, through the engini On-Prem Agent, with no inbound ports opened.

Book a demo
[ Behind your firewall + engini ]

Files inside your network, for AI agents and workflows.

Legacy systems often talk in files: exports in a shared folder, scans in a drop folder, reports on a network share. engini reaches them through the On-Prem Agent, a small service inside your network that connects out to engini and never asks you to open a port. Agents and workflows can list, read, create, move, rename and delete files and folders there, with the same toolsets and audit log as every other system.

MCPPython and TypeScript SDKCLIREST APIWorkflow Studio
Read the On Prem Files guide →
ReachLocal folders and network shares on the server where the On-Prem Agent runs, or that it can reach
NetworkOutbound only, over HTTPS on port 443. No inbound ports or firewall rules
Same agentAlso reaches SQL Server, MySQL, PostgreSQL, Oracle, IBM DB2, ODBC sources and internal REST and HTTP applications
[ 01 / What agents can do ]

What your agent can do with files inside your network. Every tool is one you allow or leave out.

The On Prem Files 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

Get Files, Get Folders

List what a folder holds.

Read
Get File

Read a file's contents.

Read

Write

Create File, Create Folder

Write a new file or make a folder.

Write
Move File, Rename File

Move a file to another folder or rename it.

Write

Delete

Delete File, Delete Folder

Remove a file or a folder.

Delete

Triggers

There are no file 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 On Prem Files. Four ways in, one set of permissions.

MCP

Claude, ChatGPT, Cursor

Create an MCP server in engini with your On Prem Files 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 On Prem Files 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 On Prem Files 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 On Prem Files 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 On Prem Files 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 your file shares through engini
// .cursor/mcp.json: Cursor, connected to your file shares through engini
{
"mcpServers": {
"engini-files": {
"url": "<your engini MCP server address>"
}
}
}

Create the MCP server in engini with your On Prem Files 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 export files did the legacy system drop today?”
“Read the latest payroll file and total it by department.”
“Move the processed invoices to the archive folder.”
“Save this report to the finance share as a CSV.”
“Is there a scan for purchase order 4521 in the inbound folder?”
“Rename today's files with the date first.”

Each request runs through the On Prem Files 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 files inside the network. Legacy systems, connected through what they already do.

Legacy systems

Exports into modern systems

A legacy application writes an export to a shared folder every night. A workflow picks it up and loads the records into NetSuite, Salesforce or Snowflake.

On Prem FilesNetSuiteSnowflake
Finance

Bank files on a network share

Statement files that land on an internal share are read, matched to open invoices and recorded in the ERP.

On Prem FilesSAP S/4HANA
Operations

Scans into the right record

Scanned delivery notes in a drop folder are read and attached to the right order, then moved to a done folder.

On Prem FilesSAP Business One
Reporting

Reports back to the share

Results from cloud systems are written back as files where internal teams already look for them.

SalesforceOn Prem Files

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

[ 04 / Agent Policy ]

You decide what each agent may do in On Prem Files. engini enforces it on every call.

Toolsets

Only the tools you allow

A toolset lists the On Prem Files 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 account the On-Prem Agent runs under, with that account's permissions on your folders and shares. 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 →
[ Behind your firewall ]

How the On-Prem Agent works.

You install a small service on a server inside your network. It opens every connection itself: out to engini over HTTPS on port 443, and to your files, databases and internal applications while it runs a task. It asks engini for new tasks every few seconds and sends each result back on the same connection. Nothing connects in, and each call through it is recorded in History.

On-Prem Agent guide →
[ 05 / Set up ]

Connect On Prem Files in three steps. Then decide what each agent may do.

Step 01

Install the On-Prem Agent

Add an agent in engini, download and install it on a server inside your network, and test its connection.

Step 02

Connect the files

Add an On Prem Files connection that uses the agent, pointing at the folders or shares it should work with.

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 On Prem Files setup guide →
[ 06 / Questions ]

On Prem Files and engini. Straight answers.

Can an AI agent write to On Prem Files, or only read?

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

Do I need to open a port in the firewall?

No. The On-Prem Agent connects out to engini over HTTPS on port 443. Nothing connects in, so you open no inbound ports or firewall rules. The alternative, for systems you expose yourself, is to allow engini's fixed IP addresses.

What else can the On-Prem Agent reach?

On-premises databases (SQL Server, MySQL, PostgreSQL, Oracle, IBM DB2 and ODBC sources), internal REST and HTTP applications, and file drops in local folders and network shares.

Does the agent act as me in On Prem Files?

It acts as the account the On-Prem Agent runs under, with that account's permissions on your folders and shares. Every run is recorded under the person who started it.

Can a change in On Prem Files start work?

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