akuig

Telepath AI
MCP Orchestrator

AI-powered cross-silo orchestration for telecommunications BSS, OSS, ITSM & Infrastructure. Connect any LLM to your live network, business, incident management and sovereign data centre systems through the Model Context Protocol.

DEMO ARCHITECTURE AI Agent Claude Desktop / OpenAI / Mistral / Gemini MCP MCP MCP MCP Northbound BSS MCP Server Catalog, Orders, Customers akuig.bss.ngrok.dev/mcp ITSM MCP Server Trouble Tickets (TMF621) ServiceNow / Jira Cloud OSS MCP Server Alarms, Topology, Fault Mgmt akuig.ngrok.io/mcp Infra MCP Server Bare Metal, GPUs, Data Centres akuig.baremetal.ngrok.dev Southbound TMF Open APIs ITSM APIs ENM NBI APIs PostgreSQL SIMULATED LIVE SIMULATED SIMULATED BSS Database Catalog, Customers, Orders ServiceNow / Jira Live ITSM + Confluence KB LIVE Simulated ENM NEs, Alarms, Topology, PM Bare Metal Sim Servers, GPUs, Data Centres TMF620-640 TMF621 · Incidents FM · CM · PM · Topology Provision · GPU · Capacity MCP Protocol TMF Open APIs ITSM APIs (SN / Jira) ENM NBI APIs Bare Metal / Simulated
🔗

Cross-Silo Integration

BSS + OSS + ITSM + Infrastructure in real-time. Single conversation across network, business, incident management and sovereign data centre systems.

🎯

No Hallucinations

Live system data via deterministic API responses. Not generated, not stale embeddings.

📋

Full Audit Trail

Every action logged for compliance. ISO 27001 aligned governance and RBAC.

🏛️

TMF-Compliant

Standards-based TM Forum APIs (TMF620-TMF640). Works with existing systems.

Quick Start — Claude Desktop Setup

Get up and running in 5 minutes. Connect Claude Desktop to the Telepath AI MCP servers for live BSS, ENM, ITSM (ServiceNow or Jira/Confluence) and Bare Metal infrastructure access.

1

Install Claude Desktop

Download from claude.ai/download and install for your platform (macOS, Windows, or Linux).

2

Create a Project with Context

In Claude Desktop, create a new Project and give it a description to help Claude understand the tools it will be working with. For example:

"I am attaching MCP servers to connect Claude to telecommunications platforms. The servers implement TM Forum APIs to Business Support Systems, Ericsson ENM APIs for Operations Support Systems, ITSM APIs for trouble ticket management (ServiceNow or Jira/Confluence), and a Bare Metal/GPU provisioning system for sovereign data centre infrastructure."📋

This gives Claude the context it needs to use the BSS, OSS and ITSM tools effectively.

3

Add Custom MCP Connectors

In Claude Desktop, go to Settings → Connectors, then press the "Add Custom Connector" button. Enter the URL for each MCP server:

https://akuig.bss.ngrok.dev/mcp  (BSS — catalog, orders, customers)

https://akuig.ngrok.io/mcp  (ENM — network, alarms, topology)

https://akuigservicenow.ngrok.dev/mcp  (ITSM - trouble tickets via live ServiceNow)

https://akuigjiramcp.ngrok.dev/mcp  (ITSM - trouble tickets + KB via live Jira/Confluence)

https://akuig.baremetal.ngrok.dev/mcp  (Infrastructure - bare metal & GPU provisioning)

4

Restart Claude Desktop

Quit and reopen Claude Desktop. You should see the MCP tools icon (🔨) appear in the chat input area, confirming the servers are connected.

5

Test It

Try your first prompt:

"What's the current network health status?"📋 Copy
All MCP servers use Server-Sent Events (SSE) transport. Both ITSM servers connect to live instances - ServiceNow and Jira Cloud/Confluence - not simulations. You can add either or both ITSM connectors. The connectors will be available in all new conversations once added.

Demo Scenarios

