Marzban MCP

io.github.Ilmar7786Published by GitHub account Ilmar7786v0.4.0Updated Oct 24, 2026

Manage Marzban panels through the Model Context Protocol.

Overview

AI-generated overview

Local MCP server that exposes Marzban VPN panel operations as tools so an AI assistant can manage a Marzban panel.

What you can do
  • Expose Marzban panel operations as tools for AI agents, built on the marzban-sdk TypeScript client.
  • Manage a Marzban panel through the Model Context Protocol, sharing the SDK's authentication, retries and typed errors.
  • Run locally over stdio, either from the npm package via npx or from the Docker image.
  • The manifest lists no individual tools, so the exact set of operations is not documented here.
When to use it
Useful when you run a Marzban panel and want an assistant to carry out panel management tasks from a chat client such as Claude or Cursor instead of the panel UI or API by hand.
Requirements
Runs as a local process over stdio, via npx (npm package marzban-mcp) or the Docker image ilmar7786/marzban-mcp. Requires the environment variables MARZBAN_BASE_URL (panel URL), MARZBAN_USERNAME and MARZBAN_PASSWORD (administrator credentials), plus network access to the panel.
Before you install
The server needs Marzban administrator credentials (MARZBAN_USERNAME and MARZBAN_PASSWORD) in its environment, so store them carefully. It manages a live panel, so assistant actions may create, change or delete users and other panel data. The manifest lists no tools, so review what it can do before pointing it at a production panel.

Installation

In SourceWeft

  1. Open Marzban MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[MarzbanSDK]

MarzbanSDK

A TypeScript toolkit for the Marzban API.

[CI] [license]

Documentation · SDK · MCP Server


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.

How it fits together

mermaid
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.

Packages

PackagenpmDockerWhat it is
packages/sdkmarzban-sdk—The TypeScript SDK — auth, retries, resilient WebSocket reconnects, webhooks, lifecycle
packages/mcpmarzban-mcpilmar7786/marzban-mcpAn 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*).

Documentation

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/.

Contributing

Contributions are welcome — see CONTRIBUTING.md for how to submit a patch. Found a bug or have an idea? Open an issue.

License

MIT © ilmar7786

If this project saves you time, consider giving it a ⭐ on GitHub.

Source: README.md at commit 4318c88

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not start.

Version history

2
  1. v0.4.0LatestOct 21, 2026
  2. v0.3.0Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts