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
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

33 minutes ago