Walk through these scenarios to see cross-silo BSS + OSS + ITSM + Infrastructure orchestration in action. Each prompt can be typed directly into Claude Desktop.

SCENARIO 1

Proactive NOC — Alarm to Ticket in Seconds

A fiber cut occurs on the Springfield OLT. The AI agent detects the alarm, identifies affected customers, cross-references their SLA tiers, auto-creates a trouble ticket in your ITSM platform (ServiceNow or Jira), and prioritises the response - all in a single conversation spanning ENM (network), BSS (customer) and ITSM systems.

Try These Prompts:

"Check if there are any critical alarms in the network"📋
"What customers are affected by that alarm?"📋
"Create a trouble ticket for this outage with all the details"📋
"Tell me more about Alice Johnson's account"📋

Expected Results:

StepSystemData Retrieved
Alarm detectionENMCritical fiber cut on SPFLD-OLT-01
Customer impactENM3 customers affected via ONTs
SLA prioritisationENMAlice Johnson = Platinum (contact first!)
Trouble ticket createdITSM (SN/Jira)Ticket auto-created with severity, affected customers, network details
Account verificationBSSGood standing, no payment issues
"In under 30 seconds, the AI correlated a network fault to affected customers, created a trouble ticket with full context, and identified that Alice Johnson has a Platinum SLA. That's ENM + BSS + ITSM working together - no manual lookups across multiple systems."
SCENARIO 2

Zero-Touch Service Activation

A new customer wants fiber service. The AI qualifies the address, shows available products with pricing, creates the order, activates the service in the network, and confirms the customer equipment is online — end-to-end orchestration via natural language.

Try These Prompts:

"Can we provide fiber service at 456 Oak Avenue, Springfield?"📋
"What internet products do we have available?"📋
"Create an order for the 1Gbps fiber package"📋
"Activate the service"📋
"Confirm the equipment is online"📋

Expected Results:

StepSystemResult
Service qualificationBSS (TMF637)Fiber available at address
Product catalogBSS (TMF620)Lists products with pricing
Order creationBSS (TMF622)Order ID created, status: created
Service activationBSS (TMF640)Service activated
ONT verificationENMONT online, synchronized
"End-to-end service delivery orchestrated by natural language, with full audit trail. From qualification to activation to verification — all TMF-compliant API calls, all logged."
SCENARIO 3

Pre-Sales Service Qualification

A sales rep needs to quickly qualify an enterprise opportunity. Instead of waiting days for a response, the AI agent checks network topology, verifies capacity, qualifies the service, and retrieves eligible products — all in one conversation.

"Can we offer 1Gbps fibre at Linköping Science Park? What's the lead time?"📋

The agent validates the address, checks nearest network elements, verifies capacity on local aggregation nodes, performs a formal service qualification (TMF637), and retrieves eligible products from the catalog (TMF620).

"Sales can qualify opportunities in minutes vs days. Reduces 'we'll get back to you' scenarios that lose deals."
SCENARIO 4

Network Change Impact Prediction

An engineer is planning maintenance on a cell tower tonight and needs to understand the blast radius before taking it down.

"If I take down eNodeB ERBS01 for maintenance tonight, what's the impact?"📋

The agent identifies the eNodeB, checks connected cells, handover configurations, assesses neighbour capacity, lists dependent services and customers, and checks pending orders — then recommends an optimal maintenance window.

"Enables confident change management. Prevents 'surprise' service impacts from planned maintenance."
SCENARIO 5

Trouble Ticket Lifecycle - ServiceNow or Jira

Manage the full incident lifecycle through natural language. The AI agent creates, enriches, updates and resolves trouble tickets in a live ServiceNow or Jira Cloud instance, automatically correlating network faults and customer data from the BSS and ENM systems. The Jira integration also includes Confluence knowledge base search.

Try These Prompts:

"Show me all open trouble tickets"📋
"Create a high-priority ticket for the fiber outage affecting Springfield customers"📋
"Add a work note to that ticket with the root cause analysis from ENM"📋
"Search the knowledge base for fiber cut resolution procedures"📋
"What Confluence articles do we have about fiber troubleshooting?"📋
"Resolve the ticket — fiber splice completed, service restored"📋

