Skip to main content
Glama
wejack639

mcp-jumpserver

by wejack639
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mcp-jumpserver

No user-submitted related servers found.

    Related Servers

    • database-remote-mcp

      agts86
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables remote database access (RDBMS and MongoDB) through MCP tools, supporting read/write queries, schema management, and more.
      -

    • Supabase MCP Server

      JiayuuWang
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides secure access to Supabase databases via PostgREST API and management tools for projects, schemas, branches, logs, and code generation.
      MIT

    • PostgreSQL-MCP-Server

      I8Zoro8I
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to safely query one or more PostgreSQL databases with read-only tools and explicitly approved write operations.
      56 npm
      1
      MIT

    • Supabase MCP Server

      dedalus-labs
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables secure interaction with Supabase databases via the PostgREST API, supporting full CRUD operations and stored procedure calls. It utilizes the Dedalus MCP framework to provide encrypted credential handling and just-in-time token exchange.
      4
      MIT

    • Database Bridge MCP Server

      LucasSiqueiraSurreco
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables secure database interactions with MySQL, PostgreSQL, and SQLite through granular permissions, multi-database support, and cloud-ready SSL/TLS connections. Supports read-only modes, schema-specific permissions, and transaction management for safe database operations.
      8 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool has a distinct purpose: testing login, listing databases, listing accounts, and two credential-generation tools. The two credential tools differ by scope (single asset vs. all configured assets), which is clear from their descriptions, though they could still be confused at a glance.

    Naming Consistency5/5

    All tool names follow a consistent verb_jumpserver_noun pattern using snake_case (test, list, list, get, get). The pattern is predictable and readable, with no mixing of conventions or vague verbs.

    Tool Count5/5

    With 5 tools, the server is well-scoped for its purpose of managing and retrieving JumpServer database credentials. Each tool fills a clear role without excess or deficiency.

    Completeness4/5

    The set covers authentication verification, asset listing, account listing, and credential retrieval for single and bulk scenarios. Missing CRUD operations for databases or accounts are not central to the stated purpose, but a create/delete tool would round out the surface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources