01 · Interface
No REST API out of the box
The path that can be traced is a licensed .NET SDK, not a web API. It has to be wrapped in a service before an agent can call it, and that service becomes part of what your IT team runs.
For Dutch manufacturers running Ridder iQ
A Ridder iQ MCP server built on the Ridder iQ SDK, under each person's own Ridder iQ login
A Ridder iQ MCP server gives Claude, ChatGPT or Copilot named tools for offers, work orders and stock in Ridder iQ from ECI Software Solutions. Ridder iQ has no public REST API; the traceable interface is the separately licensed .NET SDK, wrapped in a service. ECI ships no Ridder iQ MCP server as of 21 September 2026.
Why Ridder iQ is hard for agents
Where a Ridder iQ connection needs engineering, not configuration
02 · Identity
Sessions log in per user and company
The SDK logs in with a user and a company. The wrapper has to hold a session per person and company and reuse it safely, so answers stay inside that person's Ridder iQ rights.
03 · Data model
Tables, not business objects
Access is at table and recordset level, with customer-specific scripting and calculated columns. Business meaning, such as what counts as an open offer, has to be mapped per installation with your Ridder iQ owners.
04 · Ownership
Ridder now sits under ECI
Ridder iQ belongs to ECI Software Solutions, and ridder.nl now redirects to ecisolutions.com. Partner documentation and support paths changed with it, so the SDK licence and material are requested through ECI.
Checked 21 September 2026
Ridder iQ at a glance: interfaces, access and what exists for AI
| What we found | |
|---|---|
| Interfaces | Ridder iQ SDK (Ridder.Client.SDK) (.NET SDK, docs not published): separately licensed SDK module; a .NET client that logs into the Ridder iQ Service and works on recordsets by table name, so any REST layer has to be built on top · API coupling for customer and order data (not published, docs not published): listed by ECI for CRM and e-commerce data exchange, without technical detail · Standard integrations (file/EDI, docs not published): Gatewise purchasing, CAD/CAM and PDM/PLM to BOM, Exact, Twinfield and AFAS accounting, Qlik Sense BI, OCR and CPQ |
| Authentication | Not documented publicly. A community SDK project logs in with username, password and company against the Ridder iQ Service. |
| Vendor MCP server | No vendor server. No Ridder iQ MCP server from ECI; a GitHub search for Ridder iQ returns only community scripting and a C# SDK wrapper, no MCP server. |
| Vendor AI assistant | ECI promotes ECI AI and says AI functions are integrated in its ERP solutions, without naming Ridder iQ-specific features. |
| Other connectors | RidderIQAPI is a community ASP.NET Web API with Swagger over the Ridder iQ SDK, covering records, permissions, documents, sales and stock actions; it needs the SDK module licence. |
ECI Software Solutions (Ridder iQ) (NL). Manufacturing SMEs, mainly in the Netherlands, in metal fabrication, machine building, construction, high-tech and offshore, doing engineer- and make-to-order work.
What we build
A first Ridder iQ tool list, written as the manifest your IT team signs
ECI Software Solutions (Ridder iQ) does not publish its interface reference, so every backend below is confirmed against your installation in the blueprint before a tool is built.
# ridder-iq-mcp-server: tool manifest, draft for blueprint week 1
# Every tool runs as the person asking. Nothing is written without a person confirming.
tools:
query_records: # table, filter, columns -> rows from allow-listed tables
backend: Ridder.Client.SDK CreateRecordset
mode: read
get_open_offers: # customer -> open offers with value and status
backend: SDK recordset, table confirmed in blueprint
mode: read
get_work_order_status: # project or order -> work orders with planned against actual
backend: SDK recordset, table confirmed in blueprint
mode: read
get_item_stock: # item code -> stock and reservations
backend: SDK recordset, table confirmed in blueprint
mode: read
draft_order_from_offer: # offer -> sales order proposal for a person to confirm
backend: SDK action, confirmed in blueprint
mode: propose
audit: every call logged with user, tool, arguments and the Ridder iQ responseThe manifest is the contract. A question that needs an operation not on it gets a new line and a review, not a wider permission.
Ridder iQ holds the records. An assistant without a governed way in answers from whatever someone pasted into the chat. The connector is the governed way in: named operations, the person's own permissions, every call logged.
What the connector answers, and what it will not do
Questions it answers
- Which work orders for project P are behind schedule?
- What is the stock and reserved quantity for item I?
- Which offers to customer X are still open, and what is their value?
What it will not do
- Read more than the asking user may read in Ridder iQ; every call runs in that person's own SDK session.
- Create a sales order by itself: the only write tool drafts one from an offer, and a person confirms it in Ridder iQ.
- Read any table the model chooses: the generic query tool is limited to an allow-list of tables agreed in the blueprint.
When this is the wrong page
If the need is dashboards, the Qlik Sense integration ECI lists is the shorter path, and cross-year analysis belongs in a data warehouse. A connector is right when people ask questions in Claude, ChatGPT or Copilot, or need Ridder iQ combined with another system.
Start with the Readiness Blueprint.
Two weeks, €4,900 fixed price. Week one agrees the tool list with your Ridder iQ owners and checks every backend against your release and licence. Week two tests whether a person's own Ridder iQ permissions reach through the connector. You keep the manifest and a costed build plan, whoever builds it. All prices are net and exclude VAT.
What we need from you: a named Ridder iQ administrator, a test or sandbox system we may call, and one business owner who can say which questions the assistant should answer first. The first production connector is usually a use-case pilot from €15,000; it runs in your environment, and the code is yours.
Related
- Connectors for 100 source systems — the dated catalogue this page belongs to
- Claude MCP server development — how we build an MCP server for any internal system
Questions Ridder iQ teams ask before the first tool call
Does Ridder iQ have its own MCP server?
Not as of 21 September 2026. ECI promotes ECI AI across its ERP products without naming Ridder iQ features, and GitHub shows only community scripting and an SDK wrapper for Ridder iQ. An MCP server for Claude, ChatGPT or Copilot has to be built on the Ridder iQ SDK.
Do we need extra Ridder iQ licences for an AI connector?
Yes. The Ridder iQ SDK is a separately licensed module, and the community wrapper also needs it. What the licence costs, and whether ECI's API coupling offers another route, is a question to check with ECI. The blueprint answers it before any build starts.
Can the assistant see data a user is not allowed to see in Ridder iQ?
No. Each call runs in the asking person's own SDK session for their company, so Ridder iQ decides what that person may read. The generic query tool is further limited to an allow-list of tables, and that is tested before go-live.
What does a Ridder iQ connector cost?
The two-week Readiness Blueprint is fixed at €4,900: agreed tool list, backends checked against your release, identity tested end to end, costed build plan. The production connector is usually a use-case pilot from €15,000. Prices are net, excluding VAT.
Next step
Not a sales call. An architecture call.
Thirty minutes with the engineer who would build the connector, with your Ridder iQ administrator in the room if you like.