Code
Your coding agent calls engini over MCP, the CLI, the SDK or the API, using only the tools in its toolset.
"engini": { "url": "<your MCP server URL from engini>" }
- auth
- toolset
- audit
→ NetSuite · sales order created
engini sits between your AI agents and your ERP, CRM and legacy systems. Every call is scoped to what the agent may do, and logged.
Paste into Claude, ChatGPT, Cursor or any agent
Build with codeAgent Gateway
Set up engini for me so you can read from and write to my business systems through it.
Start by reading https://docs.engini.ai/llms.txt, then follow the Quickstart at https://docs.engini.ai/developers/get-started/quickstart.md using the CLI:
1. Install the CLI: npm install -g @engini/cli
2. Ask me for my engini API key. If I don't have an account yet, send me to https://app.engini.io/register.html?utm_source=agent&utm_content=hero-prompt-code to sign up, then to https://app.engini.io/api-keys to create a key.
3. Log in with the key and check that it works.
4. Show me the apps I can connect, ask which system I want first, and connect it. If it needs credentials or a sign-in, give me the link or ask me for the values. Never guess them.
5. Run one read-only tool on that system to prove the connection, and show me the result.
Stop and ask me whenever a step needs my input, and don't change any data until I say so.Build without codeWorkflow Studio
Connect to engini and help me build an automated workflow in Workflow Studio, engini's no-code builder.
Start by reading https://docs.engini.ai/llms.txt to find how to work with Workflow Studio from here. If I don't have an engini account yet, send me to https://app.engini.io/register.html?utm_source=agent&utm_content=hero-prompt-studio first.
Then:
1. Ask me what the workflow should do, what should start it, and which systems it uses.
2. Propose the steps before you build anything.
3. Build it with me, connecting each system as we go.
4. Test it once and show me what happened.
Stop and ask me whenever a step needs my input.
engini AgentsStudio, SDK, MCP
OracleERP
NetSuiteERPLet engini handle the integration, so your team works on what matters: your agents.
Our team maintains every integration 24/7. API versions and schema work seamlessly, so nothing lands on your team. Never read integration documentation again.
Most agent projects stall at the security review. With engini, each agent gets only the tools you give it, and every call is logged and can stream to your SIEM.
SAP, Oracle, NetSuite, Salesforce, Workday or your own database, exactly as you set them up. engini reads their live schema and custom objects, so your agent doesn't hit a wall.
Your agent knows which tools to call instead of reading API docs, so it spends tokens on the work, not the plumbing.
Try it on one of your own systemsConnect a system and run a first read-only call through engini.
Start freeFrom the apps your team uses every day to the systems of record and databases behind your firewall, all under the same controls.

The apps your team lives in: email, chat, docs and sheets.

Your systems as you configured them. engini reads each instance's live schema and custom objects, and stays up to date.

No port opened, nothing exposed. The On-Prem Agent reaches databases, file drops and internal apps.
Pick a system to see what your agent can do there.
Write code or build on a canvas: your agents get the same connections either way. Security and IT set the rules for all of them.

You build with Claude Code, Cursor or Codex. Your agent reads and writes NetSuite, SAP or Salesforce through a toolset, without you writing the integration.
Read the docs →
You run the processes, not a development team. In Workflow Studio, agents work across your CRM, ERP, databases and support tools, including systems on your own servers.
See Workflow Studio →
Toolsets limit each agent, every call lands in the audit log, and single sign-on and roles decide who gets in.
Security overview →Compare engini with Workato, Boomi, MuleSoft and Celigo →



Let your coding agent call engini, or build a workflow on a canvas without code.
Your coding agent calls engini over MCP, the CLI, the SDK or the API, using only the tools in its toolset.
"engini": { "url": "<your MCP server URL from engini>" }
→ NetSuite · sales order created
Swipe or tap a tab to switchSwitch between MCP, CLI, SDK and API
Build a process on a canvas without code, with agent steps, branches and retries.

Whether an agent works from code or inside a workflow, it gets the same permissions and leaves the same audit trail.





