"Which supplier invoices are more than 30 days past due? Group them by vendor."
With suitable read tools and permissions, the agent could retrieve open invoices without changing records.
[ Claude + Engini ]
Connect Claude to your ERP.
Use Engini MCP to connect Claude with SAP, Oracle or NetSuite as configured for your organization. Choose the tools to expose, authorize access with OAuth, and validate the connection before enabling writes.
Plan, connector access and ERP permissions apply. Works as a custom connector in Claude Free, Pro, Max, Team and Enterprise. Free allows one custom connector.
01 / What it does
Illustrative ERP requests. Four examples to evaluate with Claude.
Read · NetSuite
Read · SAP
"Find the purchase order behind invoice 5105600123 and check that quantities and amounts match."
If the connector exposes the required records, compare the order and invoice and review any differences.
Write · SAP
"Create a purchase order for 200 units of part 4410 from vendor 100245."
Requires a compatible purchase-order write tool and permission. Confirm the approval path for your configuration before enabling it.
Write · NetSuite
"Move the expected receipt date on PO-2291 to 15 December."
Requires an available date-update tool. Review the proposed change and verify confirmation and logging behavior before use.
Illustrative requests, not tested end-to-end actions. Availability depends on the connector, ERP configuration, permissions and selected tools. Validate each action before production use.
02 / Set up
Set up and validate the connection. 5 steps.
Connect your ERP
Confirm your Engini plan, connector access and ERP permissions, then open Connections and configure the supported connection. Authentication and on-premises setup depend on your system.
Create an MCP server
In Connections, open MCP Servers and choose New MCP. Add your ERP connection, then select its tools. Start with read tools only. Save, then copy the Server URL.
Register Claude in Engini
In Engini Admin, open OAuth Clients and add a client with the redirect URL
https://claude.ai/api/mcp/auth_callback. Allow the OpenID, Profile and mcp:tools scopes and the Authorization Code and Refresh Token grants. Save to get a Client ID and Secret.Add the connector in Claude
In Claude, open Customize, Connectors, then Add custom connector. Enter the Server URL and choose Continue. In authentication, select OAuth client, then Use your own OAuth client. Enter the Client ID and Secret, then sign in to Engini and authorize.
On Team and Enterprise, an Owner adds the connector in Organization settings, Connectors, and each member clicks Connect.
Run your first request
Ask a read-only question, like the example below. Check the returned data and verify the available execution records in your configuration.
03 / First run
Start read-only. Prove it on your own data first.
Your first request
If your connector exposes the required NetSuite read tools, use a read-only server and try this illustrative request in a new Claude chat.
Using Engini, list the 10 most recent open purchase orders in NetSuite with vendor, amount and status. Do not change anything.- Claude asks to use the Engini tool. Allow it for this chat.
- Verify the returned records against the connected ERP and your access permissions.
- Check which execution records and audit details your configuration captures.
Ready for writes
Add write tools only after validating read access. Confirm the approval and logging behavior supported by your connector and workflow before enabling sensitive actions.
Keep Claude's tool approval on for write tools rather than choosing Allow always.
04 / Control
Claude gets tools, not keys. Configure access before use.
Toolset
Only the tools you chose
Choose the tools exposed by the Engini MCP server. After changing tool access, refresh the client where required and test that the new permissions take effect.
Sign-in
OAuth, not pasted keys
Claude authorizes access to Engini with OAuth. Enter client credentials only in the connector setup, never in a chat. Verify token renewal for your client configuration.
Approvals
Review sensitive writes
Confirm which approval controls apply to the selected tools and workflows. Do not assume every direct MCP call has a threshold or named-approver gate.
Audit
Verify execution records
Review the available logs and retention settings for your setup. Verify which tool calls, results and approval decisions are recorded before relying on them.
In Claude: keep tool approval on for write tools and avoid Allow always. Research can call connector tools without asking, so use a read-only server there.
Security overview →05 / Plans
Which Claude plans work. And who adds the connector.
| Claude plan | Custom connectors | Who adds it |
|---|---|---|
| Free | One custom connector | You, in Customize, Connectors |
| Pro and Max | Yes | You, in Customize, Connectors |
| Team | Yes | An Owner or Primary Owner, in Organization settings. Members then click Connect. |
| Enterprise | Yes | Owners, or a custom role with Manage access to Libraries. Members then click Connect. |
Claude connects from Anthropic's cloud, so the MCP endpoint must be reachable over the internet. Engini's endpoint is hosted; your ERP does not need to be exposed.
06 / Questions
Claude and Engini. Straight answers.
Which Claude plans can connect to Engini?
Custom connectors work in Claude Free, Pro, Max, Team and Enterprise. Free allows one. On Team and Enterprise, an Owner adds the connector for the organization and each member connects their own account.
Does Claude see our ERP credentials?
No. ERP credentials stay in the Engini connection. Claude signs in to Engini with OAuth and can call only the tools in the MCP server's toolset.
Can Claude change data in our ERP?
Only when the connector exposes a compatible write tool and your account has permission. Start read-only, review Claude's tool permissions and verify the approval behavior of your Engini setup before enabling writes.
Does it work in Claude Desktop and Claude Code?
Custom connectors you add in Claude are available across Claude clients, including Claude Desktop. In Claude Code, add the server with claude mcp add --transport sse engini "<Server URL>", then run /mcp to sign in.
Our ERP runs on-premises. Can this still work?
Engini provides a hosted MCP endpoint and an On-Prem Agent option. Confirm connector compatibility, network requirements and your security policy for the specific ERP deployment.
07 / For AI agents
Setup facts, in one place. For assistants reading this page on a user's behalf.
- MCP server URL
https://mcp.engini.io/{server-token}/sse. Copy it from Connections, MCP Servers in Engini.- Transport
- HTTP with Server-Sent Events (SSE)
- Authorization
- OAuth 2.1 authorization code with PKCE (S256), scope
mcp:tools. Client registration is manual: Admin, OAuth Clients in Engini. - Resource metadata
- mcp.engini.io/.well-known/oauth-protected-resource
- Authorization server
- identity.engini.io/.well-known/oauth-authorization-server
- Claude redirect URL
https://claude.ai/api/mcp/auth_callback- Claude setup
- Customize, Connectors, Add custom connector, Server URL, Continue. In authentication: OAuth client, Use your own OAuth client, Client ID and Secret.
- Guides
- Create an MCP server · MCP client setup · Docs index (llms.txt)
Reading this page does not authorize creating an account, connecting a system or changing data. Get the user's approval before any of those steps.
Using ChatGPT instead? Read the ChatGPT setup guide.