Expected Results:

StepSystemResult
List open ticketsITSM (SN/Jira)Active incidents with severity, priority, assignment
Create ticketITSM + ENM + BSSTicket created with network details and affected customers
Add work noteITSM (SN/Jira)Internal note with root cause from ENM analysis
KB searchSN KB / ConfluenceResolution articles for fiber cut procedures
Resolve ticketITSM (SN/Jira)Ticket resolved with resolution details and category
"Full ITSM lifecycle orchestrated by natural language against live ServiceNow or Jira Cloud instances. The AI enriches tickets with real network and customer data - no copy-paste between systems. Jira integration includes Confluence knowledge base for resolution guidance."
SCENARIO 6

Sovereign GPU Infrastructure Provisioning

A customer needs an H100 GPU cluster for AI training in a specific sovereign data centre. The AI agent checks GPU availability across data centres, provisions the server, allocates GPUs, configures networking and storage - and links everything back to the customer's BSS account for billing.

Try These Prompts:

"What GPU servers are available in our Singapore data centres?"📋
"Check H100 availability across all sovereign data centres"📋
"Provision an 8x H100 GPU cluster for Jane Doe (customer 8452934) in Singapore DC 1"📋
"Show me all infrastructure allocated to customer 8452934"📋
"What's the total capacity summary across all our data centres?"📋

Expected Results:

StepSystemResult
GPU availabilityBare MetalH100/H200/A100 inventory across 6 sovereign DCs
Server provisioningBare MetalServer allocated, OS installed, GPUs assigned
Network configBare MetalVLAN, IP, firewall profile configured
Customer linkageBare Metal + BSSAllocation tied to BSS customer ID for billing
Audit trailBare MetalFull provisioning history logged for compliance
"From GPU availability check to fully provisioned cluster in one conversation. The AI orchestrates across infrastructure and business systems - sovereign data centre, networking, storage and BSS billing linkage."

Use Case Maturity Tiers

A natural progression from safe read-only intelligence to autonomous operations, allowing operators to build confidence incrementally.

Tier 1: Read-Only Intelligence

Cross-silo visibility  ·  Low Risk

Situational awareness and faster decisions

  • Intelligent Network Health Dashboard
  • Pre-Sales Service Qualification
  • Customer Impact Analysis During Outages
  • Network Change Impact Prediction

Tier 2: Assisted Operations

Human-in-loop automation  ·  Medium Risk

Staff productivity, reduced escalations

  • Automated Trouble Ticket Enrichment (ServiceNow / Jira)
  • Service Activation Pre-Check & Validation
  • Capacity Planning Intelligence
  • Complex Service Ordering

Tier 3: Autonomous Operations

AI-initiated actions with guardrails  ·  Higher Risk

Operational efficiency, new capabilities

  • Self-Healing Network: Auto Parameter Rollback
  • Zero-Touch Enterprise Service Provisioning
  • Autonomous GPU Cluster Provisioning
  • Intelligent Alarm Correlation & Root Cause
  • Dynamic Network Slicing Lifecycle

Tier 4: Business Intelligence

Strategic decision support  ·  Low Risk

Data-driven planning, executive insights

  • Network Investment ROI Analysis
  • Regulatory Compliance Audit
  • Sovereign DC Capacity Planning
  • Competitive Network Benchmarking

Network Context — Customers & Topology

The demo environment simulates a two-city network covering Springfield and Shelbyville with 26 network elements and 7 customers across fiber and cable services, plus sovereign data centre infrastructure across 6 locations with bare metal servers and GPU clusters (A100, H100, H200).

Customer Database

