What it does
Manage domains, DNS, mail, databases and backups on a Jabali Panel hosting server.
- Connects Runs on your computer
- Account or key Needs JABALI_API_TOKEN · 1 setting to fill in (JABALI_PANEL_URL)
- Category Developer tools
Use together with
Skills that teach the AI this kind of work; they work alongside this one
andrej-karpathy-skills
A single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
Why it ranks here
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 6/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 18/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Install
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
Download the maker’s installer
Download the maker’s .mcpb file
The .mcpb file comes straight from the maker; we do not change it
Double-click the file, then click Install in the Claude desktop app
Try it
Use Jabali Panel and tell me what you can do for me, then show me one thing✓ If Claude says it is using Jabali Panel or shows a Jabali Panel tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect Jabali Panel yet
Jabali Panel runs on your computer, but ChatGPT can only connect servers that run on the web
What you can do instead
A · Use an app that can connect Jabali Panel
- No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
B · Others in Developer tools that work with ChatGPT
Picked from the most used in the same category, only ones that connect by address with no key
- Sentry✓ ChatGPT
- Compiler Explorer✓ ChatGPT
- GitDiagram✓ ChatGPT
Claude Code cannot connect Jabali Panel yet
The maker only provides an installer for the Claude desktop app
What you can do instead
A · Use an app that can connect Jabali Panel
- No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
Cursor cannot connect Jabali Panel yet
The maker only provides an installer for the Claude desktop app
What you can do instead
A · Use an app that can connect Jabali Panel
- No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
VS Code cannot connect Jabali Panel yet
The maker only provides an installer for the Claude desktop app
What you can do instead
A · Use an app that can connect Jabali Panel
- No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
For developers: Terminal commands and JSON settings
Values you fill in
JABALI_PANEL_URLrequired envPanel API URL, for example https://panel.example:8443/api/v1JABALI_API_TOKENsecret required envA jat_ API token from the panel. Use a non-admin token.
Descriptions are as written by the maker.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
At a glance
- Downloads per weeki
- Not on npm/PyPI
- Connection
- Runs on your computer
- Latest versioni
- 0.6.1
- Categoryi
- Developer tools
- Published to registryi
- Nov 1, 2026
- Code last changedi
- Nov 1, 2026
- Maker
- shukiv
- Packages
mcpb: …/jabali-mcp-0.6.1.mcpb- Website
- jabali-panel.com
- Registry status
- Active
Which apps can use it
Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Related guides
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account shukiv, which owns the repo
- ✓ Pass
Still maintained
Code last changed 18 days ago
- ✓ Pass
Has a licence
Uses AGPL-3.0
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Published vulnerabilities (OSV.dev)
Not checked: only npm and PyPI packages with a version can be checked
Makers: ask for a re-check or report wrong info
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/shukiv-jabali-mcp)Discussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
User reviews
No reviews yet
Compared with others in Developer toolsi
- More stars than 77% of the other 6116 servers in this category
- Published to the registry more recently than 61% of the other 6116 servers in this category
- Basic checks equal to or better than 99% of the other 6116 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Jabali Panel safe?
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: JABALI_API_TOKEN
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed 18 days ago, and the latest version (0.6.1) reached the registry 18 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
What can I use instead?
In the same category: GitDiagram, Appllama, Cloudflare MCP, Omnara, Repowise
Similar alternatives
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitDiagram
Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
Appllama
Study screens, flows and paywalls from top-earning iOS apps, then build from what wins.
Cloudflare MCP
Cloudflare MCP servers
Omnara
Deploy durable AI agents with Omnara, an open-source managed-agent platform.
Repowise
Codebase intelligence for AI coding agents: graph, git history, docs, decisions, code health.
| This one Jabali Panel | GitDiagram | Appllama | Cloudflare MCP | Omnara | Repowise | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Cloud or install on your computer |
| Needs a key | Yes | No | No | No | No | No |
| Add with + in Claude | No | No | No | Yes | No | No |
| Basic checks | 3/3 | 4/4 | 4/4 | 4/4 | 4/4 | 5/5 |
| License | AGPL-3.0 | MIT | MIT | Apache-2.0 | Apache-2.0 | AGPL-3.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
jabali-mcp
A [Model Context Protocol](https://modelcontextprotocol.io) server for [Jabali Panel](https://github.com/shukiv/jabali-panel).
Install | Set up | Tools | Safety | Generation
Lets an AI assistant drive panel operations — domains, DNS, mail, applications, databases, backups — through natural language. It's a thin, generated wrapper over the panel's existing REST API: it reimplements no auth, validation, or scoping, it rides them.
Status: working MVP. Read tools + gated write/destructive tools + a fleet
registry, generated from the panel's OpenAPI spec (a golden test fails if the
checked-in code drifts from the spec).
Install
Prerequisites: Go 1.25+ and a reachable Jabali Panel with an API token (see Set up). The server speaks MCP over stdio — an MCP client (Claude Code, Claude Desktop, …) launches it; you don't run it as a daemon.
Prebuilt binaries
Grab the binary for your platform from the latest release (linux/darwin × amd64/arm64, with SHA256SUMS), then:
chmod +x jabali-mcp_*_linux_amd64
sudo install -m 0755 jabali-mcp_*_linux_amd64 /usr/local/bin/jabali-mcp
With go install
go install github.com/shukiv/jabali-mcp/cmd/jabali-mcp@latest
The binary lands in $(go env GOBIN) (or $(go env GOPATH)/bin).
From source
git clone https://github.com/shukiv/jabali-mcp.git
cd jabali-mcp make build # -> ./jabali-mcp (stamps the version from git describe)
Update
jabali-mcp update --check # report the latest release, install nothing
jabali-mcp update # re-installs the latest (go install …@latest) jabali-mcp update --ref v1.2.3 # pin a tag/commit jabali-mcp update --dry-run # print the command only
Self-update runs go install, so it needs Go on the PATH. Restart your MCP client afterward to pick up the new binary. (Installed from a checkout instead? git pull && make build. Installed a prebuilt binary? Download the new release.)
Verify
JABALI_PANEL_URL=https://panel.example:8443/api/v1 \
JABALI_API_TOKEN=jat_… \ jabali-mcp < /dev/null
-> jabali-mcp — read-only; panels: [default]
It reads config from the environment, prints a one-line status to stderr, then serves MCP on stdin/stdout (it exits on EOF, which is why the < /dev/null smoke test returns immediately).
Set up
Quickest: the guided walkthrough
jabali-mcp init
It prompts for each panel (name, URL, token), verifies the token against the panel, and writes a 0600 panels.json to your config dir (~/.config/jabali-mcp/panels.json). Add as many panels as you like — one for a single instance, several for a fleet. Because that path is the default, the server finds it with no env vars, so registering with a client is just:
claude mcp add jabali -- jabali-mcp # no --env needed after init
Re-run init any time to reconfigure. The manual steps below are the same thing by hand.
Manual
1. Mint an API token. In the panel, go to the tenant shell → API Tokens and create one. The plaintext jat_… is shown once — copy it. Use a non-admin (tenant) token so the server is confined to that one account.
2. Point the server at your panel with these environment variables:
| Variable | Required | Meaning |
|---|---|---|
JABALI_PANEL_URL | ✓ | e.g. https://panel.example:8443/api/v1 |
JABALI_API_TOKEN | ✓ | the jat_… bearer token |
JABALI_PANEL_NAME | logical name (default default) | |
JABALI_CA_FILE | PEM bundle to trust a self-hosted panel CA | |
JABALI_MCP_ALLOW_WRITE | 1 to enable mutating tools (default: read-only) | |
JABALI_MCP_DRY_RUN | 1 to force every write to preview instead of act | |
JABALI_MCP_ADMIN | 1 to also expose the /admin/* tools (needs an admin token) | |
JABALI_PANELS_FILE | JSON array of panels for fleet mode (overrides the single-panel vars) |
3. Register it with your MCP client. In every example below jabali-mcp is assumed on your PATH (else use its full path), and the two required env vars are shown inline. It's a stdio MCP server, so any MCP-capable client can launch it.
Claude Code (CLI — writes .mcp.json / your Claude config):
claude mcp add jabali \
--env JABALI_PANEL_URL=https://panel.example:8443/api/v1 \ --env JABALI_API_TOKEN=jat_… \ -- jabali-mcp
Claude Desktop — claude_desktop_config.json:
{
"mcpServers": { "jabali": { "command": "jabali-mcp", "env": { "JABALI_PANEL_URL": "https://panel.example:8443/api/v1", "JABALI_API_TOKEN": "jat_…" } } } }
OpenAI Codex (CLI — writes ~/.codex/config.toml):
codex mcp add jabali \
--env JABALI_PANEL_URL=https://panel.example:8443/api/v1 \ --env JABALI_API_TOKEN=jat_… \ -- jabali-mcp
or edit ~/.codex/config.toml by hand — note it's TOML, and the key is mcp_servers (underscore), not the JSON mcpServers:
[mcp_servers.jabali]
command = "jabali-mcp"
[mcp_servers.jabali.env] JABALI_PANEL_URL = "https://panel.example:8443/api/v1" JABALI_API_TOKEN = "jat_…"
OpenCode — opencode.json:
{
"$schema": "https://opencode.ai/config.json", "mcp": { "jabali": { "type": "local", "command": ["jabali-mcp"], "environment": { "JABALI_PANEL_URL": "https://panel.example:8443/api/v1", "JABALI_API_TOKEN": "jat_…" }, "enabled": true } } }
Kimi Code CLI (writes ~/.kimi/mcp.json):
kimi mcp add --transport stdio jabali \
-e JABALI_PANEL_URL=https://panel.example:8443/api/v1 \ -e JABALI_API_TOKEN=jat_… \ -- jabali-mcp
Cursor, Windsurf, Cline, Gemini CLI, and other clients that use the standard mcpServers JSON take the same entry as Claude Desktop above — a { "command": "jabali-mcp", "env": { … } } block under mcpServers in that client's config file.
Start read-only. When you want mutations, add JABALI_MCP_ALLOW_WRITE=1 to the env (and, at first, JABALI_MCP_DRY_RUN=1 to watch what it would do).
Run it on a remote box over SSH
Because it speaks stdio, any of the above can launch it on a remote host over SSH instead of locally — the tool stream tunnels through the SSH pipe. Set the client's command to ssh and pass the remote invocation as its argument, e.g. for Claude Desktop:
{
"mcpServers": { "jabali-prod": { "command": "ssh", "args": ["operator@box", "JABALI_PANEL_URL=https://localhost:8443/api/v1 JABALI_API_TOKEN=jat_… jabali-mcp"] } } }
On the box the panel API is reachable at localhost, and the token still scopes everything to its user. Nothing to install client-side beyond an SSH key.
Fleet (multiple panels)
The easiest path is jabali-mcp init — add several panels when it asks "Add another panel?". It writes them to the default panels.json, which the server loads automatically.
Equivalently, point JABALI_PANELS_FILE at a JSON array (this overrides the single-panel vars), or write that array yourself:
[
{ "name": "prod-a", "url": "https://a:8443/api/v1", "token": "jat_…" }, { "name": "prod-b", "url": "https://b:8443/api/v1", "token": "jat_…" } ]
Config resolution order: JABALI_PANELS_FILE → single-panel env (JABALI_PANEL_URL + JABALI_API_TOKEN) → the default panels.json. In a fleet, every tool takes an optional panel argument to pick one; omit it for the first (default) panel.
Admin tools (same binary, separate opt-in)
The admin operator surface (list/create users, read/update server settings, run panel updates and read their status) lives in the same binary but a separate registration group, exposed only with JABALI_MCP_ADMIN=1. It fronts whole-box operations — a far larger blast radius than the tenant tools — so it is deliberately opt-in and requires an admin token (the panel's RequireAdmin rejects a non-admin token with 403 regardless of the flag). Admin write tools still need ALLOW_WRITE, and admin_run_updates is confirm-gated. admin_renew_ssl and admin_retry_ssl also live here: their paths look tenant-scoped, but the panel registers them behind RequireAdmin. Give the admin server its own admin token; use tenant tokens for everything else.
Auth model — inherits the panel's tenant isolation
Tools authenticate with the per-user Bearer token. The token acts as its owning user and the panel enforces ownership on every endpoint, so the server can only ever reach the resources that token's user owns — a tenant token is confined to that tenant. That is why a non-admin token is the safe default.
Safety
This fronts a hosting control plane, so mutation is fenced in four layers:
- Read-only by default. Write tools register only with
JABALI_MCP_ALLOW_WRITE=1. - Destructive tools require `confirm: true`. Every
delete_*/revoke_*/rotate_*_passwordtool (plusrestore_backup,disable_ssl) returns a preview and acts only when re-called withconfirm: true. A model cannot destroy state in one step — the guard against a prompt-injected tool call. - Tool hints. Read tools carry
readOnlyHint; destructive tools carrydestructiveHintso clients can surface the risk. - Dry-run. Any write tool accepts
dry_run: trueto return the exact request it *would* send without acting;JABALI_MCP_DRY_RUN=1forces that globally.
TLS verification is always on. To trust a self-hosted panel's private CA, point JABALI_CA_FILE at its bundle — that *adds* the CA, it never disables verification.
Tools
Full per-tool reference with arguments and constraints: [docs/TOOLS.md](docs/TOOLS.md) (generated — make docs).
Read (always on): list_domains, get_domain, list_dns_records, list_mailboxes, list_forwarders, list_applications, list_databases, list_backups, list_api_tokens, list_mail_logs, tail_web_log, get_ssl_status, get_domain_whois, get_domain_bandwidth, whoami, get_disk_usage, list_activity, list_cron_jobs, get_cron_job, get_cron_log, list_app_catalog, get_application, get_database, list_database_users, get_mailbox, get_autoresponder, get_backup_manifest, list_ssh_keys, get_php_settings, list_php_versions, list_files, preview_file — plus the composite diagnose_domain (config + SSL + DNS + recent errors + bandwidth in one answer; a failed probe is reported without failing the rest) and report_issue (draft a bug report / feature request for the jabali-panel or jabali-mcp GitHub repo as a prefilled link; in write mode it can also file it directly via gh, gated by confirm: true) and search_docs (look up the official panel documentation from jabali-panel.com mid-task — anonymous, origin-restricted fetches; override the source with JABALI_DOCS_URL).
preview_filereads file contents (up to 1 MiB) into the conversation — that
can include secrets such as
wp-config.php.create_database_userand the
rotate_*_passwordtools return the plaintext secret once, by panel design.
Write (needs `JABALI_MCP_ALLOW_WRITE=1`): create_domain, update_domain, create_dns_record, update_dns_record, create_mailbox, create_forwarder, create_backup, install_application, `create_dat