Use ELO ECM Suite with AI via MCP
For many companies and public authorities, the ELO ECM Suite is the long-term memory for contracts, invoices and project files. No MCP server exists for it, so we build the CompanyGPT connection individually on the REST interface of the ELO Indexserver.
What is ELO ECM Suite?
The ELO ECM Suite from ELO Digital Office GmbH in Stuttgart, Germany, is an enterprise content management platform for archiving, digital case files, invoice workflows and contract management. It is predominantly operated on-premises and configured project by project through a partner network; ELO Cloud is available as a hosted operating model.
Because ELO installations have usually grown over many years, they hold a substantial body of knowledge: filing structures, keywording and workflow histories map business processes in detail. An AI assistant can open up that body of knowledge without employees having to know the historically grown folder logic – provided access rights are mapped cleanly.
Connection at a Glance
- MCP server
- None available – individual integration via the Indexserver API
- Interfaces
- ELO Indexserver API (REST/JSON), ELOix for Java/.NET, workflow services
- Authentication
- Ticket-based Indexserver login, SSO/OAuth2 via identity provider possible
- Operating model
- Hybrid – predominantly on-premises, ELO Cloud available
- Permissions
- Dedicated ELO account with its own rights, role-based control in CompanyGPT
How to Connect ELO ECM Suite to CompanyGPT
ELO does not provide an MCP server. For CompanyGPT we therefore implement the integration ourselves, on the same interface the ELO clients use.
The core is the ELO Indexserver API (REST/JSON), which allows searching archive structures, reading documents and keywording fields, and retrieving workflow information; the ELOix client APIs for Java and .NET are available in addition. Sign-in uses the ticket-based Indexserver login, optionally connected to your identity provider via SSO or OAuth2. From the required operations we generate an OpenAPI description that CompanyGPT consumes as MCP tools. As an alternative or complement, n8n can be placed in front as an automation layer when processes span several systems.
Since ELO usually runs in your own data centre, the Indexserver is made reachable for your CompanyGPT environment through your network setup; with ELO Cloud that step is unnecessary. Access uses a dedicated account that is subject to the regular ELO permissions – the integration can only see what this account is allowed to see. Who may use it is controlled by your administrators in CompanyGPT via roles and groups.
Note for on-premises operation: CompanyGPT runs in your own Azure tenant – so your on-premises network can be connected directly: via a site-to-site VPN (Azure VPN Gateway) or ExpressRoute between your corporate network and the virtual network of your CompanyGPT environment. The system does not need to be publicly reachable; we set up the connection together with your IT team.
Typical Use Cases
How AI agents in CompanyGPT work with ELO ECM Suite
Search the contract archive
Procurement asks about terms, durations or contacts and receives the matching contract documents from the ELO archive with a pointer to their location.
Prepare project files
Ahead of a handover, the assistant summarizes the contents and status of a project file instead of leaving successors to work through a grown folder structure.
Track invoice workflows
Accounting clarifies in chat where an invoice workflow currently stands and which approval is still outstanding.
Frequently Asked Questions
ELO ECM Suite and AI – the most important answers
Does ELO offer an MCP server?
No. No MCP server is available for the ELO ECM Suite. We connect the system to CompanyGPT individually via the official Indexserver API.
How does the ELO API become an MCP integration?
We select the operations your use case needs, describe them as an OpenAPI specification and provide them to CompanyGPT as tools. The assistant can then only execute those defined calls.
Are ELO permissions preserved?
Yes. Access runs through a dedicated ELO account subject to the regular archive permissions. Anything that account cannot see stays invisible to the assistant as well.
What needs to be considered for an on-premises installation?
The Indexserver sits in your network and has to be made reachable for your CompanyGPT environment. We plan this together with your IT team; with ELO Cloud the step does not apply.
Can the AI file documents or start workflows?
The Indexserver API supports write operations. Whether we enable them is your decision – projects often start read-only and are extended selectively after a trial phase.
ELO ECM Suite and Your AI – GDPR-Compliant with CompanyGPT
CompanyGPT is the enterprise AI assistant in your own cloud tenant: all relevant AI models, your company data and integrations like ELO ECM Suite – centrally managed, with roles and permissions. We set up the connection together with you.
ELO ECM Suite is a trademark of its respective owner (ELO Digital Office GmbH). Its mention describes compatibility and does not imply any partnership or endorsement. Availability and scope of the connection depend on the respective vendor.