Skip to main content
Glama

Related Servers

Alternatives to marzban-mcp

Related Servers

  • A
    license
    Not graded
    quality
    A
    maintenance
    Manage a fleet of OPNsense firewalls from an AI agent, inside guardrails it can't drive around. MCP server for central management of OPNsense firewall fleets. 129 tools across devices, config sync, tasks, schedules, templates, backups and remote consoles - destructive actions confirmation-gated, MCP-issued tokens lifetime-bounded, backup and storage secrets excluded from the toolset entirely.
    Apache 2.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    MCP server for regulated enterprises, providing per-tool RBAC, redacted audit logging, and structured error handling. Exposes bank tools for customer lookup, statement search, and dispute resolution over stdio and HTTPS transports.
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Local-first CLI + proxy that curates your MCP servers per client from one canonical config, cutting tool-schema tokens ~80% and resolving secret references instead of hardcoding keys.
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Headless MCP server for Metabase: 161 tools for queries, dashboards, admin and more. Plain API-key auth with no OAuth or browser, stdio or HTTP, works on any Metabase version and tier.
    47,629 npm
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    MCP server for the LiteLLM proxy, enabling agents to administer resources like keys, teams, users, models, and proxy settings through risk-graded meta-tools.
    6
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    An enterprise MCP server scaffold that provides secure, governed access to internal tools through RBAC, audit logging, rate limiting, and prompt-injection boundaries, with a FastAPI control plane and OpenTelemetry observability.
    MIT

TDQS

A3.9/5.0

Scored across 15 tools

Disambiguation5/5

Tools are clearly separated by resource and action, and the descriptions explicitly distinguish potentially overlapping operations such as status changes, renewal, and partial update. Cross-references between config_get and system_get_inbounds, and between users_get and subscription_get, further reduce misselection risk.

Naming Consistency5/5

All tools follow a consistent marzban_<resource>_<action> snake_case pattern. Compound actions like get_inbounds and get_usage still fit the same predictable convention.

Tool Count5/5

With 15 tools, the set is well-scoped and each tool has a clear purpose within user, node, subscription, system, or config administration. There is no obvious filler or redundant tool.

Completeness3/5

User lifecycle coverage is strong for create/get/list/update/status/renew/usage, but there is no delete-user operation. Node, host, and config surfaces are mostly read-only or list-only, so common admin tasks like removing a user or managing nodes/hosts have no tool path.

Maintenance

ActivityActive
ResponsivenessWithin a week