Manage Marzban panels through the Model Context Protocol.
One TypeScript SDK for Marzban, and everything built on top of it. Fix a bug or add an endpoint in the SDK, and the MCP server, the CLI, and every app built on it get it for free.
flowchart LR
Panel(["Marzban Panel"])
SDK["marzban-sdk"]
MCP["marzban-mcp<br/>MCP server"]
CLI["marzban-cli<br/>CLI · WIP"]
App["Your app<br/>Node · Bun · Deno · Browser"]
Agents(["Claude · Cursor · any MCP client"])
Panel <--> SDK
SDK --> MCP --> Agents
SDK --> CLI
SDK --> App
The SDK talks to your Marzban panel. The MCP server and CLI are just clients of that same SDK — same auth, same retries, same typed errors — so they never drift from each other or from your own code.
| Package | npm | Docker | What it is |
|---|---|---|---|
packages/sdk | marzban-sdk | — | The TypeScript SDK — auth, retries, resilient WebSocket reconnects, webhooks, lifecycle |
packages/mcp | marzban-mcp | ilmar7786/marzban-mcp | An MCP server exposing Marzban operations as tools for AI agents |
packages/cli | — | — | A CLI on top of the SDK — WIP, unpublished |
apps/docs | — | — | The documentation site |
Each publishable package has its own version, README.md, changelog and
release tags (sdk-v*, mcp-v*, cli-v*).
Full guides, configuration reference and the complete typed API live at ilmar7786.github.io/marzban-sdk.
For how the repository itself is built — architecture, conventions, testing,
CI and releases — see docs/.
Contributions are welcome — see CONTRIBUTING.md for how to submit a patch. Found a bug or have an idea? Open an issue.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y marzban-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-ilmar7786-marzban-mcp": {
"command": "npx",
"args": [
"-y",
"marzban-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencemarzban-mcpnpmMarzban MCP works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.