The questionHow does this fit the tooling estate we already have?
AiDN is built on the Model Context Protocol as its primary integration standard. Existing MCP servers in the operator's environment plug in directly as tool providers with no custom adapters, so integration work already completed elsewhere is immediately reusable, and the operator's own orchestration can call AiDN agents through standard APIs.
What we can evidence
Reuse the integration work you have already done.
Studio treats MCP servers as first-class tool providers. Existing MCP servers plug in directly with no custom adapters or translation layers, so integration effort spent elsewhere in the tooling estate carries over.
Connect the data sources operators actually run.
Native support spans ClickHouse, PostgreSQL with PostGIS for geospatial work, MariaDB, REST and OSS APIs, SharePoint document stores, Zendesk ticketing, Zabbix monitoring and Telegram for notification delivery — alongside operator OSS systems, network configuration managers and observability via Langfuse.
Produce deliverables, not just conversation.
Built-in output tooling covers interactive charts, geospatial maps, PDF, Word and Excel generation, and a sandboxed Python environment for statistical analysis. An investigation ends with a report, a map or a structured dataset.
Why MCP rather than another adapter layer
Every integration standard an operator adopts is a bet. The Model Context Protocol is the emerging open standard for connecting tools to agents, which means an MCP server built for one platform works with the next one. Treating MCP as first-class rather than as one connector among many is what makes the integration investment portable, and portability is the property operators have been burned on most often.
Designed to sit alongside what you run
The platform is built for coexistence, not replacement. Operators whose orchestration platforms or existing automation pipelines need to call AiDN agents can do so through standard APIs. The agent layer fits into an existing tooling estate without displacing it, which matters because the alternative — asking an operator to retire working systems to adopt an AI layer — is not a proposition most estates can absorb.
built on
related
Infinity
The no-code platform the whole suite runs on
NetTopo
One end-to-end view, stitched from everything you already have
Core network digital twin
835,000 entities, 2.5 million relationships, one graph
Your knowledge stays yours
Platform IP is ours. Domain IP is yours. Contractually explicit.
Evidence-gated onboarding
Clean data is not a prerequisite — honest data handling is the product