On Prem Files
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 demoFiles 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.
Cursor, your code
audit log
outbound only
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
List what a folder holds.
Read a file's contents.
Write
Write a new file or make a folder.
Move a file to another folder or rename it.
Delete
Remove a file or a folder.
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.
Connect your AI agent to On Prem Files. Four ways in, one set of permissions.
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 →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 →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 →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 →.cursor/mcp.json. Claude Code: claude mcp add.// .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.
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.
What teams build on files inside the network. Legacy systems, connected through what they already do.
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.
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.
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.
Reports back to the share
Results from cloud systems are written back as files where internal teams already look for them.
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.
You decide what each agent may do in On Prem Files. engini enforces it on every call.
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.
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
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.
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.
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 →Connect On Prem Files in three steps. Then decide what each agent may do.
Install the On-Prem Agent
Add an agent in engini, download and install it on a server inside your network, and test its connection.
Connect the files
Add an On Prem Files connection that uses the agent, pointing at the folders or shares it should work with.
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.
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.