openshift-backplane-mcp-server

Created By
mmazura year ago
MCP server providing Managed OpenShift infra access via Backplane
Overview

what is openshift-backplane-mcp-server?

The openshift-backplane-mcp-server is a Managed Control Plane (MCP) server that provides access to Managed OpenShift infrastructure via a backplane.

how to use openshift-backplane-mcp-server?

To use the openshift-backplane-mcp-server, you need to set up the server in your OpenShift environment and configure it to manage your infrastructure resources through the backplane.

key features of openshift-backplane-mcp-server?

  • Provides managed access to OpenShift infrastructure.
  • Facilitates resource management through a backplane architecture.
  • Supports integration with various OpenShift components.

use cases of openshift-backplane-mcp-server?

  1. Managing OpenShift clusters efficiently.
  2. Streamlining infrastructure access for developers.
  3. Enhancing resource allocation and management in cloud environments.

FAQ from openshift-backplane-mcp-server?

  • What is the purpose of the openshift-backplane-mcp-server?

It serves as a managed access point for OpenShift infrastructure, simplifying resource management.

  • Is there any cost associated with using the openshift-backplane-mcp-server?

The cost may vary based on your OpenShift subscription and usage.

  • What programming language is the server built with?

The openshift-backplane-mcp-server is built using Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mmazur
Star
0
Language
Python
License
-

Recommend Servers

View All
Voyei

2 hours ago
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