ELO Digital Office

Setup

1. Confirm the ELO Indexserver (IX) publishes its REST interface — typically https://<server>/ix-<repo>/rest. The repository name is part of the path, so an installation with several archives needs one connector each.
2. Create an ELO user for the integration with read rights on the archive areas the agent should see. ELO enforces ACLs per Sord, so a restricted user sees a smaller archive rather than an error.
3. Set ELO_URL to the IX REST root (no trailing slash), plus ELO_USERNAME and ELO_PASSWORD.

ELO's session is a ticket. The adapter logs in at /ix/login and sends the returned ticket back on every call. AnythingMCP caches it (encrypted, in connector_auth_cache) and re-logs in when ELO expires it — ELO tickets are short-lived and logging in per call would exhaust the server's session pool.

Everything is a Sord. ELO models folders and documents as the same object, a Sord, identified by a numeric objId or a GUID. sordType distinguishes them: values below 254 are folders, 254 and above are documents. An agent that treats every search hit as a document will be wrong about a third of the time.

Keywording forms (Verschlagwortungsmasken) define which index fields a Sord carries. elo_list_keywording_forms returns them, and you need the mask's field group names to make a find request precise.

Find is two calls. ELO's search creates a result set and then pages it: elo_find_first runs the query and returns the first page plus a searchId, and elo_find_next pages through it. Release the search when done or ELO keeps the result set alive.

Unverified. The paths and field names below follow the vendor's published documentation and have not been exercised against a live tenant. Treat a 404 as a docs-versus-reality gap and check the developer portal before concluding that the credential is wrong. A correction from anyone running this against a real system is genuinely welcome.

Self-hosted, which is the thing to plan for.

• On AnythingMCP Cloud the instance must be reachable from the public internet on a real hostname with a valid TLS certificate. A self-signed certificate will fail: the connector offers no trust-anything switch.
• On an internal host (elo.intern, 10.0.0.x), self-host AnythingMCP on the same network and add that host to SSRF_ALLOWED_HOSTS, or the outbound guard refuses the call before it is made.