# Infor SyteLine MCP connector

The Infor SyteLine connector brings customer orders, order lines, shipments, customers and departments to Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person works on live records inside their own Infor SyteLine access.

Source: https://elaichi.ai/connectors/inforsyteline/

## Facts

| | |
| --- | --- |
| Application | Infor SyteLine |
| Category | Accounting |
| AI tools | 130 |
| Authentication | App credentials |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Infor SyteLine is connected

- Show open customer orders for Acme Tooling and their shipments
- Add a line for 200 brackets to customer order CO-10482
- List departments and flag any customer missing a currency code

## Connect Infor SyteLine in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Infor SyteLine.
2. Optionally set Share with, then press Connect.
3. Paste your Infor SyteLine app credentials. Infor SyteLine authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Infor SyteLine tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Infor SyteLine MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Infor SyteLine MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Infor SyteLine MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Infor SyteLine MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Infor SyteLine MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Infor SyteLine to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Infor SyteLine tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Infor SyteLine through Elaichi

### Catch a customer order up after a call

Sales. Ask for the open customer orders on an account before the call, then add a line or change a quantity afterwards without opening Infor SyteLine.

### Answer where an order is right now

Customer service. Pull the shipments against a customer order and tell the customer what went out and when, in one reply.

### Enter an order from an emailed purchase order

Order desk. Create the customer order and its lines straight from the details in the email, against the right customer record in Infor SyteLine.

### Check currency codes before invoicing abroad

Finance. List the currency codes set up in Infor SyteLine and confirm the one on a customer's record before quoting or invoicing in it.

### Keep departments current as the company changes

Finance. Add a new department or rename one, and list the existing ones when someone asks where a cost should sit.

### Clean up customer records in bulk

Sales operations. Find customers with missing or outdated details and update them one at a time from a short list, without clicking through every form.

## Elaichi vs Zapier MCP vs Composio for Infor SyteLine

All three can connect Infor SyteLine to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Infor SyteLine tools | Allow or restrict single Infor SyteLine tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Infor SyteLine call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Infor SyteLine to Claude?

Connect Infor SyteLine in Elaichi first, which asks for your Infor SyteLine app credentials and nothing else; there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Sign in to Elaichi when Claude asks and Infor SyteLine is ready to use.

### Does Infor SyteLine work with ChatGPT and Cursor as well as Claude?

Yes. Once Infor SyteLine is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Infor SyteLine once and every client picks it up.

### What can an AI agent actually do with my Infor SyteLine data?

It can list and look up customer orders, add or change order lines, check the shipments against an order, and create or update customers and departments in Infor SyteLine. It can also read currency codes and configurations and run the custom operations your company has set up. Short, concrete asks such as "open orders for Acme this month" work better than long paragraphs.

### Does connecting Infor SyteLine give the AI access to everything in my ERP?

No. Every request runs under the Infor SyteLine access of the person who signed in, so the agent sees the customers, orders and departments that person can already see. Elaichi can narrow that access further with roles and restrictions, and it never widens it.

### Can my team share one Infor SyteLine connection?

Yes. One person connects Infor SyteLine in Elaichi and shares the connection with a team, and nobody else ever handles an app credential. Each teammate still signs in to Elaichi as themselves, so the audit log names the person behind every customer order or customer change.

### Can I stop an agent from deleting or changing things in Infor SyteLine?

Yes. Restrictions in Elaichi work per action, so you can restrict deleting customer orders or updating customers for a role or for one person while leaving reads open. A restricted action still appears in Elaichi's tool search flagged as restricted, but no client can run it against Infor SyteLine, whatever the prompt says.

### What happens to an Infor SyteLine connection when someone leaves?

Offboarding a person in Elaichi ends their Infor SyteLine access through every client at once. A connection they shared keeps working for everyone else on the team. If you later want Infor SyteLine gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent together.

### Does the Infor SyteLine MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Infor SyteLine is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Infor SyteLine?

Yes. Both let Claude, ChatGPT or Cursor use Infor SyteLine. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Infor SyteLine call.