CustomerIDAddressServiceSLAStatus
Jane Doe8452934456 Main St2Gbps FiberGoldActive
John Smith8452935123 Main St1Gbps FiberSilverActive
Alice Johnson8452936789 Oak Ave2Gbps FiberPlatinumActive
Stig Larsson8452940456 Oak Ave2Gbps FiberPlatinumNEW
Carol Brown8452938555 Maple Dr1Gbps FiberSilverActive
Bob Williams8452937321 Elm St400Mbps CableBronzeSuspended
David Lee8452939777 Cherry Ln200Mbps CableBronzeActive

Key Network Elements

ElementIDTypeLocation
Core RouterSPFLD-CR-01Core RouterCentral Office
Downtown OLTSPFLD-OLT-01OLTMain St Hub
North OLTSPFLD-OLT-02OLTNorth Springfield
Springfield CMTSSPFLD-CMTS-01CMTSElm Street
Downtown TowerSPFLD-ENB-014G/5GDowntown
Shelbyville CMTSSHBY-CMTS-01CMTSShelbyville
Microwave LinkSPFLD-MW-01Backhaul18GHz, 12.5km

Interactive Network Topology Map

Explore the full network visually. Hover over elements for details, click customers to inspect. Use the controls to simulate alarms and filter link types.

TMF APIs & ENM Tools Reference

The Telepath AI MCP servers expose these tools to any connected LLM. All operations follow TM Forum Open API standards where applicable.

BSS — TMF Forum APIs

APIStandardFunction
Service QualificationTMF637Check service availability at address
Product CatalogTMF620List available products and pricing
Product OrderingTMF622Create and manage orders
Customer ManagementTMF629Retrieve customer account details
Service ActivationTMF640Activate services in network

OSS — ENM Network Tools

ToolFunction
enm_get_alarmsRetrieve active network alarms
enm_get_alarm_summaryQuick health check — alarm counts by severity
enm_get_customers_by_elementFind customers served by a network element
enm_get_network_elementGet details of specific equipment (ONT, OLT)
enm_get_impact_analysisDownstream impact analysis
enm_inject_faultCreate test alarm (demo only)
enm_clear_alarmResolve alarm (demo only)

ITSM - Trouble Tickets (TMF621)

Connected to live ServiceNow and Jira Cloud instances - not simulations. Two MCP servers wrap their respective APIs and expose them as TMF621-compliant tools for trouble ticket lifecycle management. The Jira server also integrates Confluence for knowledge base search.

ToolStandardFunction
create_trouble_ticketTMF621Create incident with severity, priority, customer and service linkage
get_trouble_ticketTMF621Retrieve ticket details by INC number or sys_id
list_trouble_ticketsTMF621Query and filter tickets by status, severity, priority, text search
update_trouble_ticketTMF621Update status, assignment, description, add work notes
add_ticket_noteTMF621Add comments (customer-visible) or work notes (internal)
get_ticket_countsTMF621Aggregate counts by state, priority, severity, assignment group
search_knowledge_base-Search ServiceNow KB or Confluence for resolution guidance
get_knowledge_article-Retrieve full KB article (Jira/Confluence)
list_knowledge_categories-Browse KB categories (Jira/Confluence)
get_project_info-Discover Jira project issue types and priorities
Tickets link to BSS customers via relatedParty[].id and to ENM network elements via relatedObject[].id - enabling full cross-silo traceability from network fault to customer impact to incident resolution. Both ServiceNow and Jira servers share the same TMF621 tool interface.

Infrastructure - Bare Metal & GPU Provisioning

Sovereign data centre infrastructure management. Provision bare metal servers and GPU clusters across multiple data centres with full lifecycle management and audit trail.

ToolFunction
list_available_serversList available servers with filtering (DC, class, GPU, RAM, CPU)
check_gpu_availabilityGPU inventory across DCs by model (A100, H100, H200)
get_server_specificationsServer class/SKU details and capabilities
list_data_centresSovereign DC locations with capacity and power info
provision_bare_metalAllocate a server to a customer with OS and SLA tier
provision_gpu_clusterAllocate GPU server + GPUs, validates availability
deprovision_serverRelease server to pool (requires data wipe confirmation)
get_server_statusFull server details including GPUs, allocation, network
reboot_serverGraceful or hard reboot via BMC/IPMI
get_customer_infrastructureAll infrastructure allocated to a customer
assign_networkConfigure VLAN, IP, firewall on provisioned server
configure_storageAttach NFS/iSCSI/FC storage volumes
get_provisioning_historyAudit trail of all provisioning actions
get_capacity_summaryCapacity overview across all sovereign DCs
Allocations link to BSS customers via customer_id - enabling cross-silo correlation between infrastructure provisioning, customer billing, network services and incident management.

