MCP server for Croit Ceph cluster management with dynamic OpenAPI tool generation
If you already use MCP, the mcp mcp server is the piece that lets your assistant work with it directly. MCP server for Croit Ceph cluster management with dynamic OpenAPI tool generation.
Connect your AI assistant (like Claude) directly to your Croit Ceph cluster for intelligent cluster management, troubleshooting, and monitoring.
An MCP server that gives AI assistants access to your Croit Ceph cluster's REST API. Ask your AI to: - "Show me all pools with errors" - "List OSDs on server node-5" - "Search logs for slow requests in the last hour" - "What's the cluster health status?"
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
list_endpoints — Discover available API endpointscall_endpoint — Make API calls with optimizationsearch_last_result — Drill down into large responsesmanage_services — Ceph servicesmanage_pools — Storage poolsmanage_servers — Cluster serversmanage_s3 — S3 bucketscroit_log_search — Advanced log analysiscroit_log_check — Quick log condition checksConfiguration is passed through the environment: CROIT_HOST, CROIT_API_TOKEN, LOG_LEVEL, YOUR_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of file and storage access servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — list_endpoints, call_endpoint, search_last_result and 6 more — is a fair guide to whether it matches your workflow. It is maintained by croit; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| list_endpoints | Discover available API endpoints |
| call_endpoint | Make API calls with optimization |
| search_last_result | Drill down into large responses |
| manage_services | Ceph services |
| manage_pools | Storage pools |
| manage_servers | Cluster servers |
| manage_s3 | S3 buckets |
| croit_log_search | Advanced log analysis |
| croit_log_check | Quick log condition checks |
**With debug logging:**
```json
{
"mcpServers": {
"croit-ceph": {
"command": "docker",
"args": [
"run", "--rm", "-i",
"-e", "CROIT_HOST=http://your-cluster.croit.io:8080",
"-e", "CROIT_API_TOKEN=your-api-token-here",
"-e", "LOG_LEVEL=DEBUG",
"croit/mcp-croit-ceph:latest"
]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| CROIT_HOST | Endpoint or connection string the server talks to. | Optional |
| CROIT_API_TOKEN | Credential the server authenticates with. | Yes |
| LOG_LEVEL | Configuration value read at startup. | Optional |
| YOUR_TOKEN | Credential the server authenticates with. | Yes |
Scoped local file access — read, write, search and reorganise files in directories you explicitly allow.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Chat with your second brain — search, read and write vault notes through the Local REST API.
Connects AI models to an Obsidian knowledge base for direct access and manipulation of notes and folders.