









































Works out-of-box with your favorite AI agents

DigAlert is the trade name of Underground Service Alert of Southern California, the 811 one-call notification center for Imperial, Inyo, Los Angeles, Orange, Riverside, San Bernardino, San Diego, Santa Barbara and Ventura counties. Excavators open tickets, for example through the DigAlert Direct portal, and the center routes each one to member utility operators, who mark their lines and post an Electronic Positive Response. A ticket carries the work area polygon, work date, work type, excavator contacts and notified members.
Where the connection exposes tickets and responses, the DigAlert MCP takes on the follow-up that fills a contractor's or locator's day. An agent lists tickets nearing the end of their 28-day life and flags which need a renewal or re-mark before crews return. It scans positive responses for codes 021, "No access to locate area", which needs a resend, or 034, "Field meet required", and drafts the call to the facility owner. For a member, it sorts incoming tickets by work date and priority.
You sign in through Makini Link with the DigAlert credentials you already use, paste the MCP endpoint into Claude, ChatGPT, Cursor or another MCP client, and run get_connection_details to see which records that login reaches. On DigAlert's side, members receive tickets by email or webhook and post responses through the member portal, a TCP connection or a REST API that needs a token from the center. Tickets start legal notice periods, so keep creating and renewing them with a person.
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 DigAlert 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 DigAlert 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 DigAlert data without a custom build.
To get started with DigAlert MCP, connect Makini, authenticate DigAlert once, and point your agent at the MCP server. The connector and data mapping already exist, so an agent can be working with DigAlert the same day.
Yes. DigAlert has an MCP server through Makini, which hosts and maintains it. It lets AI agents connect to DigAlert without custom development, on SOC 2 Type II certified infrastructure.