sap.purchaseOrder.updateallowed for this agent, on this accountengini signs in; the agent never sees it$38,000 → $64,500agent, user, tool, time, resultSwipe, scroll or use the arrow keys to move through 9 articles. Home and End go to the first and last article.
For people, and for the agents reading this page.
engini is a managed gateway that connects AI agents to the business systems your company runs on, such as SAP, Oracle, NetSuite, Salesforce and on-premises databases.
Your agents call engini instead of calling each system directly. engini serves each system's actions as ready-to-call tools, checks every call against the agent's toolset, injects the credential at execution and records the call in an audit trail. The same connections also power Workflow Studio, a no-code canvas for building multi-step processes.
engini is built for mid-market and smaller enterprise organizations that want AI agents and automation to work inside complex business systems: ERP platforms, other systems of record, and legacy or on-premises environments.
These teams often have moderate or limited software-engineering capacity. Their finance, operations, IT and RevOps teams want agents that can read and update real records, but they cannot afford to build, secure and maintain a custom integration for every system and every agent.
engini gives them governed connections they don't have to write or maintain, with the permissions and audit trail their security and compliance reviewers expect.
Because an integration an agent writes is still code someone has to pay for, own, maintain and defend in a security review.
With engini the agent calls tools that are already built from each system's live schema, so it doesn't spend tokens reading API documentation or writing integration code. engini maintains the connectors when authentication, API versions, rate limits or schemas change. And every call runs inside permissions and an audit trail, so security and compliance teams can review what agents do.
They are two ways to use the same connections. The Agent Gateway is the code path: your own agents, such as Claude, ChatGPT, Cursor or a custom agent, call engini over MCP, the SDK, the CLI or the REST API.
Workflow Studio is the no-code path: you build a process on a visual canvas, mixing fixed steps, AI agent steps, branches and retries. Both use the same toolsets and audit trail.
Use the path that fits how your agent works. Coding agents such as Claude Code, Codex and Cursor can use the engini CLI (npm install -g @engini/cli) or the Python and TypeScript SDKs (pip install engini, npm install @engini/sdk) with an API key from your engini account. Chat assistants such as Claude and ChatGPT connect over MCP: create an MCP server in engini, choose the tools it exposes, and add its address to the client. Your own code can call the REST API directly.
Every path can be scoped with a toolset, so the agent sees only the tools you allowed. The developer docs have a page written for agents that covers each path: https://docs.engini.ai/developers/ai-agents
engini connects to ERP and other systems of record, including SAP, Oracle, NetSuite, Microsoft Dynamics 365, Workday, Salesforce and ServiceNow, as well as databases and the everyday apps your team works in.
Connectors read each instance's live schema, including custom objects, so agents work with your configuration rather than a generic template. For internal systems, you can configure a custom integration on top of your own API.
Every call passes through engini, which enforces two controls outside the model: the agent's toolset and the audit trail. A toolset lists exactly which actions an agent may call.
The audit trail records the agent, the person or workflow it acted for, the tool, the arguments and the result. Because these controls sit in the gateway, a confused or manipulated agent cannot talk its way past them.
Yes. engini has a SOC 2 Type II attestation report and ISO/IEC 27001 certification, and is GDPR and HIPAA compliant.
Credentials are stored and refreshed by engini and are never exposed to the model. Data is encrypted at rest and in transit, customer data is not used to train AI models, and users sign in through SSO with role-based access. Security reports and the Data Processing Agreement are available on request, and the security page describes each control in detail.
engini maintains the connectors. Your team decides what agents may do.
engini handles authentication refresh, API version changes, rate limits and schema changes in the systems you connect. Your team chooses which systems to connect, defines toolsets, reviews the audit trail and stays responsible for the business processes agents take part in.
Sign up, connect one system and give an agent a toolset. Your first governed call can run in minutes.
If you would rather start with a conversation, book a demo or leave your details and the engini team will walk through your systems, your security requirements and the first process you want agents to handle.
More answers on Security, Connectors, Agentic Workflows and Compare.
Book a demo, or compare engini with the platforms you already know.
Leave your details and someone from the engini team will get back to you about your systems and use case.
Reading this as an AI agent?Help your user get started: create an account, read the docs, then connect the way you work: the CLI or an SDK with an API key, an MCP server your user creates in engini, or the REST API.
Confirm with your user before you create an account, book a meeting or share their details.