Rook Ceph Mcp

Created By
Shreyansh Sanchetia year ago
A Model Context Protocol (MCP) server for managing Rook Ceph storage clusters in Kubernetes environments.
Overview

what is Rook Ceph MCP?

Rook Ceph MCP is a Model Context Protocol (MCP) server designed for managing Rook Ceph storage clusters within Kubernetes environments.

how to use Rook Ceph MCP?

To use Rook Ceph MCP, you can install it locally, host it in the cloud, or deploy it using Docker. Follow the installation instructions provided in the documentation to set it up according to your needs.

key features of Rook Ceph MCP?

  • Cluster Management: Monitor and manage Ceph clusters.
  • Storage Resources: Handle block pools, filesystems, and object stores.
  • Manifest Templates: Access pre-configured YAML templates for common resources.
  • Kubernetes Integration: Seamless integration with Kubernetes API.
  • Troubleshooting: Built-in prompts for setup and troubleshooting assistance.

use cases of Rook Ceph MCP?

  1. Managing storage resources in a Kubernetes environment.
  2. Monitoring the health and status of Ceph clusters.
  3. Automating the creation and management of storage pools and filesystems.

FAQ from Rook Ceph MCP?

  • Can Rook Ceph MCP manage multiple Ceph clusters?

Yes, it can manage multiple clusters simultaneously.

  • Is Rook Ceph MCP compatible with all Kubernetes versions?

It is designed to work with Kubernetes clusters that have Rook Ceph installed.

  • How do I troubleshoot issues with Rook Ceph MCP?

Use the built-in troubleshooting prompts or refer to the Rook Ceph documentation for guidance.

Server Config

{
  "mcpServers": {
    "rook-ceph-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-p",
        "3000:3000",
        "rook-ceph-mcp"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Shreyansh Sancheti
Star
-
Language
-
License
-

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