









































Works out-of-box with your favorite AI agents

EDAMS (Engineering Design and Management Systems) is a software suite from EDAMS Technology, the development arm of the Cyprus-based Hydro-Comp Group. It serves water and sanitation utilities, electricity distributors, municipalities and government environmental departments. On the asset side it combines an industry-specific register of network elements such as pipes and pumps, a GIS module, and Maintenance Management covering complaints, work orders, preventive and routine programs and maintenance history. Billing and CRM modules sit alongside.
Where a connection exposes the relevant records, the EDAMS MCP answers questions a maintenance planner or call center supervisor would otherwise work out screen by screen. The agent can list open work orders raised from customer complaints in one supply zone, pull the maintenance history of a pumping station before proactive work is scheduled, or check which network assets are due for routine inspection. Where the connection permits writes, it can draft a work order from a logged complaint for a supervisor to confirm.
You sign in to EDAMS through Makini Link, then paste the MCP endpoint Makini issues into Claude, ChatGPT, Cursor or another MCP client, and get_connection_details shows which objects and fields that connection offers. EDAMS packages run either as a yearly cloud subscription, hosted by EDAMS Technology or a provider the utility appoints, or locally on the utility's own servers. For a locally hosted installation, IT may need to allowlist Makini's fixed IP addresses or set up a VPN first.
Have any questions? We’re here to help You
Minutes, not a project. You point your agent at a single Makini MCP endpoint and authenticate once. There's no per-system SDK, data mapping, or integration to build on your side. That same endpoint reaches EDAMS and 2,000+ other EAM/CMMS, ERP, and WMS systems.
No. Makini owns the connectors. When a vendor ships an API change, deprecates an endpoint, or updates its auth, we fix it on our side. Your agent keeps calling the same tools with no rebuild, redeploy, or downtime on your end.
It still connects. Hundreds of providers in EAM, ERP, and WMS have no API or are heavily customized. Makini builds and owns adapters, so your agent reaches those systems through the same MCP endpoint as everything else.
Same platform, two entry points. MCP server lets AI agents (Claude, ChatGPT, Cursor, and others) reach your systems through the Model Context Protocol. Unified API covers traditional app and backend integrations over REST. Unified API exposes normalized data, MCP provides product-specific tools, both cover the same 2,000+ systems listed on Makini.
Yes. Many enterprises choose to connect through Makini specifically because of security. Every user is authenticated with dedicated scoped token. This comes with tool and record level permissions management even if the agent you are connecting doesn't support it on its own.
You connect AI to EDAMS by running Makini's MCP server in front of it. The server works with any MCP-compatible agent, so any AI can read and write EDAMS data without a custom build.
To get started with EDAMS MCP, connect Makini, authenticate EDAMS once, and point your agent at the MCP server. The connector and data mapping already exist, so an agent can be working with EDAMS the same day.
Yes. EDAMS has an MCP server through Makini, which hosts and maintains it. It lets AI agents connect to EDAMS without custom development, on SOC 2 Type II certified infrastructure.