Cisco Optical Network Controller Configuration Guide, Releases 26.x.x

PDF

Cisco Optical Network Controller Configuration Guide, Releases 26.x.x

Cisco Optical Network Controller MCP server

Updated: July 22, 2026

Want to summarize with AI?

Log in

This section explains the Cisco Optical Network Controller MCP server, including AI-agent usage, enablement behavior, and hardware requirements. Use it to understand MCP server capabilities before configuration.

Cisco Optical Network Controller MCP server is a Cisco Optical Network Controller capability that

  • supports the related optical network management workflow,

  • provides context for configuration, monitoring, or troubleshooting tasks, and

  • helps operators understand how the feature behaves before they use it.

Cisco Optical Network Controller MCP server details

The Cisco Optical Network Controller MCP server is a Model Context Protocol (MCP) service that exposes supported Cisco Optical Network Controller APIs as tools for AI agents.

  • Cisco Optical Network Controller MCP server is an optional component that requires an additional patch installation. If you want to deploy the MCP server, contact Cisco TAC for guidance and assistance with the installation process.

  • AI agents connect to the server by using an MCP client configuration that includes the Cisco Optical Network Controller MCP endpoint and an Authorization header with Base64-encoded Cisco Optical Network Controller credentials.

  • Installing a Cisco Optical Network Controller service pack disables the MCP Server. Contact Cisco TAC to enabled the MCP server again.

How AI agents use the Cisco Optical Network Controller MCP server

Use the Cisco Optical Network Controller MCP server when you want an MCP-compatible agent to query Cisco Optical Network Controller by calling supported tools instead of directly invoking individual REST APIs.

  • The agent discovers the tools that the Cisco Optical Network Controller MCP server publishes and selects the required tool or tools based on the user request.

  • The MCP server acts as an integration layer between the AI agent and Cisco Optical Network Controller and returns live data from the target system.

  • If the Cisco Optical Network Controller deployment uses a self-signed HTTPS certificate, the MCP client must trust that certificate or use a client-specific workaround before it can connect successfully.

Additional hardware requirements

This table lists the minimum additional hardware requirements to run the Cisco Optical Network Controller MCP server. These CPU requirements are in addition to the vCPU requirements that are listed in the Minimum Hardware Requirements table in the Installation requirements section.

Table 1. MCP server additional hardware requirements

Sizing

CPUs

Extra Small (XS)

16 vCPU baseline + 2 additional vCPU

Small (S)

32 vCPU baseline + 2 additional vCPU

Medium (M)

48 vCPU baseline + 4 additional vCPU

Configure Cisco Optical Network Controller MCP server settings in an AI agent

Use this procedure to configure Cisco Optical Network Controller MCP server settings in an AI agent in Cisco Optical Network Controller. Complete this task when you need to configure, verify, or manage the related network operation.

The Cisco Optical Network Controller MCP server is a feature that is packaged with this release but disabled by default. Cisco TAC or CX must enable the server before you start this procedure.

Before you begin

Before you begin, verify that you have these items:

  • Access to a Cisco Optical Network Controller deployment where the Cisco Optical Network Controller MCP server is enabled

  • A valid Cisco Optical Network Controller username and password

  • An AI agent or MCP client that supports HTTP-based MCP server connections

Follow these steps to configure an MCP-compatible AI agent for the Cisco Optical Network Controller MCP server.

Procedure

1.

Enable the Cisco Optical Network Controller MCP server.

  1. Contact Cisco TAC to enable the MCP server.

    Warning

    Installing a Cisco Optical Network Controller service pack disables the MCP Server. Contact Cisco TAC to enabled the MCP server again.

  2. Reboot the VM.

The Cisco Optical Network Controller MCP server is enabled and ready for client configuration.
2.

Run this command in the operating system terminal to generate the Base64-encoded credentials for the Authorization header.

Example:

printf '%s:%s' "<conc-username>" "<conc-password>" | base64

When you add the encoded value to the MCP configuration file, prefix it with Basic and a space.

Example:

If your output is

aW50ZXJuXYw6Q2lZZ29ATMIz, your configuration entry should look like this: 
"Authorization": "Basic aW50ZXJuXYw6Q2lZZ29ATMIz"

You have the encoded credential string that the AI agent uses in the MCP server configuration.
3.

Open the MCP server configuration for your AI agent.

The exact location and method depends on the AI agent.
4.

Add the Cisco Optical Network Controller MCP server configuration.

Replace <conc-hostname-or-ip> with the Cisco Optical Network Controller host name or IP address that the client can reach.

Example:

{
  "servers": {
    "conc-mcp-server": {
      "url": "https://10.0.10.1:8443/onc-mcp-server/mcp",
      "type": "http",
      "headers": {
        "Authorization": "Basic aW50ZXJuXYw6Q2lZZ29ATMIz"
      }
    }
  },
  "inputs": []
}
{
  "servers": {
    "conc-mcp-server": {
      "url": "https://<conc-hostname-or-ip>:8443/onc-mcp-server/mcp",
      "type": "http",
      "headers": {
        "Authorization": "Basic <base64-encoded-credentials>"
      }
    }
  },
  "inputs": []
}
5.

CONC MCP server uses a self-signed certificate by default, which some agents may not support, in this case:

Note

If the deployment uses a CA-signed certificate, you do not need this workaround.
6.

Enable conc-mcp-server in the AI agent and test the connection.

Ask a question such as What tools are available from the MCP server?.

The AI agent returns the list of tools that the Cisco Optical Network Controller MCP server publishes.

The AI agent is configured to use the Cisco Optical Network Controller MCP server and can query live Cisco Optical Network Controller data through the published MCP tools.

Cisco Optical Network Controller MCP server tool descriptions

Cisco Optical Network Controller MCP server tools provide access to specific controller data, such as alarms, services, inventory, node status, and network summary information.

Cisco Optical Network Controller MCP server provides these tools:

Table 2. Cisco Optical Network Controller MCP server tool descriptions

Tool name

Description

get_conc_agent_guide

Returns the Cisco Optical Network Controller MCP server agent instruction guide and tool-usage guidance. This is also available as resource for agents that support it.

get_ns_timestamp_with_current_date

Returns nanosecond timestamps and dates for a relative or custom time range.

get_chassis_utilization

Analyzes rack, shelf, and chassis utilization data across the network.

get_conc_version

Returns the current Cisco Optical Network Controller software version.

get_top_n_issues

Returns the top network issues or alarms, with optional service impact information.

get_nodes_status

Returns the current status of nodes in the network.

analyze_alarms

Analyzes one or more alarms and provides occurrence statistics and resolution guidance.

get_network_summary

Returns a summary dashboard of overall network status metrics.

get_top_n_history_of_alarms

Returns the top historical alarms for a selected time period.

get_conc_services_mini_data

Returns minimal service or circuit details for the network.

get_services_by_site

Returns the services for a specific site or node.

get_services_by_ppm_and_card

Returns the services that pass through a specific PPM or card.

get_historical_flapping_alarms

Returns historical flapping or fluctuating alarms.

get_services_affected_count_by_top_alarms

Returns the count of services that are affected by the top alarms.

get_services_affected_details_by_top_alarms

Returns detailed information about services that are affected by the top alarms.

get_current_alarm_details

Returns current alarm details with field selection and severity filtering.

get_historical_alarm_details

Returns historical alarm details and trends for a selected time range.

get_services_data_details

Returns detailed information about network services or circuits.

quick_search

Performs a unified search across network inventory tables.

get_nodes_data

Returns detailed node or site inventory data from the node inventory API.