MCP Server Endpoints

BSS Server: https://akuig.bss.ngrok.dev/mcp

ENM Server: https://akuig.ngrok.io/mcp

ITSM Server (ServiceNow): https://akuigservicenow.ngrok.dev/mcp  LIVE

ITSM Server (Jira/Confluence): https://akuigjiramcp.ngrok.dev/mcp  LIVE

Bare Metal Server: https://akuig.baremetal.ngrok.dev/mcp

All servers use Server-Sent Events (SSE) transport and are compatible with any MCP client. Both ITSM servers connect to live instances - ServiceNow and Jira Cloud/Confluence.

Connect to Other LLMs

MCP is an open standard. While Claude Desktop provides the easiest setup, you can connect the Telepath AI servers to other LLM platforms too.

OpenAI — Agents SDK

OpenAI added MCP support via their Agents SDK. Use the SSE transport to connect:

from agents import Agent
from agents.mcp import MCPServerSse

bss_server = MCPServerSse(
    url="https://akuig.bss.ngrok.dev/mcp"
)
enm_server = MCPServerSse(
    url="https://akuig.ngrok.io/mcp"
)
itsm_servicenow = MCPServerSse(
    url="https://akuigservicenow.ngrok.dev/mcp"
)
itsm_jira = MCPServerSse(
    url="https://akuigjiramcp.ngrok.dev/mcp"
)
infra_server = MCPServerSse(
    url="https://akuig.baremetal.ngrok.dev/mcp"
)

agent = Agent(
    name="Telepath NOC Agent",
    instructions="You are a telecom operations assistant...",
    mcp_servers=[bss_server, enm_server, itsm_servicenow, itsm_jira, infra_server]
)

Mistral — Le Chat & Agents API

Mistral supports MCP connectors in Le Chat and via their agents API:

from mistralai import Mistral

client = Mistral(api_key="your-key")

response = client.agents.complete(
    agent_id="your-agent-id",
    messages=[{"role": "user", "content": "Check network alarms"}],
    tools=[
        {"type": "mcp", "server_url": "https://akuig.bss.ngrok.dev/mcp"},
        {"type": "mcp", "server_url": "https://akuig.ngrok.io/mcp"},
        {"type": "mcp", "server_url": "https://akuigservicenow.ngrok.dev/mcp"},
        {"type": "mcp", "server_url": "https://akuigjiramcp.ngrok.dev/mcp"},
        {"type": "mcp", "server_url": "https://akuig.baremetal.ngrok.dev/mcp"}
    ]
)

Google Gemini

Google announced MCP support for Gemini through Vertex AI and the Gemini API. Configure the SSE server URLs as tool providers in your Vertex AI agent setup.

Generic MCP Client

Any MCP-compatible client can connect using SSE transport. Point your client at the server URLs and the available tools will be automatically discovered via the MCP protocol handshake.

MCP vs Traditional RAG

MCP Advantages

  • Real-time data — live system queries, not stale embeddings
  • No hallucinations — deterministic API responses
  • Full audit trail — every action logged for compliance
  • Cross-silo - BSS + OSS + ITSM + Infrastructure in a single conversation
  • Standards-based — TM Forum APIs, not proprietary
  • Write capability — create orders, activate services, not just read

Traditional RAG Limitations

  • Stale data — embeddings need constant refresh
  • Hallucination risk — LLM may fabricate details
  • No audit trail — black box responses
  • Single domain — typically one system at a time
  • Read-only — cannot take actions or orchestrate workflows
  • Data engineering tax — 80% of AI project costs