### How is Elaichi different from Composio for Infor SyteLine?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Infor SyteLine: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 130 Infor SyteLine tools

Every tool below is callable through https://api.elaichi.ai/mcp once Infor SyteLine is connected, subject to the toolbox it is in and the restrictions on the caller.

- **Create a Infor SyteLine aes event** (Create). Fire an Application Event System event (POST /aes/&lt;event_name&gt;) with named parameters; parameters with Return true come back with their values. Required: event_name.
- **List all Infor SyteLine API collections** (List). List the IDOs that have custom (REST API Wizard) APIs (GET /dynamic/api-docs-collection). Page with pageNumber / pageSize.
- **Get single Infor SyteLine API document by ID** (Get). Get the Swagger 2.0 document of an IDO's custom APIs (GET /dynamic/api-docs-collection/&lt;ido&gt;). Each path's operationId can be run with custom_api_results.list (GET) or custom_api_operations.execute (POST). id: the IDO name.
- **List all Infor SyteLine configurations** (List). List the Mongoose configuration names on the server (GET /configurations), e.g. CSI_DALS. Each name is a value for the account's configuration.
- **List all Infor SyteLine currency codes** (List). List currency codes (IDO SLCurrencyCodes) (GET /load/SLCurrencyCodes). Key properties: CurrCode. Filter with a SQL-style `filter` and pick columns with `properties`. The connector pages through all rows with Mongoose bookmarks (200 per page; `limit` sets the page size).
- **Infor SyteLine custom API operations execute** (Execute). Run a custom UpdateCollection or IDO-method API made with the REST API Wizard (POST /dynamic/api-docs-collection/&lt;ido&gt;/&lt;operation_id&gt;). Method parameters go in parameter1 ... parameter50. Required: ido, operation_id.
- **List all Infor SyteLine custom API results** (List). Run a custom LoadCollection API made with the REST API Wizard (GET /dynamic/api-docs-collection/&lt;ido&gt;/&lt;operation_id&gt;). Takes the same filter, properties and orderby options as a list. The connector pages through all rows with Mongoose bookmarks (200 per page; `limit` sets the page size). Required: ido, operation_id.
- **List all Infor SyteLine customer order lines** (List). List customer order lines (IDO SLCoitems) (GET /load/SLCoitems). Key properties: CoNum, CoLine and CoRelease. Filter with a SQL-style `filter` and pick columns with `properties`. The connector pages through all rows with Mongoose bookmarks (200 per page; `limit` sets the page size).
- **Create a Infor SyteLine customer order line** (Create). Create a customer order line (POST /update/SLCoitems, Action 1 = insert). Key properties: CoNum, CoLine and CoRelease.
- **Update a Infor SyteLine customer order line by ID** (Update). Update a customer order line (POST /update/SLCoitems, Action 2): send only the properties to change. With an _ItemId as id, Mongoose checks the row was not changed since it was read. Key properties: CoNum, CoLine and CoRelease. Required: id.
- **Delete a Infor SyteLine customer order line by ID** (Delete). Delete a customer order line (POST /update/SLCoitems, Action 4). Key properties: CoNum, CoLine and CoRelease. Required: id.
- **List all Infor SyteLine customer order shipments** (List). List customer order shipments (IDO SLCoShips) (GET /load/SLCoShips). Key properties: CoNum, CoLine and CoRelease plus the shipment sequence. Filter with a SQL-style `filter` and pick columns with `properties`. The connector pages through all rows with Mongoose bookmarks (200 per page; `limit` sets the page size).
- **List all Infor SyteLine customer orders** (List). List customer orders (IDO SLCos) (GET /load/SLCos). Key properties: CoNum. Filter with a SQL-style `filter` and pick columns with `properties`. The connector pages through all rows with Mongoose bookmarks (200 per page; `limit` sets the page size).
- **Create a Infor SyteLine customer order** (Create). Create a customer order (POST /update/SLCos, Action 1 = insert). Key properties: CoNum.
- **Update a Infor SyteLine customer order by ID** (Update). Update a customer order (POST /update/SLCos, Action 2): send only the properties to change. With an _ItemId as id, Mongoose checks the row was not changed since it was read. Key properties: CoNum. Required: id.
- **Delete a Infor SyteLine customer order by ID** (Delete). Delete a customer order (POST /update/SLCos, Action 4). Key properties: CoNum. Required: id.
- **List all Infor SyteLine customers** (List). List customers (IDO SLCustomers) (GET /load/SLCustomers). Key properties: CustNum and CustSeq (0 = the bill-to customer, 1+ = ship-tos). Filter with a SQL-style `filter` and pick columns with `properties`. The connector pages through all rows with Mongoose bookmarks (200 per page; `limit` sets the page size).
- **Create a Infor SyteLine customer** (Create). Create a customer (POST /update/SLCustomers, Action 1 = insert). Key properties: CustNum and CustSeq (0 = the bill-to customer, 1+ = ship-tos).
- **Update a Infor SyteLine customer by ID** (Update). Update a customer (POST /update/SLCustomers, Action 2): send only the properties to change. With an _ItemId as id, Mongoose checks the row was not changed since it was read. Key properties: CustNum and CustSeq (0 = the bill-to customer, 1+ = ship-tos). Required: id.
- **Delete a Infor SyteLine customer by ID** (Delete). Delete a customer (POST /update/SLCustomers, Action 4). Key properties: CustNum and CustSeq (0 = the bill-to customer, 1+ = ship-tos). Required: id.
- **List all Infor SyteLine departments** (List). List departments (IDO SLDepts) (GET /load/SLDepts). Key properties: Dept. Filter with a SQL-style `filter` and pick columns with `properties`. The connector pages through all rows with Mongoose bookmarks (200 per page; `limit` sets the page size).
- **Create a Infor SyteLine department** (Create). Create a department (POST /update/SLDepts, Action 1 = insert). Key properties: Dept.
- **Update a Infor SyteLine department by ID** (Update). Update a department (POST /update/SLDepts, Action 2): send only the properties to change. With an _ItemId as id, Mongoose checks the row was not changed since it was read. Key properties: Dept. Required: id.
- **Delete a Infor SyteLine department by ID** (Delete). Delete a department (POST /update/SLDepts, Action 4). Key properties: Dept. Required: id.
- **List all Infor SyteLine document object contents** (List). Download one document object's file (GET /docobj/&lt;ido&gt;): returns the raw bytes (application/octet-stream). Give name or refseq. Required: ido, rowPointer.
- **List all Infor SyteLine document objects** (List). List document objects (attachments), optionally for one IDO row (GET /docobj/list). DocumentObject holds the file as base64.
- **Create a Infor SyteLine document object** (Create). Upload a file as a document object (POST /docobj/&lt;ido&gt;): with rowPointer it is attached to that IDO row as a new document; with itemid it replaces an existing document object. The body is the raw file. Required: ido.
- **List all Infor SyteLine employees** (List). List employees (IDO SLEmployees) (GET /load/SLEmployees). Key properties: EmpNum. Filter with a SQL-style `filter` and pick columns with `properties`. The connector pages through all rows with Mongoose bookmarks (200 per page; `limit` sets the page size).
- **Create a Infor SyteLine employee** (Create). Create a employee (POST /update/SLEmployees, Action 1 = insert). Key properties: EmpNum.
- **Update a Infor SyteLine employee by ID** (Update). Update a employee (POST /update/SLEmployees, Action 2): send only the properties to change. With an _ItemId as id, Mongoose checks the row was not changed since it was read. Key properties: EmpNum. Required: id.
- **Delete a Infor SyteLine employee by ID** (Delete). Delete a employee (POST /update/SLEmployees, Action 4). Key properties: EmpNum. Required: id.
- **List all Infor SyteLine file contents** (List). Download the binary value of an IDO property, e.g. an image (GET /file/&lt;ido&gt;). Returns raw bytes. Required: ido, property, rowpointer.
- **Create a Infor SyteLine file content** (Create). Upload a file into a binary IDO property (POST /file/&lt;ido&gt;). The body is the raw file. Required: ido, property, itemid.
- **Create a Infor SyteLine ido change** (Create). Send a raw Mongoose UpdateCollection request (POST /update/&lt;ido&gt;): several inserts, updates and deletes in one transaction. Required: ido.
- **Get single Infor SyteLine ido definition by ID** (Get). Get an IDO's keys, properties (type, length, required, read-only, label) and subcollections (GET /info/&lt;ido&gt;). Use it to find the property names for filters and writes. id: the IDO name, e.g. SLCustomers.
- **Infor SyteLine ido methods execute** (Execute). Call an IDO method (POST /invoke/&lt;ido&gt;?method=&lt;method_name&gt;), e.g. a SyteLine stored-procedure method such as a posting or a get-defaults call. Parameters are positional; pass null for output parameters. Required: ido, method_name.
- **List all Infor SyteLine ido records** (List). List records of any IDO (GET /load/&lt;ido&gt;). Filter with a SQL-style `filter` and pick columns with `properties`. The connector pages through all rows with Mongoose bookmarks (200 per page; `limit` sets the page size). Required: ido.
- **Create a Infor SyteLine ido record** (Create). Create a record in any IDO (POST /update/&lt;ido&gt;, Action 1 = insert). Required: ido.
- **Update a Infor SyteLine ido record by ID** (Update). Update a record in any IDO (POST /update/&lt;ido&gt;, Action 2): send only the properties to change. With an _ItemId as id, Mongoose checks the row was not changed since it was read. Required: id, ido.
- **Delete a Infor SyteLine ido record by ID** (Delete). Delete a record in any IDO (POST /update/&lt;ido&gt;, Action 4). Required: id, ido.
- **List all Infor SyteLine item customers** (List). List customer item cross-references (IDO SLItemCusts) (GET /load/SLItemCusts). Key properties: Item and CustNum. Filter with a SQL-style `filter` and pick columns with `properties`. The connector pages through all rows with Mongoose bookmarks (200 per page; `limit` sets the page size).
- **Create a Infor SyteLine item customer** (Create). Create a customer item cross-reference (POST /update/SLItemCusts, Action 1 = insert). Key properties: Item and CustNum.
- **Update a Infor SyteLine item customer by ID** (Update). Update a customer item cross-reference (POST /update/SLItemCusts, Action 2): send only the properties to change. With an _ItemId as id, Mongoose checks the row was not changed since it was read. Key properties: Item and CustNum. Required: id.
- **Delete a Infor SyteLine item customer by ID** (Delete). Delete a customer item cross-reference (POST /update/SLItemCusts, Action 4). Key properties: Item and CustNum. Required: id.
- **List all Infor SyteLine item locations** (List). List item stock locations (IDO SLItemlocs) (GET /load/SLItemlocs). Key properties: Item, Whse and Loc. Filter with a SQL-style `filter` and pick columns with `properties`. The connector pages through all rows with Mongoose bookmarks (200 per page; `limit` sets the page size).
- **Create a Infor SyteLine item location** (Create). Create a item stock location (POST /update/SLItemlocs, Action 1 = insert). Key properties: Item, Whse and Loc.
- **Update a Infor SyteLine item location by ID** (Update). Update a item stock location (POST /update/SLItemlocs, Action 2): send only the properties to change. With an _ItemId as id, Mongoose checks the row was not changed since it was read. Key properties: Item, Whse and Loc. Required: id.
- **Delete a Infor SyteLine item location by ID** (Delete). Delete a item stock location (POST /update/SLItemlocs, Action 4). Key properties: Item, Whse and Loc. Required: id.
- **List all Infor SyteLine items** (List). List items (IDO SLItems) (GET /load/SLItems). Key properties: Item. Filter with a SQL-style `filter` and pick columns with `properties`. The connector pages through all rows with Mongoose bookmarks (200 per page; `limit` sets the page size).
- **Create a Infor SyteLine item** (Create). Create a item (POST /update/SLItems, Action 1 = insert). Key properties: Item.
- ...and 80 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
