Onos Mcp Server

Created By
ortega-kb4 months ago
Model Context Protocol (MCP) for the ONOS SDN controller. This server exposes the network state (topology, flows, statistics) to AI agents, facilitating automation and intelligent monitoring of SDN networks.
Overview

What is ONOS MCP Server?


The ONOS MCP Server is a Model Context Protocol (MCP) server implementation built with Java 21 and Spring Boot. It provides a professional bridge to the ONOS SDN controller, allowing AI models to manage network infrastructure, control OpenFlow devices, and access real-time network analytics through a secure REST API.

How to use ONOS MCP Server?


  1. Build: Clone the repository and run ./mvnw clean install to generate the JAR.
  2. Configure: Set your ONOS URL and credentials in src/main/resources/application.yaml or via environment variables (ONOS_CONTROLLER_HOST, etc.).
  3. Run: Start the server using java -jar target/onos-mcp-server-0.0.1-SNAPSHOT.jar.
  4. Connect: Add the server configuration to your MCP client (Claude Desktop, Antigravity, etc.) using the JSON snippet provided in the main README.

Key features of ONOS MCP Server?


  • Application Control: Dynamically list, activate, and deactivate ONOS applications.
  • Infrastructure Inventory: Full visibility into switches, routers, and network topology.
  • Host Tracking: Monitor end-node locations, IP addresses, and MAC associations.
  • Flow Management: Programmatically add, remove, and list network flow rules.
  • Production Ready: High-performance implementation using Spring Cloud OpenFeign and Spring AI.

Use cases of ONOS MCP Server?

  • Enterprise SDN Automation: Managing large-scale network configurations with AI assistance.
  • Rapid Prototyping: Developing and testing new network flow logic using natural language.
  • Network Observability: Real-time monitoring and diagnosis of network anomalies by AI agents.
  • Academic Research: Platform for testing Software-Defined Networking concepts and AI-driven orchestration.

FAQ

What programming language is ONOS MCP Server written in? It is written in Java 21 using the Spring Boot framework.

Is there a license for using ONOS MCP Server? Yes, it is licensed under the MIT License, which allows for free use, modification, and redistribution.

What are the requirements to run ONOS MCP Server? You need Java 21 (JDK), Maven (wrapper included), and an accessible ONOS Controller (v2.x or higher) with REST API access.

Project Info
Created At
4 months ago
Updated At
4 months ago
Author Name
ortega-kb
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago