Announcing jabali-mcp — drive your Jabali Panel with an AI assistant #963
Replies: 3 comments 8 replies
|
I personally find it an unnecessary energy wear and tear, and that it would not be a profiter for anyone. cpanel, plesk, with the millions of dollars they have, they didn't do it yet, why is that ? A hosting dashboard, is only used to install things, we don’t live within it, and customers just want it to work always, without ANY bugs. Because not focusing efforts on things that really work and can grow this panel for the community? For example integration with whcms, blesta or wisecp (which i use) so that millions around the world start using it. See the example of CWP , it is used by millions, they charge it 1 dollar per month per server and its very obsolete because it stops its development in centos 7, really centos 7 ??? and jabali is using mcp ? It seems a lot difference to me. I think if you focused on the efforts where the public really uses it, you would grow exponentially. Dont add more features, just make it work without bugs, and integrate with billing panels. |
|
Its pretty neat especially with AI Bot helpers, but yeah focus for sure in the panel itself is key. I plan on switching partially to Jabali Late August early September, |
|
Interesting but not sure I would use it or have any need for it I regularly use Microsoft copilot |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
If you have been asking yourself @johnnyq @mrlp57 @mailanetworks @altomarketing why lately I am slow in responding to your issues, well this is why: https://jabali-panel.com/mcp/
What is it?
jabali-mcp is a Model Context Protocol server for Jabali Panel. It exposes the panel's REST API as tools an AI assistant can call, so you can manage your hosting in plain language from Claude Code, Claude Desktop, Cursor, Codex, or any MCP-capable client.
It's a thin, generated wrapper over the panel's existing API: it reimplements no auth, validation, or scoping — your API token acts as your user, and the panel enforces ownership on every call, exactly as it does for any other API client.
As of v0.3.1 it ships 75 tools covering domains, DNS, SSL, mail (mailboxes, forwarders, autoresponders), applications, databases and DB users, backups, cron, SSH keys, PHP settings, logs, and diagnostics. Full reference: docs/TOOLS.md.
What is it good for?
Things you can just ask for:
diagnose_domaintool pulls config, SSL status, DNS records, recent nginx errors, and bandwidth in one shot and the assistant reads the tea leaves.Safety (this fronts your hosting — it's designed around that)
JABALI_MCP_ALLOW_WRITE=1.confirm: truecall — deletes, restores, password rotations. An AI cannot destroy anything in one step.Quick start
go install github.com/shukiv/jabali-mcp/cmd/jabali-mcp@latest.jabali-mcp init— it prompts for your panel URL + token, verifies them, and writes the config.claude mcp add jabali -- jabali-mcpStart read-only. Add
JABALI_MCP_ALLOW_WRITE=1when you're comfortable, andJABALI_MCP_DRY_RUN=1to watch what it would do first. The README covers Claude Desktop, Cursor, Codex, OpenCode, fleet mode (multiple panels), and running over SSH.What should it do next?
This is where you come in. Current candidates on the list:
diagnose_domain— e.g. a mail-deliverability triage (DNS + DKIM + recent mail logs in one answer)?What would you ask an assistant to do on your panel? Which everyday task is still too many clicks? Anything you'd want gated even harder? Drop ideas below — tool requests, workflow stories, or safety concerns all welcome.
All reactions